Privacy policy

The short version

• Markindex only reads your ad accounts. It never changes anything in them.
• What an AI assistant can search holds no names of companies, accounts, campaigns or ads, no web addresses, and no IDs that can be looked up at Meta.
• We never save the text or the images of your ads. A model on our own server reads the text as it comes in, picks a few words from a fixed list, and forgets the rest.
• We do not sell data, we do not show you ads, and we do not let outside companies train models on your data.
• When you disconnect an ad account, what we pulled from it is deleted at once, and it is gone from our backups within 30 days.

Who we are

Markindex is run by Mighty Mini Apps, C.F. Møllers Allé 97, 2. tv, 2300 København S, Denmark, company registration number 42411027. We decide what is done with the data described here, which makes us the data controller under the General Data Protection Regulation (GDPR).

Write to hello@markindex.io with any question about this policy or your data.

What we save, and why

Your user

What we save: your email address, your password as a hash we cannot turn back into the password, whether you have confirmed your email, and the businesses you have access to. For each session we save when it started, the IP address and the browser it was started from, until it ends.

Why: to let you sign in, keep your user safe and send you the emails the service needs, such as a code to sign in with, a link to choose a new password, or an invitation.

Your business

What we save: the business's name, who has access and with which role, the invitations sent, whether each ad account is B2B or B2C, and its plan.

Why: to run the business you created in Markindex and let its people work together.

Your connection to Meta

What we save: the key Meta gives us when you connect (an access token), encrypted, with the ID and the name of your Meta login. We ask Meta for permission to read your ads and nothing more (ads_read).

Why: to pull the ad accounts and pixels you choose, each day, for as long as you keep them connected.

Your ad accounts

What we save: for each ad account you choose to connect, its name, its currency and time zone, the settings of the ad account and of every campaign, ad set and ad, its numbers by day and country, and Meta's record of the changes made in it. We do not save the names of the people who made the changes.

Why: to show you your own ad accounts, to find them when your assistant compares them with the index, and to build the index.

Your pixels

What we save: for each pixel you choose to connect, its settings and how many times each kind of event fired, by hour.

What we never receive: anything about the people who visit your website. Meta gives us counts, not visitors.

What your ads say

When an ad is new or has changed, we fetch its text from Meta and a small model on our own server reads it. The model picks the ad's objective, offer, angle, hook and call to action from a fixed list, and we save those picks.

What we never save: the text itself, the images and the videos. The text is held in memory while the model reads it and is never written to our database, a file or a log. No outside company sees it.

Your AI assistant

What we save: the keys your assistant uses to reach Markindex for you, stored as hashes, and how many calls each business makes, for the Free plan's cap. For each call we note which assistant made it, which of our tools it used and how many lines came back.

What we do not save: what you ask your assistant, what it searches for in the index, or what it answers you.

Your conversation takes place with the company behind your assistant, such as Anthropic for Claude or OpenAI for ChatGPT, under that company's own terms and privacy policy. What Markindex sends back to your assistant goes to that company. Read their policies before you connect.

Payments

What we save: which plan a business is on, and the IDs Stripe gives the business and its subscription.

What we never see: your card. Stripe handles cards, addresses, VAT numbers and receipts.

How the site is used

We use PostHog to see which pages are visited, what is clicked and what goes wrong, and to record visits so we can see where people get stuck. A signed-in visit is tied to your user by its ID, never by your email.

• What you type into a field is masked in a recording.
• Pages that show other people's emails, and pages whose address holds a link from an email, are not recorded.
• PostHog sets no cookie and saves nothing in your browser. A visitor who is not signed in counts as a new one each time.
• When something you do succeeds, such as connecting an ad account, we count it under your user's ID. We never send what you typed, an email address, a token or anything from your ad accounts.

Our own ads on Meta

Markindex advertises on Meta, and uses Meta's pixel on its own site to see what those ads lead to. It has nothing to do with the pixels you connect. It is only used if you press “Accept” when we ask about cookies. Until then, and if you press “Reject”, Meta's code is not loaded and nothing below is sent to Meta, from your browser or from our server.

• What Meta gets: that a page was visited, and when a user is created, a business is created or a business starts a paid plan. With each, the page's address without what follows “?”, your IP address, your browser, Meta's own cookies and, once you are signed in, a hash of your user's ID.
• What Meta never gets: your email, what you typed, the text of what you click, or anything from your ad accounts. Pages whose address holds a link from an email or an invitation send nothing.
• It is sent from your browser and from our server, so that it is counted once even when a browser blocks the pixel.
• Meta Platforms Ireland uses it under its own terms and privacy policy, and for this part we and Meta decide together what is done with it.

The index

The index is what members share and AI assistants search. It is kept apart from what we save to run Markindex, and the assistants' access reaches the index and nothing else.

