Privacy Policy
What we collect, why we collect it, who else sees it, what we publish, and how to get it back or get rid of it.
Last updated: 23 October 2026
1. Who is responsible for your data
Muplex Technologies Ltd. (UIC 204266947, VAT BG204266947), ul. Borovo 52, office 2, Sofia, Bulgaria, is the data controller for personal data processed through BrandReco. For anything in this policy, write to contact@brandreco.com. Our full company details are on the Legal notice page.
We are the controller for everything this policy describes. We do not process personal data on your behalf as a processor, which is why the Terms ask you not to put other people's personal data into BrandReco. If your use would need a data processing agreement under Article 28 GDPR, contact us before you rely on it.
We have not appointed a Data Protection Officer, as we are not required to. Your requests go to the address above and are handled by us directly.
2. What we collect from you
| Category | What it includes | Where it comes from |
|---|---|---|
| Account data | Email address, first and last name, password (stored only as a salted hash — we never see it), the plan you are on, whether you finished onboarding, and your email preferences: how often, at what hour and in which time zone. | You, when you register — or Google, if you choose to sign in with Google (your name and email address) |
| Workspace and brand data | Workspace names, brand names, domains, descriptions, notes, and the competitors you track. | You, in the product |
| Analyzed website content | Public pages, robots.txt, sitemaps and llms.txt from the domains you nominate, plus facts extracted from them. | Our analysis of public web pages |
| Prompt and result data | The prompts you track, the exact text sent to each AI model, the answers returned, visibility scores, sentiment, timings and token counts. | You, and the AI providers' responses |
| Payment data | Billing name and address, the plan you bought, invoices and payment status. Your card number goes to Stripe and never reaches us. | You, through Stripe's checkout |
| Free check requests | The website you checked, the optional one-line description you gave, the result, the email address if you choose to give one, and a one-way hash of your IP address used only for rate limiting — we do not store the raw IP. The result itself is published: see section 7. | You, on the free check page |
| Support and email | Messages you send us, the account and product emails we send you, and which actions you marked done from an email link. | You, and our mail system |
| Technical data | Server logs with request metadata and a request ID, used to run and debug the service. | Automatically, when you use the site |
| Analytics | Pages viewed and referrer, via our own self-hosted Umami instance — only if you allow analytics. When you are signed in, this is linked to your email address. | Your browser, with consent |
3. Data about people who are not our users
Some of what BrandReco processes comes from public sources rather than from the person it is about. Article 14 GDPR says those people should be told, so this is that notice.
| Whose data | What we hold | Where it comes from |
|---|---|---|
| Owners of websites someone ran a free check on | The domain, its public pages, and what AI agents said about it. A business website is rarely personal data, but a sole trader's can be. | Whoever ran the check, the public site, and the AI agents' answers |
| Publishers of pages AI agents cite | An email address or contact page published on that page, so the customer whose AI answers cited it can ask the publisher to consider them. It is shown only to that customer. | The public page itself |
| People posting in public forums | For research into the problems customers in a market describe: the link to a public discussion (for example on Reddit or Hacker News), its title, its date and the short snippet a search engine shows. We don't collect usernames or profiles, though a snippet can contain whatever its author wrote. | A web search API (Serper) and the public discussion |
| People named in AI answers or public pages | Where an AI answer or an analyzed page names a person — a founder, an author — that text is stored as part of the answer or page. | AI agents' answers, and public pages |
We rely on legitimate interests for all of this — section 5 says which interest, case by case. How long each is kept is in section 10. Everyone listed here has the rights in section 11, including the right to object in section 12; to have a public check page about your website taken down, see section 7.
4. Do you have to give us this?
Your email address and a password are required — without them we cannot create an account or sign you in, so the service cannot be provided. You need to confirm your email address to keep using the account after a short grace period. A brand name and domain are required for any analysis to run, because they are what gets analysed.
Everything else is optional. Your name, brand descriptions and notes only improve the output; leaving them out costs you accuracy, not access. Analytics is entirely optional and refusing it changes nothing about the service you receive.
5. Why we use it, and our legal basis
| Purpose | Legal basis (GDPR Art. 6) |
|---|---|
| Creating your account, signing you in, and providing the service you asked for — website analysis, prompt runs, insights and daily actions. | Performance of a contract (Art. 6(1)(b)) |
| Sending service email: email verification, password resets, your actions email, change alerts and notices about changes that affect you. Every product email can be switched off in one click. | Performance of a contract (Art. 6(1)(b)) |
| Taking payment for a paid plan and keeping the accounting records that go with it. | Contract, and legal obligation (Art. 6(1)(b) and (c)) |
| Running a free check you asked for, and emailing you the result if you give us your address. | Your request (Art. 6(1)(b)); for the email, your consent (Art. 6(1)(a)) |
| Rate-limiting the free check with a hashed IP, so a tool that costs us money per answer isn't abused. | Legitimate interest in preventing abuse (Art. 6(1)(f)) |
| Publishing free check results and the category pages built from them (section 7). | Legitimate interests (Art. 6(1)(f)): offering a free public record of how AI agents answer about businesses, and showing what we measure. We never publish who ran a check, and we remove a page when the site's owner asks. |
| Publishing your scorecard, if you turn it on. | Performance of a contract (Art. 6(1)(b)) — a feature you chose, which you can turn off at any time |
| Keeping the shared directory of businesses that customers see in their market (section 8). | Legitimate interests (Art. 6(1)(f)): showing customers who else is in their market. Only a business's domain, name and public profile are shared — never which account added it, or anything from an account. |
| Finding the publishers and public discussions that shape AI answers in a market, and the published contact route of a cited page (section 3). | Legitimate interests (Art. 6(1)(f)): helping customers reach the places AI agents learn from |
| Keeping the service secure and available: logs, error tracking, detecting and stopping bots, credential guessing, duplicate free accounts and payment fraud — including banning the accounts involved and reporting fraud. | Legitimate interests (Art. 6(1)(f)) |
| Understanding which pages are used, via self-hosted analytics. | Consent (Art. 6(1)(a)) — you can withdraw it at any time |
| Improving the product: fixing what breaks, and deciding what to build from aggregated usage. | Legitimate interests (Art. 6(1)(f)) |
Where we rely on legitimate interests, we have weighed them against your rights and concluded they don't override yours. You can object at any time — see section 12.
6. What we send to AI providers
To measure how assistants describe your brand, we must actually ask them. That means the prompt text, your brand and competitor names and domains, and relevant public page content are sent to the AI providers you have enabled for your workspace. Your email address, password and payment details are never sent to them.
Some analyses run on a language model we host ourselves, in which case nothing leaves our infrastructure. The AI Policy sets out which is which, and what the providers may do with what they receive.
None of the AI providers we use trains on your data, and when our self-hosted model is unavailable, that analysis waits until it is back rather than moving to another provider. See Training in the AI Policy.
7. What we publish
- Free check pages. When anyone runs the free check, the result for that website is published at brandreco.com/check/<site>: the questions asked, what AI agents answered, and which businesses they named. The page never shows who ran the check or their email address. Once it holds answers it can be listed in search engines.
- Category pages. brandreco.com/recommended/<category> summarises, across free checks, which businesses AI agents named for a category. It is a record of what AI agents said, not our assessment or endorsement of any business.
- Your public scorecard. Off by default. If you turn it on in Settings, your tracked questions, how AI agents answered them over time and the titles of your completed actions are published at brandreco.com/scorecard/<name> and can be listed in search engines. Turning it off takes the page down.
Getting a page removed. If a free check or a category page is about your website and you want it removed or corrected, email contact@brandreco.com with the subject "Remove a public check", from an address at that domain or with another way to show the site is yours. We act on it within 7 days. Search engines may keep showing a cached copy for a while afterwards, which we can't control.
9. International transfers
Most AI providers listed above, and Stripe's parent company, are based in the United States, so running your prompts and taking payment involves transferring data outside the EEA. Those transfers rely on the European Commission's Standard Contractual Clauses, or on the EU–US Data Privacy Framework where the provider is certified under it. Email us and we will send you a copy of the safeguards that apply to a given provider, and tell you which mechanism it relies on.
If you would rather no data left the EEA, you can restrict your workspace to self-hosted models — contact us and we will help you set that up.
10. How long we keep things
- Account data: while your account exists, and up to 30 days after you delete it (backups may lag slightly behind).
- Accounts never confirmed: a free account whose email address is still unconfirmed 30 days after sign-up is deleted, with everything in it.
- Accounts banned for bot activity: deleted once 30 days have passed without a successful challenge, apart from what we must keep by law or for a legal claim.
- Workspace, brand, prompt and run history: while your account exists, so you can see trends over time. Delete a brand or prompt and its history goes with it.
- Free checks: the email address, the optional description and the IP hash are erased 12 months after the check. The published result stays up until the site's owner asks us to remove it.
- Contact details found on cited pages: kept with the action they belong to, and deleted with it or with your account.
- Public forum links and snippets: a limited number per market problem, the oldest dropped as newer ones arrive.
- The business directory: kept while it is useful to customers; a business's owner can ask us to remove theirs.
- Activity log of AI tools you connect to your account: 90 days.
- Invoices and accounting records: as long as Bulgarian tax law requires, typically 10 years — this overrides a deletion request for those records.
- Server logs: normally 30 days.
- Analytics: aggregated, and retained no longer than 24 months.
11. Your rights
If you are in the EEA or UK, you have the right to:
- access the personal data we hold about you, and get a copy;
- have inaccurate data corrected;
- have your data deleted, where we have no overriding reason to keep it;
- restrict how we process it while a dispute is resolved;
- receive the data you gave us in a portable, machine-readable format;
- object to processing we base on legitimate interests — see section 12;
- withdraw consent at any time — for analytics, use the Cookie Settings page; withdrawal doesn't affect what we did before.
You can delete your account yourself, from Settings, at any time. For everything else, email contact@brandreco.com and we will respond within one month. We may ask you to confirm your identity first, so we don't hand your data to someone else.
You also have the right to complain to a supervisory authority. Ours is the Commission for Personal Data Protection (Комисия за защита на личните данни), 2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, Bulgaria — www.cpdp.bg. You may also complain to the authority where you live or work.
12. Your right to object
13. How we protect it
- Traffic to the site is encrypted with TLS; the certificate is renewed automatically.
- Passwords are stored only as salted hashes, using Django's password hashing — nobody at our end can read them.
- Sessions use signed, HTTP-only cookies with CSRF protection on every state-changing request.
- Your data is scoped to your account: every request is filtered by the signed-in user, and data belonging to someone else returns 'not found' rather than leaking its existence.
- Links in our emails that act on your account do exactly one thing, for one action, and expire.
- Access to production systems is limited to people who need it.
No system is perfectly secure. If we become aware of a breach that puts your rights at risk, we will notify the supervisory authority within 72 hours and tell you without undue delay where the risk to you is high.
14. Automated decisions
BrandReco scores and prioritises findings automatically, and generates recommendations with AI models. These affect what the product suggests to you — they do not produce legal effects or similarly significant effects on you, and no decision about you is made solely by automated means. You are always free to ignore a recommendation.
15. Children
BrandReco is a business tool and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child has given us data, tell us and we will delete it.
16. Changes to this policy
We will update this page when our processing changes, and revise the "last updated" date at the top. If a change materially affects you, we will tell you by email or in the product before it takes effect. Email notices go to accounts with a confirmed email address only.
Muplex Technologies Ltd. · UIC 204266947 · VAT BG204266947 · Bulgaria
Questions about this page? contact@brandreco.com