legal

Privacy Policy

Last updated: November 5, 2026

Who we are

The controller of your personal data is Oleh Karmazyn, sole trader (jednoosobowa działalność gospodarcza), Katowice, Poland — NIP 6272797122, REGON 540789943. You can reach us about anything in this policy at hello@corlecti.com.

Summary

We do not sell your data and do not use it for advertising. No Corlecti product runs third-party analytics, an advertising network or a session recorder. Threads counts steps through its reading and checkout flow as anonymous events, without cookies or any browser identifier, described under Threads.

The browser extension is local-first: your notes live in your browser, not on our servers — unless you connect Corlecti Map and choose folders or files to send to it. Map, Threads and Talk are hosted products, so what you create in them is stored on our servers: Map and Threads in the United Kingdom, Talk in Poland. Files you upload to Map are stored by Cloudflare R2, in its Eastern Europe location. Where you use an AI feature, the content that feature needs is sent to the provider of the model it uses. Every section below says which. We do not use your content to train AI models.

Your Corlecti account

One account works across all our products. It is created when you sign in with Google, and it is where we hold your identity and billing information.

We store your IP address and browser user-agent with each sign-in session, so that a sign-in can be looked into if something goes wrong with your account. We do not use them to profile you.

Every product’s database is backed up every night to a separate server of ours (OVHcloud, in the United Kingdom or Poland), and each backup is deleted after 30 days.

AI and model training

We do not use your content — notes, maps, prompts, recordings, transcripts or anything else you create — to train or fine-tune AI models, and we do not give it to anyone for that purpose. What an AI provider may do with a request it receives is set by its own terms: OpenAI, Anthropic and Google (on paid use of the Gemini API) state that they do not train their models on API requests. DeepSeek’s terms allow it to use the content it receives to improve and train its models; that is one more reason Map does not use it unless you choose it (see Transfers).

Why we are allowed to process this

Under Article 6(1) of the GDPR, we rely on:

• Performing our contract with you (point b) — running your account, storing what you create, the features you use, taking payment. Without this we cannot provide the service.
• Your consent (point a) — marketing email, Threads announcements, the optional Corlecti Map connection in the extension, connecting a Telegram bot to Map, sending your Map content to DeepSeek in China. You can withdraw consent at any time, and withdrawing it does not affect what happened before.
• Our legitimate interests (point f) — keeping accounts secure, preventing abuse, being able to show what you agreed to and when, counting usage so we can apply plan limits and decide what to build, and counting visitors steps through Threads’ reading and checkout flow, not emailing again an address that bounced for good, and sending only email about the account and payments to an address that marked our email as spam.
• Legal obligation (point c) — keeping invoices and accounting records for the period Polish tax law requires.

To have an account you have to give us your email address and Google account id, which Google sends when you sign in; without them we cannot provide the service. Everything else is up to you: leaving it out only means the feature that needs it does not work.

We make no decision about you based solely on automated processing that has legal or similarly significant effects. The one automatic rule: when a product runs a beta with a limited number of places, people are admitted in the order they sign in until it is full, and the next are put on its waitlist; a person can admit you from it.

Cookies

Every cookie any Corlecti product sets is listed below. All of them are strictly necessary: they keep you signed in, protect a sign-in, or remember a choice you made. No Corlecti product sets a measurement, analytics or advertising cookie.

Some products also use your browser’s local storage, which never leaves your device on its own: the support portal at support.corlecti.com keeps you signed in there and keeps a ticket you have not sent yet; Map, Threads and Talk remember display preferences; Threads keeps the notes and progress of a reader who is not signed in.

Who else can see your data

We use the following providers to run the service. Each receives what its job needs and processes it under its own terms. This list covers every provider our code sends personal data to; providers that only ever receive lesson text, such as the one that voices Talk’s lessons, are not listed.

We do not sell your personal data, we do not share it for advertising, and we disclose it otherwise only where the law obliges us to.

International transfers

Our servers are in the United Kingdom and Poland, with OVHcloud. Your account, Map and Threads data are stored in the UK, which is outside the EU; that transfer relies on the European Commission’s adequacy decision for the United Kingdom. Files you upload to Map are stored by Cloudflare R2, not on our servers, in the location Cloudflare labels Eastern Europe. That is where Cloudflare places the storage; it is not an EU jurisdiction setting, and we do not claim the files stay in the EU.

Several providers above are in the United States. 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. Map’s default AI provider, Anthropic in the United States, receives what the AI needs — your message and the parts of your maps it works on — on our key, under the Standard Contractual Clauses. Cloudflare’s network and Telegram operate worldwide.

DeepSeek processes and stores data in China. Map uses it only when you choose a DeepSeek model; it then receives what the AI needs — your message and the parts of your maps it works on — whenever that model runs for your account. This transfer rests on your explicit consent under Article 49(1)(a) of the GDPR. Before a DeepSeek model first runs for your account, Map asks for it and sets out the risks: China has no adequacy decision from the European Commission, so its law does not protect your data the way the GDPR does; DeepSeek does not offer the Standard Contractual Clauses, so no contract with it adds that protection; Chinese public authorities may be able to access the data, and you may not be able to enforce your rights against DeepSeek; and DeepSeek’s terms allow it to use what it receives to train its models. Map records your answer with its time and the version of the text you were shown. Without your consent no DeepSeek call is made from any part of Map — the chat, the home chat, the Telegram bot, scheduled runs or delegated tasks. You can go back to the default model, or choose another, and you can withdraw your consent at any time in Corlecti Map → Settings → AI Chat Model; DeepSeek is then refused again. Map keeps the record of your consent for six years from the deletion of your account, then deletes it. Talk tells DeepSeek only your languages, level and chosen tone, which do not identify you.

