Privacy Policy

Effective Date: April 15, 2026
Last Updated: September 21, 2026

Statory ("Service," "Platform," "we," "us," or "our") is an AI-powered statistical analysis platform operated by Statory Co., Ltd. ("Operator"). This Privacy Policy explains how we collect, use, disclose, and protect your information when you use our website at statory.org and related domains (collectively, the "Website").

By using the Service, you consent to the practices described in this Privacy Policy. If you do not agree, please do not use the Service.

1. Information We Collect

1.1 Information You Provide

1.2 Information Collected Automatically

1.3 Information We Do NOT Collect

• We do not collect payment card numbers (handled entirely by Paddle)
• We do not collect government-issued IDs
• We do not collect biometric data
• We do not use tracking pixels from advertising networks
• We do not participate in cross-site behavioral advertising

2. How We Use Your Information

We use collected information for the following purposes:

2.1 Service Delivery

• Processing your uploaded data to perform statistical analyses
• Generating AI-powered interpretations of your results
• Exporting results in your chosen format (PDF, Excel, clipboard)
• Maintaining your analysis history (if you opt in)

2.2 Service Improvement

• Monitoring analysis engine performance and error rates
• Identifying common usage patterns to prioritize features
• Improving AI interpretation quality based on aggregated, anonymized usage data—and, only with your explicit opt-in, data you allow for training (see Section 3.6)

2.3 Communication

• Responding to support requests or feedback
• Sending service announcements (e.g., maintenance, new features)
• Sending transactional emails (e.g., password reset, subscription confirmation)

2.4 Security and Legal

• Preventing fraud, abuse, and unauthorized access
• Complying with applicable legal obligations
• Enforcing our Terms of Service

3. How We Handle Your Uploaded Data

This section is critical because Statory processes user-uploaded datasets.

3.1 Data Transmission

Your data is transmitted to our servers over encrypted connections (HTTPS/TLS 1.2+) when you initiate an analysis.

3.2 Data Processing

Statistical computations are performed on our backend servers. Data is held in server memory during the analysis session.

3.3 Data Storage

Important: "We do not store your raw upload" means we do not keep your original data file as a permanent server archive. Some related data may still be stored as described below.

• Default behavior: your original file is never kept as a permanent server archive, but two short-lived copies do exist so you can come back to your work:
  • Resume snapshot — kept for 48 hours so you can pick up where you left off. A daily cleanup job removes expired snapshots, so the longest it can live is about 72 hours.
  • Parsed upload — the table we read out of your file (rows, column info) is kept for 30 days so analyses can re-run without a re-upload, then deleted by a daily cleanup job.
  You can delete either at any time from your account, and both go with the account when you delete it.
• Browser storage: Data may be cached in your browser's localStorage or session storage for session continuity and faster reload. This data stays on your device until you clear it.
• Saved results: If you choose to save analysis results to your account, the results (tables, charts, interpretations) are stored in our database. The original uploaded data file is not stored.
• Saved data (preprocessed): If you explicitly choose [Save current data], preprocessed data (tabular data, variable metadata, preprocessing history) is stored in our database under a name you specify. We do not store the original file name. Only your account can access it until you delete it (per-account storage limit applies). This data may be used for AI quality improvement in de-identified form only, under §3.6 (on by default — turn it off anytime in Settings → Data controls); use as identifiable training material still requires explicit opt-in under §3.6.
• Naming cache: To avoid repeat AI calls, we may store hashed or derived naming suggestions (variable labels, factor names) linked to your account—not your full dataset.
• Preprocess state: Optional server-side state (e.g., column mappings, preprocessing choices) may be saved to resume work across sessions when you use those features.
• Decision log: When you are signed in, we may record your confirmed choices (variable names, selected options, and settings only — never cell values or raw data) linked to your account, to improve automatic suggestions. This includes qualitative choices such as code approvals, unit settings, and anonymization on/off — response text and excerpts are never stored in this log.

3.4 AI Processing Data Flow

When you use AI-based features, information required for those features is sent to external AI providers. We use multiple providers and the system selects a provider based on feature, cost, and quality:

• Anthropic (Claude API, United States) — in-depth AI interpretation and fallback processing
• DeepSeek (DeepSeek API, China) — file type detection, label shortening, research question guidance, Tongnol temperament/decision/translation, and other auxiliary AI features. Information sent is processed on servers in the People's Republic of China (see §11)

By feature, the information sent may include:

• Summaries of statistical results (test statistics, p-values, effect sizes, etc.)
• Variable names, variable labels, and survey question text (when using label shortening, etc.)
• A sample of file content — up to approximately 1,500 characters (automatic file type detection)
• Text you directly enter for that feature (e.g., research questions, dilemma text in Tongnol decision helper)

We do not send full raw datasets (response row data) or account information (such as email) to AI providers. We recommend that you do not include personally identifiable information in text you enter directly.

Each AI provider may retain interaction data under its own privacy policy. Please review Anthropic's Privacy Policy and DeepSeek's Privacy Policy. If you do not use AI features, no information is sent to AI providers.

