Privacy Policy

Effective 10 August 2026. Last updated 29 September 2026.

Anticip8 helps you show up for the people you do business with. That only works if it handles what it learns with more care than any product you use, so this policy is written to be read, not skimmed. The controller of your personal data is Fountech.ai Limited, a company registered in Cyprus. Reach us at privacy@anticip8.ai.

The commitments that define the product

We do not sell personal data, ever, to anyone. Nothing you contribute is ever used to train a model that serves anyone else; where the service learns from your data it learns for your account alone, and that learning is never pooled or shared. Raw content from your connected sources is deleted shortly after we extract the signals we need from it; we keep the signal, not the message. Everything about a private person in your world is visible to you alone; there is no public profile, no score anyone else can see, and no shared surface for private people. Every anticipation shows you its evidence. We infer nothing sensitive: no health, no emotional-state labels, and nothing designed to profile a third party rather than help you act. We do not build cards about children: every card is checked twice against that rule before you see it, and a card that trips either check is dropped rather than softened. If you ever see a card that is about a child, tell us and we will take it down and fix what let it through.

What we collect

Account data: your email address, a securely hashed password (never the password itself), and your name if you choose to give one when your account is created. The name is optional; we use it to address you, and to stop somebody else putting your name on our public do-not-process list. Connected data, Google: if you choose to connect Google, we read contacts and calendar with read-only access, and only after Google's consent screen. That Google connection reads no email at all. Connected data, Microsoft: if you choose to connect a Microsoft account, we read contacts, calendar, Outlook mail and Teams chat, all read-only and only after Microsoft's consent screen. From Outlook mail we read the headers and the subject line, which is who wrote to whom and when, and the subject; we do not extract or store the body of any message. From Teams we read that a conversation happened, with whom and when; we do not read or store the text of Teams messages either. Uploaded data: files you import yourself (contacts or calendar exports); the file is deleted after extraction. Your own documents: if you choose documents about your company, your role and what you are working towards on the context page in the app, each one is read once to take out what it says about you and your company, and the file itself is not stored. What was taken from it is shown to you there to correct or remove; its words follow the same clock as your derived data, and anything you correct is kept as your own words for as long as your account is open. Choosing a new set replaces what was read from the last one. Derived data: the signals, anticipations, advice and outcome records (receipts) the service builds for you. Usage data: how much of the service you use, for the caps and for fair use. We publish no price, and we charge nothing unless a paid arrangement has been agreed with you in writing; where one has, we hold what is needed to bill it, Stripe handles the payment, and we never see or store your card number.

The request form is closed while Anticip8 is in development. What it collected before it closed is still held, and this paragraph says what happens to it. When it was open, we collected your name, work email, company, role, which platform your work mail and calendar run on, and anything you write in the free-text box. We also record the address your request came from and the browser that sent it, which is how we tell one person asking twice from a script asking a thousand times. We use it to answer you and to decide whether we can open an account for your company, on the basis of our legitimate interest in replying to a business enquiry. It is not used for marketing and it is never sold. The store deletes it twelve months after it arrives, on a rule rather than on somebody remembering to; we also email a copy to ourselves so a person sees it, and that copy is kept with our ordinary business correspondence. Ask us and we delete both sooner. If we open an account for you, what the account itself holds is covered by the rest of this policy.

What we use it for, and on what legal basis

To provide the service you asked for (contract): building your dashboard, anticipations, advice and receipts. To bill you (contract). To keep the service secure and honest, including enforcing usage limits (legitimate interests). To meet legal obligations (legal obligation). With your consent where the law requires it, which you can withdraw at any time, for example by disconnecting a source.

Who processes it for us

We use a short list of processors, each doing one job: Amazon Web Services hosts the service, the database and the access-request store; Stripe processes payments where a paid arrangement has been agreed; OpenRouter is our AI gateway, which passes the short text a card is built from, and the whole text of each document you choose on the context page, to one of the inference providers that serve the open-weight model we run, and every request we send carries two restrictions on that provider, that it may not keep prompts for its own purposes and that it must retain nothing once it has answered, which is set on the request rather than promised, so it holds whichever provider answers and no provider keeps or learns from what we send; Google provides the contacts and calendar APIs, and Microsoft the contacts, calendar, Outlook mail and Teams APIs for the sources you connect, and our own mailboxes; Vercel serves this website. Where data leaves the European Economic Area it travels under recognised safeguards such as Standard Contractual Clauses. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

About other people in your data

Your address book, your calendar and the documents you choose naturally mention other people. Those details stay inside your private space, are used only to help you show up for those relationships, and are never made public, pooled across users, or sold. If you are not an Anticip8 user and want your details excluded from the product entirely, see our Non-user opt-out page; we honour it.

How long we keep things

Raw connected content: deleted shortly after signal extraction, on a fixed schedule. Your derived data: the words are removed after 180 days, and the shape of the contact stays. What a person said to you, and what we wrote about them from it, goes on a fixed schedule; that you spoke on a Tuesday does not, because that is what makes the product work. Account and billing records: kept as long as the law requires. You can delete the data the service holds for you at any time, from the privacy page in the app, without closing the account. Ask us to close the account and your personal data is deleted with it, save what we must keep for legal or accounting reasons.

Your rights

You can ask for a copy of your data, correction, deletion, restriction, or portability, and you can object to processing based on legitimate interests. Write to privacy@anticip8.ai and we will answer within a month. You can also complain to the Commissioner for Personal Data Protection in Cyprus or your local supervisory authority.

Security

Data is encrypted in transit and at rest, connected-source tokens are encrypted with per-account keys, access is limited to what the service needs, and the production system refuses to start with weak configuration. No system is perfectly secure; if a breach ever puts you at risk we will tell you and the regulator as the law requires.

Changes

If this policy changes in a way that matters, we will tell you by email or in the app before the change takes effect.