Open data · Tool terms

What Sentry's terms say about your data

Six questions, answered from the documents Sentry publishes: 12 quoted facts from 11 pages, read October 22, 2026. Vendor: Functional Software, Inc. (Sentry). Plans covered: Developer, Team, Business, Enterprise.

Who owns it
The customer
AI training
Generative: opt-in. Other models: yes
Aggregated use
Reserved
What you can export
Part of it by any member through the API
History kept
Developer: 30 days, older data deleted. Team, Business, Enterprise: 90 days, older data deleted
After the account ends
None, export before the account ends

An asterisk marks our reading of the text rather than its words; the fact's note says what it rests on. "The terms don't say" means every contract, AI page and data processing addendum was read. Not legal advice.

Who owns it

Who owns the data the customer puts in?

The customer · covers all service data

  1. Headline Every plan covers all service data

    The customer

    Except for Sentry's use rights in this Agreement, between the parties Customer retains all intellectual property and other rights in Service Data provided to Sentry.

    Terms of Service 3.0.0 (terms), read 2026-10-22 · link to this fact

    Terms section 12 (Ownership).

AI training

Does the vendor train AI on it?

Generative: opt-in. Other models: yes · covers all service data

  1. Headline Every plan covers all service data

    Generative: opt-in. Other models: yes

    By default, your data will not be used to train any generative AI models without your permission.

    Service Data Usage (ai policy), read 2026-10-22 · link to this fact

    Generative: opt-in (also AI Privacy Principles: 'you may opt-in to further use of your data for product improvement'). Other models: the page's Data Access Summary table marks non-identifying data as used for training Sentry models ('Yes'), while aggregated identifying data (error messages, stack traces, spans, DOM interactions) is 'No (unless authorized)', i.e. opt-in. Terms 4.2 lets Sentry use Non-Identifying Data for Additional Uses incl. developing new products.

  2. Supporting Every plan covers non-identifying data

    Generative: opt-in. Other models: yes

    Non-identifying data No Other Sentry customers* Yes No

    Service Data Usage (ai policy), read 2026-10-22 · link to this fact

    Table row (columns: identifiable? / shared with / used for training Sentry models? / used to train 3rd party models?): non-identifying data IS used to train Sentry models by default. Identifying data for non-generative models needs authorization ('With your authorization, Sentry may use certain types of service data to improve our product.').

Aggregated use

Does the vendor keep a right to use it aggregated, de-identified or as usage data?

Reserved · covers non-identifying data

  1. Headline Every plan covers non-identifying data

    Reserved

    In addition to the rights granted above, Sentry may use Non-Identifying Data for Additional Uses.

    Terms of Service 3.0.0 (terms), read 2026-10-22 · link to this fact

    'Additional Uses' = 'any legitimate business purposes such as analytics, benchmarking, reporting and developing new products and services.' Usage Data may also be used for Additional Uses; disclosed externally only if Aggregated or Anonymized.

What you can export

What can the customer export, and who can run it?

Part of it by any member through the API · covers error events, full

  1. Detail Every plan covers error query results, selected columns

    Part of it by any member through an admin screen

    Click Export to download a CSV of the results.

    Errors (Export CSV) (help article), read 2026-10-22 · link to this fact

    Errors page query export, only the selected columns, limited to 10 million rows or 1 GB. 'who' inferred: org Members 'can view most data'; no role restriction stated for export. Page says a related query feature is 'available only if your organization is on a Trial, Business, or Enterprise plan'; plan gating of the CSV export itself is unclear.

  2. Detail Every plan covers logs, up to 10,000 lines

    Part of it by any member through an admin screen

    You can export up to 10,000 log lines in CSV or JSON Lines (JSONL) format.

    Logs (Export Data) (help article), read 2026-10-22 · link to this fact

    Logs only, capped at 10,000 lines.

  3. Headline Every plan covers error events, full

    Part of it by any member through the API

    Return a list of error events bound to an issue

    API: List an Issue's Events (help article), read 2026-10-22 · link to this fact

    REST API (auth token with event read scope); full=true includes full event body. Terms 4.6: 'During the Subscription Term, Customer may export or delete its Service Data from the Service using the export and deletion features described in the Documentation.' No full-org one-click export documented.

History kept

How much history does the plan keep?

