1. Who we are
OpenErrorAPI (openerrorapi.com) is an error-tracking service compatible with the official Sentry SDKs. It is operated by [NÁZEV PROVOZOVATELE], registered office [SÍDLO / REGISTROVANÁ ADRESA], company ID [IČO], VAT ID [DIČ / VAT ID] (“we”, “us”).
Privacy contact: hello@openerrorapi.com. Data protection officer: [POVĚŘENEC PRO OCHRANU OSOBNÍCH ÚDAJŮ (DPO) – kontakt, nebo uvést, že není jmenován]. Representative in the EU: [ZÁSTUPCE V EU (čl. 27 GDPR) – jen pokud provozovatel nesídlí v EU, jinak vypustit].
2. Our two roles
- We are the controller of data about our customers, their team members and visitors of our website: accounts, sign-in and security records, billing, support (section 3).
- We are a processor for the data that our customers’ applications send to the service — error events, release-health sessions, user feedback, source maps (section 4). The customer decides what its SDK sends and is the controller of that data. We process it only on the customer’s behalf, under the data processing terms in the Terms of Service [SMLOUVA O ZPRACOVÁNÍ OSOBNÍCH ÚDAJŮ (DPA) – doplnit samostatný dokument nebo potvrdit, že stačí kapitola v podmínkách].
If you are a user of an application that uses OpenErrorAPI and want to exercise your rights, please contact the operator of that application first. We will help them respond.
3. Data about you as our customer
| What | Examples | Why and on what legal basis |
|---|---|---|
| Account and profile | name, e-mail address, account (organisation) name, role, team membership, invitation and e-mail verification status, language and theme preference | to provide the service — contract (Art. 6(1)(b) GDPR) |
| Sign-in credentials | password stored only as a bcrypt hash; two-factor (TOTP) secret stored encrypted; recovery codes stored only as hashes | to secure your account — contract and legitimate interest (Art. 6(1)(f)) |
| Security records | IP address and browser of sign-ins and of devices you signed in from; a random device identifier (we store only its hash); failed sign-in counters; an audit log of actions in the account (for example project changes or token creation) with IP address; IP addresses that used your AI access tokens | to protect accounts, detect abuse and investigate incidents — legitimate interest (Art. 6(1)(f)) |
| Plan, usage and billing | plan and subscription periods, usage counters (events, new issues), add-on settings, monthly statements, plan change requests. We do not process payment card data — plans are invoiced, there is no payment gateway. | contract; accounting and tax obligations (Art. 6(1)(c)) |
| Optional integrations | your own AI provider API key (“bring your own key”) and access tokens of services you connect over MCP — both stored encrypted; names and domains of projects in those services | to provide features you switch on — contract |
| Correspondence | messages you send us | to answer you — contract or legitimate interest |
Website visitors. Our website uses no analytics, advertising or tracking scripts, and its fonts are served from our own servers. To deliver pages and fend off attacks, our web servers process your IP address and request details; server logs are kept for [DOBA UCHOVÁNÍ SERVEROVÝCH LOGŮ].
4. Data your applications send us
What we receive depends on how the customer configures its SDK. Typically an error event contains: the error type and message; the stack trace (file paths, function names, line numbers and the surrounding lines of source code); breadcrumbs (recent actions and log lines before the error); request data (URL, method, headers, query string); user context (such as an ID, e-mail address, username or IP address — whatever the SDK is set to send); tags; device, operating system, browser and runtime details; release and environment.
Depending on the features the customer uses, we also process release-health sessions, user feedback sent through the feedback widget (name, e-mail address, message, page URL, browser), browser security (CSP) reports, uploaded source maps (which may contain source code) and results of uptime and heartbeat monitors.
Scrubbing before storage
- On our server, before anything is stored, values of fields whose names indicate secrets — password, secret, token, API key, authorization, credit card or card number, CVV, social security number, session ID, private or access key, cookie — are replaced with
[Filtered]in request data, user data, contexts, extra data, breadcrumbs and tags. Customers can add their own field names. - IP addresses are removed by default. Each project has a “Remove IP addresses (GDPR)” setting that is on for new projects; a customer can switch it off.
- Scrubbing cannot be undone: what is filtered is never stored. Error messages and stack traces are not scrubbed, because grouping depends on them — please do not put personal data into exception messages.
We use this data only to provide the service to the customer (grouping, alerts, search, statistics and the features the customer enables). We do not sell it, use it for our own purposes or use it to train AI models.
5. Optional AI features
The AI features are optional. When they are used, part of the data is sent to an AI provider:
- AI analysis of an issue (when a team member asks for it): the error message and location, platform, environment and release, how often and when it occurred, request method and URL, the stack trace, breadcrumbs and the titles of related issues.
- Natural-language search: the text of the search query.
- Nightly AI triage — only for projects where it was switched on (it is off by default): the same kind of data for new issues.
- Digest e-mail summary: titles and counts of the most frequent issues. Each member can switch digests off.
By default these requests go through our account with Anthropic, PBC (USA). If the account owner adds its own API key for Anthropic or OpenAI (“bring your own key”), the requests go directly to that provider under the customer’s own contract instead. Transfer to the USA: [OVĚŘIT A DOPLNIT – právní mechanismus předání (např. EU-US Data Privacy Framework nebo standardní smluvní doložky) a smlouva o zpracování s Anthropic]. How Anthropic handles API data (training, retention): [OVĚŘIT AKTUÁLNÍ PODMÍNKY ANTHROPIC PRO API].
6. Where data is stored and who else receives it
| Recipient | What | Where |
|---|---|---|
| Our own servers — application, MySQL database (accounts, projects, issues), ClickHouse (events and sessions), Redis (short-lived counters and cache), source map files, backups | everything described above | EU — [LOKALITA DATOVÉHO CENTRA (stát, město)]; [PROVOZOVATEL DATOVÉHO CENTRA / HOUSINGU, pokud existuje] |
Our own mail server (mail.openerrorapi.com) | e-mail addresses and the content of e-mails we send | as above |
| Anthropic, PBC | inputs of the AI features (section 5), unless you use your own key | USA |
| Your own AI provider (Anthropic or OpenAI), only if you add your own key | inputs of the AI features | under your contract with that provider |
| Destinations you configure — webhooks, Slack, Discord, Telegram, Microsoft Teams, alert e-mail recipients | alert content (issue title, project, counts, link) | chosen by you; that service’s terms apply |
| Services you connect under Settings → Integrations (MCP) | only the requests needed to sign in and read your list of projects there — no error data is sent to them | chosen by you; that service’s terms apply |
| The public, if you publish a status page | monitor names and their status | public by design |
We use no other sub-processors. Before we add one, we will update this list and notify account owners [LHŮTA PRO OZNÁMENÍ NOVÉHO SUBDODAVATELE]. Authorities receive data only where the law requires it. Backups: [ZÁLOHY – kde jsou uložené, jak dlouho se drží, zda jsou šifrované].
7. Cookies
| Cookie | Purpose | Scope | Lifetime |
|---|---|---|---|
__Host-oea_console | keeps you signed in to the console (strictly necessary) | console.openerrorapi.com only; HttpOnly, Secure | 14 days from your last activity when signed in; otherwise until you close the browser |
__Host-oea_dev | a random device identifier, so we can warn you when someone signs in from a device you have not used before; we store only its hash (security) | console.openerrorapi.com only; HttpOnly, Secure | 1 year |
oea_hint | your display name, so our website shows “Open Console” instead of “Sign in”; it is not used for authentication | *.openerrorapi.com | same as the console sign-in (14 days); deleted when you sign out |
theme | your dark or light theme choice | *.openerrorapi.com | 365 days |
lang | the language you picked in the console’s language switcher | the site where you picked it | 1 year |
We use no analytics, advertising or third-party cookies, and the feedback widget and public status pages set none. Because we only use cookies that are needed for the service or that remember a choice you made, we do not show a consent banner. [OVĚŘIT PRÁVNĚ – zda preferenční cookies (theme, lang, oea_hint) nevyžadují souhlas]
8. E-mails we send
- Account e-mails: e-mail address verification, team invitations, password reset, confirmation of a new sign-in e-mail address.
- Security notifications — always sent, so you learn about changes you did not make: a sign-in from an unknown device, two-factor authentication switched on or off, a recovery code used or new codes generated, a new AI access token or a token used from a new IP address, a changed password, a changed sign-in e-mail (sent to the previous address), access disabled, sign-ins blocked after repeated failed attempts, account deletion scheduled and completed.
- Notifications you configure: error, regression, spike and monitor alerts, escalations, AI triage summaries and the digest (weekly, or daily on higher plans). Each member can switch the digest off.
- Account notices: trial ending, usage approaching the plan quota.
We currently send no marketing newsletters.
9. How long we keep data
| Data | Kept for |
|---|---|
| Account, members, projects and settings | until the account is deleted (section 10) |
| Raw error events | according to the plan: Free 14 days, Solo 30 days, Team 90 days, Business 180 days, Scale 180 days; with the extended-retention add-on up to 365 days; a project can choose a shorter period. Older events are no longer accessible and are physically removed by the storage expiry no later than 365 days after we received them. |
| Issue summaries (title, location, counts, first and last seen, status, comments) | until the customer deletes the issue, the project or the account |
| Release-health sessions | 90 days |
| Automatic issue history (status changes, assignments, AI triage notes — not comments) | 180 days |
| User feedback from the widget | 365 days |
| Log of rejected ingest requests | 7 days |
| Alert delivery log | 90 days |
| IP addresses that used AI access tokens | 90 days |
| Audit log of account actions | 400 days — also after the account is deleted, for security and accountability |
| Uploaded source maps | the project’s event retention, at least 30 days |
| Monthly billing statements | until the account is deleted [OVĚŘIT – zákonná lhůta pro účetní a daňové doklady může vyžadovat delší uchování] |
| Web server logs | [DOBA UCHOVÁNÍ SERVEROVÝCH LOGŮ] |
| Backups | [DOBA UCHOVÁNÍ ZÁLOH] |
10. Your rights, export and deletion
Under the GDPR you have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and to object to processing based on our legitimate interests (Art. 21). You can also lodge a complaint with a supervisory authority — in particular [DOZOROVÝ ÚŘAD (např. Úřad pro ochranu osobních údajů, pokud provozovatel sídlí v ČR)] or the authority of your country.
Most of this you can do yourself in the console under Settings → Profile:
- Export. The account owner downloads the whole account as a ZIP of JSON files — projects, issues, up to 5 000 raw events per project, settings and the audit log. Other members download their own personal data (profile, activity, comments). Password hashes and encrypted secrets are never exported.
- Deletion. The account owner can schedule deletion of the whole account. It happens after a 7-day grace period, during which it can be cancelled; we confirm both steps by e-mail. Deletion removes the account, members, projects, issues, events, sessions, source maps, tokens and integrations. Audit log entries are kept as stated in section 9.
- Corrections. You can change your name, sign-in e-mail (confirmed by a link), password and two-factor settings at any time.
For anything else, write to hello@openerrorapi.com. We answer within one month.
11. Security
- HTTPS only, with HSTS; passwords hashed with bcrypt; optional two-factor authentication with recovery codes.
- Two-factor secrets, your own AI keys and integration tokens are encrypted with a key kept outside the database.
- Sensitive fields and IP addresses are scrubbed from events before storage (section 4); the event store is not reachable from the internet.
- Roles and optional team-based project visibility; an audit log and security e-mails for sensitive changes; rate limits on sign-in and ingest.
- AI agents get scoped tokens that act with their member’s permissions and can never delete data or manage billing, members or account settings.
Please report vulnerabilities as described in security.txt.
12. Children and changes to this policy
The service is not intended for children under 16. We will announce material changes to this policy to account owners by e-mail [LHŮTA PŘED ÚČINNOSTÍ ZMĚNY, např. 30 dní] before they take effect. This policy applies from [DATUM ÚČINNOSTI].
13. Contact
[NÁZEV PROVOZOVATELE], [SÍDLO / REGISTROVANÁ ADRESA] — hello@openerrorapi.com