• What goes in: the settings, numbers and record of changes of each ad account connected on the Free and Standard plans, with what its ads say from the fixed list, whether it is B2B or B2C, its currency and its time zone.
• What is taken out: every name, every web address and email address, every place finer than a region, the names of custom events and conversions, and the business's country. Every ID that is the advertiser's own is swapped for one that cannot be looked up, and the same ad account connected to two businesses cannot be linked.
• What it is used for: answering the questions of members' assistants, and the pages of the web app that show you where you stand against the market. Single ad accounts can be seen there, but never whose they are. We never say who is doing well.
• Private plan: a business on the Private plan is kept out of the index, and its data is not used in anyone else's answers.
• Answers already given cannot be taken back. Removing an ad account changes the answers that come after.

What we never do

• Change anything in your ad accounts.
• Sell, rent or license data, in the index or outside it.
• Use your data to show you or anyone else ads.
• Let an outside company read your ads, or train a model on your data.
• Tell anyone which business an ad account in the index is.

The grounds we rely on

• Our agreement with you (GDPR article 6(1)(b)): your user, your business, your connections, pulling your ad accounts, the index, and the emails the service needs. The terms are that agreement.
• Our legitimate interest (article 6(1)(f)) in keeping Markindex working and safe and making it better: PostHog, limits on attempts to sign in, and our backups.
• Your consent (article 6(1)(a)): Meta's pixel, which sees what our own ads lead to, and only if you press “Accept”. You can take it back at any time, under “Cookies” below.
• The law (article 6(1)(c)): keeping records of payments for as long as the Danish Bookkeeping Act asks.

Who else handles data

These companies handle data for us, under agreements that let them use it for us and for nothing else.

• Hetzner Online, Germany: the servers Markindex and its database run on, in Nuremberg.
• A second European hosting company: an encrypted copy of each night's backup, outside Hetzner. We name it here when it is chosen.
• PostHog: how the site is used and what goes wrong, in its cloud in the EU.
• Resend, United States: sends our emails, so it gets your email address and the email.
• Stripe: payments, cards, receipts and the emails about them, when a business pays.

Meta is where your ad data comes from, and gets what its pixel on our site sends (“Our own ads on Meta”). The company behind your AI assistant is who you talk to. Each handles data under its own terms. We share data with others only when the law demands it.

Where data leaves the EU, as with Resend and Stripe, it is covered by the EU–US Data Privacy Framework or the European Commission's standard contractual clauses.

How long we keep it

• An ad account or a pixel: for as long as it is connected. When it is disconnected, by you, a colleague, or by removing Markindex in Meta, what we pulled from it is deleted at once, from the index too.
• Your connection to Meta: until you remove it, you lose access to the business, or the business is deleted. Meta ends the key itself after 60 days unless you connect again.
• Your user: until you delete it.
• A business: until an admin deletes it, which takes everything in it at once.
• A session: 7 days after it was last used. A link to choose a new password works for an hour, and a key for your assistant at most 30 days.
• Records of payments: 5 years, as the Danish Bookkeeping Act asks.
• Recordings of visits: at most 90 days, in PostHog.
• Backups: 30 days. What is deleted is gone from every backup within 30 days, and is deleted again if a backup is ever restored.

Cookies

• Ours: one that keeps you signed in, one that keeps your answer to whether Meta may set cookies for 12 months, and short ones that show a message once, such as “Ad account disconnected”, or hand an event to Meta's pixel, and are then removed. None of them tracks you.
• Meta's: _fbp and _fbc, set by Meta's pixel, which let Meta tell that a visit came from one of our ads. They are only set if you press “Accept”. Markindex works the same without them.

You can change your answer at any time. If you change it to “Reject”, Meta's cookies are deleted.

Your rights

Under the GDPR you can ask us to:

• show you what we have about you, and give you a copy;
• correct what is wrong;
• delete it;
• limit what we do with it, or stop doing something with it;
• give it to you in a form another service can read.

Write to hello@markindex.io. We answer within 30 days. You can also complain to the Danish Data Protection Agency, Datatilsynet, at datatilsynet.dk, or to the authority where you live.

How to have your data deleted

Most of it you can delete yourself, at once:

• An ad account or a pixel: disconnect it on the business's Meta page, under Integrations.
• Your connection to Meta: remove it on the same page, or remove Markindex under “Business integrations” in your Facebook settings. Meta tells us, and we delete the key and disconnect the ad accounts connected through it.
• A business: an admin deletes it under Settings.
• Your user: delete it on “Your user”.

Or write to hello@markindex.io and we do it for you.

How we keep it safe

• Your key to Meta is encrypted, with a key that is not in the database, so a copy of the database or a backup cannot be used at Meta.
• Backups are encrypted before they leave the server.
• Assistants reach the index through a login that can read the index and nothing else: not users, businesses or keys.
• Everything travels over HTTPS.

Children

Markindex is a service for businesses and is not meant for anyone under 18.

Changes to this policy

When we change what we save or who handles it, we change this page and the date at the top. When a change matters to how your data is used, we email the users it concerns before it takes effect.