Privacy Policy

This policy applies to the website marfor.pro, the MARFOR web application, and the MARFOR connector for Claude — both the remote connector at https://marfor.pro/api/mcp and the local MCP client available at marfor.pro/mcp.

1. Who we are

MARFOR (“we”, “us”) is a marketing mix modeling, forecasting and budget planning service operated by Oleg Egorov, Russian Federation. For any question or request about your data, email support@marfor.pro.

You decide what marketing data you upload to MARFOR and what it is used for; we process it to provide the service to you. We are responsible for your account data and for the technical data described below.

2. What we collect

Account and billing data

• Your email address, username and password. We store the password only as a hash, never as plain text.
• If you sign in with Yandex ID: the Yandex account ID, login, email, first and last name, display name and avatar ID that Yandex shares with us.
• Your plan, balance, payment history (amount, date, transaction number) and usage counters, such as how many forecasts you ran this month. You enter card details on the payment provider's page; we never see or store them.
• Optional answers to the onboarding survey: company, role, goals, marketing budget range and how you heard about MARFOR.
• If you request a paid plan: the email, phone number and comment you enter, plus the page, referring site, campaign tags (UTM), IP address and browser of that request.
• If you invite people to a project: their email addresses and the access level you give them.

Data you upload or connect

• Files you upload (CSV, Excel) and data imported from sources you connect, such as Yandex Metrica, Google BigQuery, Calltouch or Trino.
• The access tokens or credentials those sources need, kept so that scheduled imports keep working.
• Everything MARFOR builds from your data: column mappings, forecasts, models, channel elasticities, scenarios, dashboards and published links.

MARFOR works with aggregated marketing data — spend, traffic, orders, revenue. It doesn't need information about your customers as individuals, so please don't upload it.

Technical data

• Web server logs: IP address, time, requested address, response code and browser.
• Error reports that MARFOR pages send automatically from your browser: page address, error message, browser and your account ID.
• Records of AI feature use: time, feature, model and number of tokens, with the first 200 characters of the request.

3. Data from the Claude connector

When you connect Claude to MARFOR, Claude sends MARFOR a request each time it uses one of the connector's tools. The request contains the tool name and the arguments Claude filled in — for example, a project ID, metric and dimension names, filters and a period, new values for a scenario edit, a dashboard's HTML, a help question or the text of a support request. MARFOR answers with data from your account, limited to what your account can see.

• Call log. For each request we record the time, the event (for example, a tool call or a token refresh), the tool name, outcome, duration, your account ID, the connection and application IDs, and the IP address. Like every request to marfor.pro, it also appears in the web server logs (section 2). We don't record the arguments, the results or the tokens.
• Help questions and support requests. Questions you send through the help tool (marfor_help) are kept in our help log so we can improve the documentation. Support requests (marfor_feedback) are kept in the same log and emailed to our support mailbox so we can answer you.
• Connection record. When you approve a connection, we store the name the client gave itself (for example, Claude), the address it returns to, when you approved it and when it was last used. Access and refresh tokens are stored only as SHA-256 hashes.
• Local MCP client. If you use the local client instead, we store your personal access tokens as hashes, with their name, creation and expiry dates, and the time and IP address of their last use.

Results that the connector returns become part of your Claude conversation. Anthropic handles them under the terms and settings of your Claude account.

4. How we use data

• To provide MARFOR: store your data, run forecasts and models, show results, share projects with the people you invite, and publish the dashboards you choose to publish.
• To run your account: sign-in, plan limits, payments and balance.
• To keep MARFOR secure: detect abuse, limit request rates and investigate incidents.
• To support you: answer your requests and fix errors that you report or that our error log catches.
• To send service emails: email confirmation, password reset, invitations, notices when a calculation finishes, and security notices such as a new access token for Claude. MARFOR sends only service emails like these.
• To improve MARFOR: usage statistics, error reports and the questions people ask the help tool show us where the product and its documentation need work.

Your uploaded data is used only to build forecasts and models for your own projects. We don't sell personal data or uploaded data, we don't use them for advertising, and we don't use them to train AI models for anyone else.

5. AI features in MARFOR