3.5 Qualitative Analysis and Anonymization

For qualitative or open-ended responses, we may apply pseudonymization or anonymization (e.g., removing or masking identifiers) before analysis or storage. Identifiers are handled to reduce personal identification risk while preserving analytical value.

3.6 AI Quality Improvement (Opt-Out)

Default: ON (opt-out). You can turn this off at any time in Settings → Data controls, and it never affects your ability to use any core service (PIPA/GDPR-aligned — never required for basic use).

You do not need an account to turn it off. The same toggle in Settings → Data controls is available without logging in; the choice is saved in that browser and applies immediately. Signed in, the choice is saved to your account and follows you to other browsers.

What we keep — de-identified text. We keep what you said to us (a question you typed, a help-chat question), sentences from public material, what the machine suggested, what you confirmed, and the shape of your data (row and column count bands, measurement-level distribution, missing-rate bands). We keep no key that links a row to your account — no user id, email, IP address, room code or source row id.

What we do not keep. The data you upload is not kept: response values, cell values, variable names and label text, open-ended answers and file names are zero. That material belongs to the people who answered it, not to us.

What withdrawal does. Turning it off stops future collection. It does not reach back into rows already de-identified, or into a model already trained on them — those rows carry no key that leads to you, so there is no way to find "yours". We will not promise to delete something we cannot find.

Retention. Text nobody has reviewed is deleted within 90 days. Automatic checks catch email addresses, phone numbers and long digit strings, but they cannot catch a person's name or an organization's name — only a human pass can, so anything that pass has not seen does not stay. Once reviewed (approved, or with names masked), a record is kept without a time limit: it does not point to a person, so a retention clock does not apply. A record we reject in review has its text deleted there and then — it is not used for training, and the text itself does not stay. Only what was rejected and where (the shape of the data, the machine's suggestion, the person's choice) remains.

Learning never reads your call logs directly. The AI call logs in §9 are a separate store with its own retention; the learning store holds only the rows described above, written at the moment you confirmed a decision. The underlying call logs follow the table in §9.

Separately, any use of identifiable data or your analysis artifacts as training sources (e.g., per-work "can use for training" on anonymized preprocessing results) remains strictly opt-in and is never enabled by default.

3.7 Data Deletion

• You may clear locally stored data by clearing your browser's localStorage.
• You may delete saved results from your account's history page.
• You may delete your entire account from the Settings page.
• Once requested, your account is locked for 30 days and then erased. You can cancel the request at any time during those 30 days by signing in again.
• Upon account deletion, all associated data is removed within 30 days.
• Cases and results you chose to make public may remain after deletion with your name removed; you can choose to delete them together on the account deletion screen.
• Records used only as statistics are kept without you — the person is removed and the counts remain, so no individual can be identified from them.
• Payment and settlement records are retained for the period required by law (5 years under the Act on Consumer Protection in Electronic Commerce), separated from your account and reduced to the transaction id, amount and date.

4. Cookies and Tracking

4.1 Essential Cookies

We use essential cookies for:

• Authentication: Maintaining your login session (Supabase auth cookies)
• Locale preference: Remembering your language choice (statory-locale)

These cookies are strictly necessary for the Service to function and cannot be disabled while using the Service.

4.2 Analytics (When Enabled)

We may use Google Analytics 4 (GA4) to collect anonymized usage statistics:

• Pages visited, features used, session duration
• Geographic region (country level, not precise location)
• Device category (desktop, mobile, tablet)

Google Analytics data is anonymized (IP anonymization enabled) and is used solely for understanding aggregate usage patterns.

We also use Vercel Analytics, a cookieless service that records page views and a small number of product events (sign-up, first analysis run, paid conversion, file upload, guide view) without cookies or personal identifiers.

4.3 No Advertising Cookies

We do not use advertising cookies, retargeting pixels, or third-party tracking for ad purposes. We do not sell or share data with advertising networks.

4.4 Cookie Management

You can manage cookies through your browser settings. Disabling essential cookies may prevent the Service from functioning properly.

5. Data Sharing and Disclosure

5.1 We Do NOT Sell Your Data

We do not sell, rent, or trade your personal information or uploaded data to any third party.

5.2 Service Providers

We share limited data with the following service providers, solely for the purpose of operating the Service:

5.3 Legal Requirements

We may disclose your information if required by law, subpoena, court order, or governmental request, or if we believe disclosure is necessary to:

• Comply with a legal obligation
• Protect our rights, property, or safety
• Prevent fraud or address security issues

5.4 Business Transfers

In the event of a merger, acquisition, or sale of assets, user data may be transferred as part of the transaction. We will notify affected users before their data becomes subject to a different privacy policy.

6. Data Security

6.1 Technical Measures

• All data transmission uses HTTPS/TLS encryption
• Database access is restricted by authentication and role-based permissions
• Server infrastructure is hosted on managed platforms (Vercel, Render) with security certifications
• Passwords are hashed using industry-standard algorithms (via Supabase Auth)

6.2 Organizational Measures

