Privacy policy of analfabeta.pl

In short: we do not store your letters. The Service has no database or accounts: your letter passes through our server function to the AI provider only while the paid service runs, and the result returns to your tab. The only lasting trace is the payment record in Stripe. Details below.

1. Data controller

1. The controller of your personal data is:
   Sprzedawca: Michał Szadkowski
   Adres: Bluszczańska 74, 00-712 Warszawa
   Kontakt: kontakt@analfabeta.pl
   The controller operates as działalność nierejestrowana (unregistered business activity under article 5(1) of the Polish Entrepreneurs' Law) and therefore has no NIP or REGON (we).
2. Contact for data protection matters: kontakt@analfabeta.pl. We have not appointed a data protection officer.

2. How the processing works, step by step

1. The letter you paste or photograph is prepared in your browser (photos are downscaled on your device) and kept in sessionStorage, one browser tab's memory. Nothing reaches our server yet.
2. You tick the consent box for immediate performance of the service and proceed to Stripe Checkout. Stripe collects payment data on its side; we pass it only the service type, the chosen language and your consent, recorded in the session metadata.
3. After payment you return to the Service. Only then does your browser send the letter over an encrypted connection to our server function on Vercel infrastructure. The function checks with Stripe that the payment is paid and unconsumed and passes the content to Anthropic's API, whose model generates the analysis or draft reply. On our server the content exists only in working memory while that request is handled.
4. The result returns to your browser and the function marks the payment in Stripe as consumed. We store neither letter nor result: we have no database or file storage and do not log request content or model responses.
5. In the browser the letter and working state stay in sessionStorage and disappear when you close the tab; a completed analysis is additionally saved in localStorage — on your device only — so closing the tab does not destroy a paid result. You remove it by clearing the site's data in your browser.
6. The only lasting trace is the payment record in Stripe: amount, status, session identifier, service type, language, consent and a "consumed" flag. It does not contain the letter.

3. What data we process and on what basis

1. The letter and the result (text, photos or PDF, receipt date, language). Official letters usually contain personal data (name, address, PESEL, case number, amounts) and sometimes sensitive data, such as health, criminal proceedings or residence status. Basis: article 6(1)(b) GDPR (performance of the paid contract for an analysis or a reply to which you are a party); for other people's data in the letter (for example a family member you help), article 6(1)(f) GDPR (your and our legitimate interest in having it explained). Special categories of data (article 9 GDPR) are processed based on your explicit consent, given by knowingly uploading the document after reading this information (article 9(2)(a) GDPR); you may withdraw it at any time for the future. If you do not want certain data in the system, black it out before sending.
2. Payment and order data: Stripe collects the data needed for payment (method, amount, e-mail, card or bank details). From Stripe we receive only the session identifier, status, amount and order metadata (service type, language, consent, consumed flag), never the card number. Basis: article 6(1)(b) GDPR (performance of a contract) and (c) (accounting and tax obligations; the Consumer Rights Act obligation to demonstrate consent to immediate performance).
3. Technical connection data: IP address, browser (user agent), time and request path including query parameters, region and status code — kept in Vercel infrastructure logs for 1 day (point 6) to maintain and secure the Service. We do not link them to letters. Basis: article 6(1)(f) GDPR (security).
4. Visit statistics: Umami counts page views and a handful of product events (e.g. a checkout being started) with no cookies and no data that identifies you; a visit session gets an identifier derived as a hash of IP address, browser and website ID. We see only aggregates; letter content, file names and anything derived from your document never reach the statistics. Basis: article 6(1)(f) GDPR (traffic analysis).
5. Correspondence: if you write to us (a complaint, a refund request), we process your e-mail address and message to reply. If you choose a manual analysis under the refund policy, a human reads the letter; we process it only for that purpose and delete it when the matter is closed. Basis: article 6(1)(b) or (f) GDPR.

4. Recipients of data (subprocessors)

• Vercel Inc. (USA): site and server-function hosting; a processor. It handles network traffic, briefly including request content in the function's memory, and the technical data in point 3.3.
• Umami Software, Inc. (28 Geary St, Suite 650 #243, San Francisco, California, USA; the cloud.umami.is service): visit statistics — no cookies, no data that identifies you (point 3.4); a processor. Letter content never reaches it. Umami's own subprocessors: umami.is/subprocessors.
• Anthropic Ireland, Limited (6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland): provider of the AI model that processes the letter and generates the result; a processor. The recipient in the United States is Anthropic PBC. Data is stored in the US and model inference runs only there — we enforce this with a dedicated parameter on every request. Anthropic deletes inputs and outputs within 30 days. There is one exception worth saying plainly: content flagged by Anthropic's automated trust-and-safety systems may be retained for up to 2 years, and the classification scores (scores, not the content) for up to 7 years. Anthropic does not train models on commercial API content — a contractual commitment (Commercial Terms of Service, §B: "Anthropic may not train models on Customer Content from Services.").
• Stripe (Stripe Payments Europe, Limited, Ireland, and Stripe, LLC, South San Francisco, USA): payments. For payment data Stripe is an independent controller (stripe.com/privacy); it processes order metadata on our instructions.

To quality-check our own translations we use DeepL (DeepL SE, Cologne, Germany). It receives only our own texts — interface strings and our own test material — never the content of your letter, your result, or anything derived from them. DeepL therefore processes no personal data of our users and is not a processor. We use no other subprocessors, do not sell data and do not share it with anyone else unless the law requires it.

5. Transfers outside the EEA

1. Some of our providers process data in the United States, outside the European Economic Area. The transfer mechanism, for each provider separately (verified against the providers' binding contracts and the official list at dataprivacyframework.gov, 26 August 2026): - Anthropic Ireland, Limited → Anthropic PBC (USA): the European Commission's Standard Contractual Clauses (Modules 2 and 3), incorporated by the Anthropic data processing agreement. Anthropic has no entry on the EU–US Data Privacy Framework list. - Stripe Payments Europe, Limited (Ireland) → Stripe, LLC (USA): the EU–US Data Privacy Framework — Stripe, LLC's certification is Active — with the Standard Contractual Clauses as the contractual fallback; Stripe's Data Transfers Addendum sets that order of precedence. - Vercel Inc. (USA): the Standard Contractual Clauses (2021) together with the UK Addendum, per Schedule 3 of Vercel's data processing agreement. Vercel may process data in the United States and anywhere else it maintains data processing operations. - Umami Software, Inc. (USA): the Standard Contractual Clauses (Modules 2 and 3), under Irish law and Irish courts, per Schedule 3 of Umami's data processing agreement; servers in the US and the EU. Umami has no entry on the Data Privacy Framework list. - DeepL SE (Cologne, Germany): we send no personal data (point 4), so no transfer takes place.
2. You can ask for a copy of the safeguards at the address in point 1.2.

6. How long we keep data

• Letters, photos, results: we do not keep them on our side. They exist in the server function's memory while the request runs (seconds), and in your browser: working state until the tab closes, completed results in localStorage until you clear the site's data. Our processor's retention is a separate matter: our AI provider deletes inputs and outputs within 30 days, with the exceptions described in point 4.
• Payment data and order metadata: at Stripe per its policy and payment services law; accounting documents on our side as long as tax law requires (currently 5 years from the tax year's end). The consumer-law consent record is kept with the payment record for the limitation period of contract claims.
• Vercel runtime logs: 1 day (Pro plan, without the extended observability add-on; as of 26 August 2026). A log entry contains the IP address, browser (user agent), request path including query parameters, region and status code. Our application never writes letter content or results to logs — tests enforce this. Build logs live as long as the deployment itself (production deployments on the Pro plan: 1 year) and contain no user data. Vercel takes backups every two hours and keeps each for 30 days.
• Visit statistics: in Umami Cloud for our plan's retention period — currently 6 months. Only the data described in point 3.4, on servers in the US and the EU (point 5).
• Correspondence: until the matter is closed and for the limitation period of any claims.

7. Cookies and browser storage

1. The Service sets one cookie, NEXT_LOCALE, which remembers your interface language for 1 year. It is necessary for the language choice and not used for tracking, so it needs no consent.
2. We do not use advertising, tracking or analytics cookies.
3. The Service uses your browser's storage: sessionStorage for working state (points 2.1 and 2.5), gone when the tab closes, and localStorage for completed results (point 2.5). This data is sent nowhere except in the request in point 2.3; you clear localStorage by removing the site's data.
4. Stripe Checkout may set its own technical cookies on its domain, necessary for payments and fraud prevention.

8. Your rights

1. You have the right to access, rectify and erase your data, restrict its processing, object to legitimate-interest processing, data portability, and withdraw consent (without affecting earlier processing).
2. Honestly: since we store no letters or results, usually there is nothing for us to hand over, correct or erase. In practice we can handle requests about our correspondence with you and, to a limited extent, the payment record (otherwise, turn to Stripe).
3. Send your request to the address in point 1.2. We will reply within one month.
4. You can lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl) or with the supervisory authority where you live.
5. We make no automated decisions about you with legal effects (article 22 GDPR); the analysis is information for you, not a decision about you.
6. Providing data is voluntary, but without the letter we cannot perform the service and without payment data (collected by Stripe) we cannot accept payment.

9. Security

The connection is encrypted (HTTPS). The letter reaches the server only after payment and only while the service is performed. We do not log letters or results, error messages are stripped of content, and uploads are limited in size and type. The card number never reaches us. The most important safeguard, however, is architectural: nothing can be stolen from a database that does not exist.

10. Changes to this policy

We may update this policy when the law, our providers or the way the Service works change. The new version appears here with the update date. This version applies from 2026-08-26.