PlanAnswerCovers
Developer 30 days, older data deleted error events
Team 90 days, older data deleted error events
Business 90 days, older data deleted error events
Enterprise 90 days, older data deleted error events
  1. Headline Developer covers error events

    30 days, older data deleted

    Errors 30 days 90 days 90 days

    Data Retention Periods (help article), read 2026-10-22 · link to this fact

    Error events; table columns Developer / Team / Business-Enterprise. Logs, profiles, spans 30 days on all plans (Business/Enterprise add 13 months sampled spans). Security page: 'Individual events are deleted after the above retention period.'

  2. Headline Team covers error events

    90 days, older data deleted

    Errors 30 days 90 days 90 days

    Data Retention Periods (help article), read 2026-10-22 · link to this fact

    Error events; table columns Developer / Team / Business-Enterprise. Logs, profiles, spans 30 days on all plans (Business/Enterprise add 13 months sampled spans). Security page: 'Individual events are deleted after the above retention period.'

  3. Headline Business covers error events

    90 days, older data deleted

    Errors 30 days 90 days 90 days

    Data Retention Periods (help article), read 2026-10-22 · link to this fact

    Error events; table columns Developer / Team / Business-Enterprise. Logs, profiles, spans 30 days on all plans (Business/Enterprise add 13 months sampled spans). Security page: 'Individual events are deleted after the above retention period.'

  4. Headline Enterprise covers error events

    90 days, older data deleted

    Errors 30 days 90 days 90 days

    Data Retention Periods (help article), read 2026-10-22 · link to this fact

    Error events; table columns Developer / Team / Business-Enterprise. Logs, profiles, spans 30 days on all plans (Business/Enterprise add 13 months sampled spans). Security page: 'Individual events are deleted after the above retention period.'

After the account ends

How long is data kept after the account ends, and can it still be exported?

None, export before the account ends · covers all service data

  1. Headline Every plan covers all service data

    None, export before the account ends

    When a customer terminates their subscription and deletes their account by selecting the option in their Sentry organization settings, all event data stored in the account becomes inaccessible to the customer within 24 hours.

    Security & Compliance (help article), read 2026-10-22 · link to this fact

    Data then deleted from production 'upon the expiration of the retention period' (30 or 90 days by plan from ingestion); backups deleted 90 days after creation. Terms 4.6: export only 'During the Subscription Term'; 'After the Subscription Term, Sentry will delete Service Data in accordance with its standard schedule and procedures.' days=null because no fixed post-cancel period is stated.

What the read couldn't settle

  • export: Sentry help-center articles on export (sentry.zendesk.com) require sign-in, unreadable; whether Errors CSV export is limited to Business/Enterprise/Trial is unclear from docs.sentry.io wording.
  • export 'who' is inferred (no role restriction stated); no documented full-organization data export for SaaS customers.
  • ai_training other_models: default state of the 'Service Data Usage' toggles for identifying data is described as requiring authorization; non-identifying data used by default.
  • after_cancel days: no fixed number; deletion follows plan retention (30/90 days) plus 90-day backups.
  • Docs pages (retention, service data usage, AI principles, errors, logs) show no last-updated date.

Documents

11 of 12 read. Each fact above names the one it comes from.

  1. Terms of Service 3.0.0 Terms · version 2024-02-12 · read 2026-10-22
  2. Data Processing Addendum 5.1.0 Data processing addendum · version 2024-05-29 · read 2026-10-22
  3. Privacy Policy 3.3.2 Privacy policy · version 2025-10-29 · read 2026-10-22
  4. AI Privacy Principles AI policy · read 2026-10-22
  5. Service Data Usage AI policy · read 2026-10-22
  6. Data Retention Periods Help article · read 2026-10-22
  7. Security & Compliance Help article · version 2025-08-27 · read 2026-10-22
  8. Errors (Export CSV) Help article · read 2026-10-22
  9. Logs (Export Data) Help article · read 2026-10-22
  10. API: List an Issue's Events Help article · read 2026-10-22
  11. Pricing Plans page · read 2026-10-22
  12. How can I export data? (help center) Help article · not read yet · couldn't be reached

Part of Tool terms, 20 tools under CC BY 4.0. JSON for this tool: /api/tools.json?tool=sentry. Spotted a changed term? Write to contact@dataconto.com with the page and the date.