1. About this Privacy Policy
This Privacy Policy informs you of the policies and procedures governing the collection, use and disclosure of the information Statsopia receives when you access and use the service. It is incorporated by reference into our Terms of Use.
By using Statsopia you confirm that you have read, understand and agree to this Privacy Policy and the Terms of Use. Please do not use or access Statsopia if you do not agree to this Privacy Policy.
Statsopia is not intended for people under 18 and does not knowingly collect personal information from them. If you believe someone under 18 has provided information to Statsopia, use the contact address below and that information will be removed.
Statsopia — the website, software and analysis services described in this policy — is operated by Codreanu Daniel PFI, registered in Romania under registration number 35666649, with its registered office at Str. Olteniei no. 28, Sector 1, Bucharest, Romania. It is responsible for the information described here and is referred to throughout as "Statsopia".
For any privacy question or request, contact [email protected].
2. Information used by Statsopia
- Account details: your name, email address and authentication records, used to create and manage your account.
- Analysis inputs: your uploaded CSV or Excel dataset, variable choices and questions, used to prepare descriptive statistics and run supported analyses.
- Billing and usage: credit balances, transactions and payment references, together with a record of each AI request — the model used, token counts, duration and estimated cost. These support credit accounting and service operation. The text of your questions is not stored in these records.
3. Before you upload
You must have the right to upload and process your dataset, including permission or another valid basis for using information about other people.
Remove or anonymise names, national identification numbers, addresses, medical identifiers and other unnecessary personal data before uploading. Check free-text cells, column names and the questions you type, too.
4. Analysis and AI explanations
Statsopia processes datasets on its own backend, where dedicated statistical engines calculate the results. AI is never used to perform the calculations.
Statsopia sends each AI request to OpenAI, which processes it on Statsopia's behalf. A request contains your question, the number of rows and columns, your column names, and the statistical results already computed by Statsopia. Those results include category and group labels drawn from your data, which is why section 3 asks you to keep identifiers out of column names and labels. Your uploaded file and its individual rows are never sent, and requests do not carry your name, email address or account identifier.
OpenAI states that data submitted through its API is not used to train its models. Under the current configuration, OpenAI retains the request and the response for up to 30 days under its API data policies, and short-lived caching may hold request content for up to 24 hours.
Statistical results and AI explanations do not replace professional, medical, legal or research judgement.
5. Storage and deletion
When you upload a dataset, its full contents are saved to Cloudflare R2, an object storage service, so that your analyses can run across requests. The stored copy contains every row of your file, not a sample or a summary, and is readable only by your own account.
That copy stops being usable two hours after upload: after this point Statsopia refuses to read it and no analysis can reach it. Deletion is handled separately, by a scheduled cleanup job and by a storage rule that removes every dataset object within one day. Loss of access is therefore immediate at two hours, while physical removal follows within a day.
The active dataset and analysis stay in browser memory while you move around the signed-in area. Refreshing ends that continuity. Signing out or replacing a dataset clears the active browser workspace; it does not immediately erase the server copy. The dataset flow does not save raw datasets to your browser's local or session storage.
Account and billing records are kept for as long as your account exists, and afterwards for as long as accounting and tax obligations require. Credit transactions form a permanent ledger and are not edited or removed. Beta account retirement currently uses deactivation: this ends access but does not erase account or billing records, and existing credit transactions can prevent deletion of an account. Records already deleted may persist for a short time in routine database backups until those backups expire in the normal cycle.
When you agree to the Terms of Use and this Privacy Policy, Statsopia records that acceptance against your account: which version of each document you accepted, and when. Evidence of that acceptance — your email address in normalised form, the version of each document, the time each was accepted and the date the account was deleted — is retained for three years following account deletion, solely for the defence of legal claims, and is then deleted automatically. Where a documented legal hold applies, such as an active complaint, regulatory investigation or legal claim, that record is kept until the matter is finally resolved. No IP address or browser information is recorded with your acceptance.
Contact [email protected] about access, correction or deletion requests.
7. Services that support Statsopia
Statsopia relies on the following providers, each processing information only to deliver the function named:
- DigitalOcean — application hosting.
- Neon — the database holding account, credit and usage records.
- Cloudflare R2 — temporary dataset storage, as described in section 5.
- Cloudflare Web Analytics — page view and performance measurement.
- Resend — account emails such as address confirmation and password reset.
- OpenAI — AI explanations of computed results, as described in section 4.
- Stripe — credit purchases, when credit purchases are enabled.
Statsopia processes your information on these grounds: to perform the contract with you, which covers your account, your analyses and your credit balance; for its legitimate interests in keeping the service secure, preventing abuse and measuring whether the site works; and to meet legal obligations, in particular the retention of accounting records. Statsopia does not sell your information, does not use it for advertising, and does not use your datasets to train any model.
Some of these providers process information outside the European Economic Area. Where that happens, the transfer relies on the safeguards set out in that provider's data processing terms, such as the European Commission's standard contractual clauses.
8. Your rights and policy updates
Depending on where you live, you may have the right to ask for a copy of the information Statsopia holds about you, to have it corrected or erased, to restrict or object to how it is used, and to receive it in a portable form. You may also withdraw agreement to optional processing at any time — Statsopia currently relies on no such optional processing.
Send any request to [email protected]. Statsopia will answer within one month. Some requests cannot be met in full: credit transactions form an accounting record that must be retained, so erasing an account with a transaction history is not always possible. Where a request is refused or only partly met, you will be told why.
If you are in the European Economic Area or the United Kingdom and believe your information has been handled improperly, you may lodge a complaint with the data protection authority in the country where you live or work.
Future revisions will be identified by the effective date shown at the top of this page, and account holders will be asked to acknowledge the revised policy the next time they sign in. Where a change significantly affects how your information is used, account holders will also be notified by email before it takes effect. A correction that does not change the meaning of this policy — a wording, spelling or punctuation fix — updates only the “Last updated” date shown alongside it, leaves the effective date unchanged, and is not sent to you for acknowledgement. See also our Terms of Use.