Requests the extension makes with your own AI key go from your browser straight to that provider — including DeepSeek in China and OpenRouter — under your own agreement with it; they never pass through us.

How we protect it

• Your browser connects to our products only over encrypted HTTPS.
• Refresh tokens and API keys are stored hashed. Provider keys and bot tokens you give Map are encrypted, and only the last four characters of a provider key are ever displayed.
• We never see your card details — Stripe handles payment on its own pages.
• Signing in uses Google, so we never hold a password of yours.

No system is perfectly secure. If a breach puts your data at risk, we will notify UODO within 72 hours of learning of it, and, where the risk to you is high, tell you without undue delay.

Your rights

Wherever you are, you can ask us to:

• Give you a copy of what we hold about you.
• Correct anything that is wrong.
• Delete your account and the data in it.
• Export your data in a portable, machine-readable form.
• Restrict processing while a dispute about it is resolved.
• Withdraw a consent you gave, such as marketing email.

Your right to object. You can object at any time, on grounds relating to your situation, to processing based on our legitimate interests; we then stop unless we have compelling legitimate grounds that override yours, or need the data for a legal claim. You can object to direct marketing at any time, with no reason needed, and we then stop.

You can change your Corlecti marketing-email choice yourself on your account page. Notification and news emails from Corlecti products carry an unsubscribe link or a switch in the product’s settings (Map: Settings → Notifications; Threads: Settings → Notifications), and Map’s plan offer goes only to people who joined that plan’s waitlist. One press on the link stops that kind of email from that product, and the same page undoes it. Emails about your Corlecti ID, payments and security are not part of it. For anything else, email hello@corlecti.com from the address on your account and we will answer within 30 days. There is no charge. We will not make you justify the request. Deleting an account and exporting its data are done by hand on request — there is no button for either. An export comes as a file of your account’s data, an export of each of your maps and, where a product holds data for you, a copy of it. In Threads you can also download or erase your reading data yourself, in Settings; in Map you can delete a map yourself.

When we delete your account, we cancel your subscriptions and, within 30 days, delete the account and its data, have Corlecti Map delete your content (see the Map section for what it keeps), and remove what Threads and Talk hold for you. Backups are not edited: they age out within 30 days of the deletion. Delivery logs at our email provider and short-lived server logs expire on their own.

What remains after a deletion:

• Invoices and payment records, at Stripe and in our accounts: 5 years from the end of the calendar year in which the tax on them fell due, as Polish tax law requires.
• A short record outside our database — your email address, account id, Stripe customer id, the date of your request and what you asked for, when the account was created, whether and when you accepted our terms and which version, and which products we touched — kept as proof that you consented and that we handled your request, for 6 years from the end of the year of the deletion, the general limitation period for claims under the Polish Civil Code (Art. 118).
• In Threads, the record of emails sent to you, kept so that they are not sent again.
• If an email to your address bounced for good or was marked as spam, a one-way hash of the address (not the address itself), under our legitimate interest: after a bounce we send that address no more email, after a spam mark only email about the account and payments, until we lift the block. It names no one without the address.
• Our record of admin actions on email delivery (lifting such a block, sending a message again), which holds that hash or a message id, never the address.
• Content already sent to an AI provider, which stays under that provider’s own retention.

If you think we have handled your data wrongly, we would rather you told us first. But you have the right to complain to a supervisory authority regardless. Ours is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warsaw, Poland — uodo.gov.pl. If you live elsewhere in the EEA, you may complain to your own national authority instead.

California residents

We collect the categories of personal information set out in the tables above, for the purposes stated there. We do not sell or share personal information as the CCPA defines those terms, and you can ask to know, correct or delete what we hold, without being treated differently for asking, at hello@corlecti.com.

Children

Corlecti is not for anyone under 16. We do not knowingly collect data from children. If you believe a child has given us data, write to hello@corlecti.com and we will delete it.

Changes to this policy

We will update the date at the top whenever this changes. If a change materially affects your rights — a new category of data, a new purpose, a new provider seeing your content — we will tell you by email or in the product before it takes effect, not after.

What changed on November 4, 2026: every Corlecti product’s email now goes through Brevo, and no other email provider is used. One unsubscribe page serves Corlecti’s email; Map and Threads join it as their email moves over. The tables above gain an “Email we send you” record, and we keep a one-way hash of an address that bounced for good or marked our email as spam, and a record of admin actions on email delivery, even after an account is deleted.

What changed on November 5, 2026: Map’s default AI provider is now Anthropic (Claude), on our key, in the United States, under the Standard Contractual Clauses; Claude Sonnet also runs on our key. DeepSeek, in China, is used only when you choose it, and only with your consent as before. Files you upload to Map are described by their Cloudflare R2 location, Eastern Europe. Map now deletes the record of your DeepSeek consent six years after your account is deleted, instead of keeping it indefinitely.

Contact

Privacy questions, data rights requests and anything else: hello@corlecti.com. Our terms of service are at corlecti.com/terms.