Some features inside MARFOR use Claude, an AI model made by Anthropic: explanations of model results, recommendations, help with scenarios, and dashboards built by AI. When you use such a feature — and for some analyses, automatically after a model finishes training — MARFOR sends Anthropic what the feature needs: column and metric names, aggregated figures, model results and your question. Anthropic processes this data under its commercial terms and privacy policy.

These requests pass through a relay server that we run on Railway in the USA. Requests to Google BigQuery made by the BigQuery connector go through the same relay.

If you add your own Anthropic API key in MARFOR, these features use your key, and the terms of your Anthropic account apply. We store the key so we can make those requests for you.

This section is about AI features inside MARFOR. When you use Claude through the connector, Claude runs in your own Claude account (see section 3).

6. Cookies and analytics

• Sign-in cookie. One cookie keeps you signed in. It expires after 31 days.
• Browser storage. Your browser's local storage keeps interface settings, such as the language you chose.
• Yandex Metrica. On marfor.pro we use Yandex Metrica to understand how people use the site: pages visited, time on page, clicks, device and browser, and approximate location derived from the IP address. Metrica sets its own cookies for this. On public pages — such as the home page, the connector pages and this policy — Metrica also records session replays and click maps for visitors who are not signed in. Inside the application, session replay and click maps are turned off, so the figures in your projects are not recorded. You can block Metrica with your browser's tracking protection or with the Yandex Metrica opt-out add-on.
• Language detection. On your first visit, the site asks ipapi.co which country your IP address belongs to, to choose the interface language.
• Page assets. Fonts and page libraries load from Google Fonts, jsDelivr and cdnjs (Cloudflare). As with any web request, these providers receive your IP address and browser details.

7. Where data is stored

MARFOR runs on servers we rent from Yandex Cloud in the Russian Federation. Account data, uploaded data, models and results, logs and backups are stored there. If you use MARFOR from another country, your data is transferred to the Russian Federation.

Some processing happens outside Russia, only as described in this policy: AI requests (Anthropic and our relay on Railway, USA), BigQuery requests (Google, through the same relay), language detection (ipapi.co) and page assets (Google Fonts, jsDelivr, cdnjs).

8. Who we share data with

We share data with these service providers, only for the purpose shown:

Data also reaches other people only when you decide so:

• People you share with see the projects and dashboards you share with them, at the access level you choose.
• A dashboard you publish can be opened by anyone with its link. If you allow indexing, search engines can show it.
• Claude. When you use the connector, the results of each tool call go into your Claude conversation (section 3).

We disclose data to authorities only when the law requires it. We don't sell data and don't share it with advertisers.

9. How long we keep data

10. Security

• All connections to marfor.pro use HTTPS.
• Passwords and access tokens are stored only as hashes.
• Our databases accept connections only from inside our server, not from the internet.
• Every request is checked against your access rights to the project it touches.
• The connector limits request rates and rejects requests from unexpected websites.
• Access to our servers is limited to the operator of MARFOR.

If a security incident affects your data, we will tell you by email.

11. Your choices and rights

• Get a copy. Export tables from MARFOR yourself, or ask us for a copy of your data.
• Correct. Change your data in MARFOR or ask us to correct it.
• Delete. Delete projects and data sources in MARFOR at any time. To delete your account, email support@marfor.pro from the address of your account.
• Revoke Claude's access. In Claude, open Customize › Connectors › MARFOR and select Disconnect. In MARFOR, open Account › Connect Claude (MCP) and select Revoke next to the connection; it stops working immediately. See the connector guide.
• Analytics. Block Yandex Metrica as described in section 6.
• Object or restrict. Email us if you object to a particular use of your data or want us to limit it.

Depending on where you live — for example, under the EU or UK GDPR or Russian Federal Law No. 152-FZ “On Personal Data” — you may have further rights, including the right to complain to a data protection authority. We answer requests within 30 days.

12. Children

MARFOR is a tool for businesses. It isn't intended for children, and we don't knowingly collect data about them.

13. Changes to this policy

We publish changes on this page and update the date at the top. If a change significantly affects how we use your data, we'll email you before it takes effect.

14. Contact

Oleg Egorov, operator of MARFOR, Russian Federation
Email: support@marfor.pro

Legal information in Russian, including payment and refund terms, is on the Legal information page.