• Access to user data is limited to the Operator
• We do not share database credentials with third parties
• We conduct periodic reviews of access permissions

6.3 Limitations

No method of electronic transmission or storage is 100% secure. While we strive to protect your information, we cannot guarantee absolute security. You use the Service at your own risk.

7. Your Rights

7.1 All Users

Regardless of your location, you have the right to:

• Access: Request a copy of the personal data we hold about you
• Correction: Request correction of inaccurate personal data
• Deletion: Request deletion of your account and associated data
• Export: Download your saved analysis results
• Withdraw consent: Stop using the Service at any time

To exercise these rights, contact us at support@statory.org.

7.2 European Economic Area (EEA) — GDPR

If you are in the EEA, you have additional rights under the General Data Protection Regulation (GDPR):

Legal Bases for Processing:

Additional GDPR Rights:

• Right to restriction: Request that we limit processing of your data
• Right to data portability: Receive your data in a structured, machine-readable format
• Right to object: Object to processing based on legitimate interest
• Right to lodge a complaint: File a complaint with your local data protection authority

Data Transfers: Your data may be processed on servers located outside the EEA (currently United States). We rely on standard contractual clauses and the data processing agreements of our service providers to ensure adequate protection.

Data Protection Officer: For GDPR inquiries, contact support@statory.org with the subject line "GDPR Request."

7.3 California Residents — CCPA

If you are a California resident, you have rights under the California Consumer Privacy Act (CCPA):

• Right to know: You may request disclosure of the categories and specific pieces of personal information we collect, the sources, the business purpose, and third parties with whom we share it.
• Right to delete: You may request deletion of personal information we collected.
• Right to opt-out of sale: We do not sell personal information. No opt-out is necessary.
• Right to non-discrimination: We will not discriminate against you for exercising your CCPA rights.

Categories of Personal Information Collected (past 12 months):

To exercise your CCPA rights, email support@statory.org with the subject line "CCPA Request."

7.4 South Korea — PIPA

If you are in South Korea, your data is protected under the Personal Information Protection Act (PIPA, 개인정보보호법):

• You have the right to access, correct, delete, and suspend processing of your personal information.
• We process personal information based on your consent (provided by using the Service).
• In the event of a data breach, we will notify affected users and relevant authorities within 72 hours as required by law.

For PIPA inquiries, contact support@statory.org.

Personal Information Protection Officer:

• Name: Yongchan Song
• Email: support@statory.org

8. Sensitive Data — Special Restrictions

8.1 Health Data (HIPAA)

Statory is NOT a HIPAA-compliant service. We do not enter into Business Associate Agreements (BAAs). Do not upload Protected Health Information (PHI). If you work with health data, you must de-identify it in accordance with HIPAA Safe Harbor or Expert Determination methods before uploading.

8.2 Education Data (FERPA)

Statory is NOT a FERPA-compliant service. Do not upload education records containing personally identifiable student information. De-identify all student data before uploading.

8.3 Children's Data (COPPA)

Statory is not directed at children under 13. We do not knowingly collect personal information from children under 13. If we learn that we have collected such data, we will delete it promptly.

8.4 Your Responsibility

You are solely responsible for ensuring that data you upload does not contain sensitive information prohibited by applicable regulations, or that you have obtained all necessary consents and authorizations.

9. Data Retention

Upon account deletion, all personal data is removed within 30 days. Aggregated, anonymized data that cannot identify you may be retained indefinitely for statistical analysis of service usage patterns.

10. Third-Party Links

The Service may contain links to third-party websites or services (e.g., documentation references, YouTube tutorials). We are not responsible for the privacy practices of these third parties. We encourage you to read the privacy policies of any third-party service you visit.

11. International Data Transfers

Our servers are currently located in the United States (Vercel, Render, Supabase). Information may also be sent to AI providers in the United States (Anthropic) and China (DeepSeek) for AI processing. Under applicable law, we disclose cross-border transfers as follows:

You may avoid transfers to AI providers by not using AI features. Server hosting in the United States is essential to the Service; if you do not agree, you cannot use the Service. For EEA users, we rely on Standard Contractual Clauses (SCCs) and similar transfer mechanisms; for transfers to China, we provide this notice and the choice not to use the relevant AI features.

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will:

• Post the revised Privacy Policy on this page
• Update the "Last Updated" date
• Notify users of material changes via email or a prominent notice on the Website

Continued use of the Service after changes constitutes acceptance of the revised Privacy Policy.

13. Contact Us

For any questions, concerns, or requests regarding this Privacy Policy or your personal data:

statory
Email: support@statory.org
Website: https://statory.org

For region-specific requests, use the following subject lines:

• GDPR: "GDPR Request"
• CCPA: "CCPA Request"
• PIPA: "PIPA Request"
• General: "Privacy Inquiry"

We will respond to all requests within 30 days (or sooner as required by applicable law).

See also: Terms of Service.

This Privacy Policy is effective as of the date first written above. This policy may be supplemented or updated as laws and our service evolve. We will notify you of material changes in advance when practicable.