This policy explains what personal data we collect when you use status302: the website and developer documentation at status302.com, the web app at app.status302.com, the status302 iOS app and the API at api.status302.com (together, the “Service”). It explains why we collect the data, who processes it on our behalf and what rights you have. We have tried to write it so it can be read without a lawyer.
Who is responsible for your data
status302 is a product of status403 Sp. z o.o. (status403 Spółka z ograniczoną odpowiedzialnością), with its registered office in Warsaw, Aleja "Solidarności" 68 lok. 121, 00-240 Warszawa, Poland, entered in the Register of Entrepreneurs of the National Court Register (KRS) kept by the District Court for the Capital City of Warsaw, 12th Commercial Division, under KRS number 0001269943, NIP 5253108931, REGON 54585207200000, share capital PLN 5,000.00. We are the controller of the personal data described here.
For anything concerning your personal data, write to [email protected]. We have not appointed a data protection officer, because the scale of our processing does not require one; that address reaches the people who handle it.
What data we collect and why
Visiting the website and the docs
When you open a page, your browser necessarily sends connection data: your IP address, browser and device type, the page requested, the referring page and the time of the request. We need it to deliver the page and to protect the Service against abuse. All our domains are served through Cloudflare, which processes this data as part of delivering and protecting them. Our own web server does not keep an access log.
The website’s fonts and search are served from our own domain. The interactive API reference runs in your browser: when you try a request there, it goes from your browser directly to our API.
Analytics and advertising measurement, only with your consent
With your permission we use Google Analytics 4 to understand how the website and the docs are used and Google Ads to measure campaigns and show relevant ads. Both load through Google Tag Manager, and Tag Manager itself is not fetched until you allow at least one of them in the cookie notice. Until then nothing is sent to Google’s measurement servers and no Google cookies are set. The two purposes are separate choices.
If you allow analytics, Google collects the pages you view, how you got here, approximate location derived from your IP address, your browser and device, and interactions such as scrolling and outbound clicks. If you allow advertising, Google additionally stores advertising identifiers and uses your activity to measure our campaigns and personalise ads. The web app and the API never load Google Analytics or Google Ads.
Your account
To create and run your account we process your email address, your name and profile picture (if you set them, or if they come from Google, Discord or Apple when you sign in with them), the organisations you belong to and your role in each, and the settings you choose (region, display currency, price basis, fee settings, saved presets, lists and alert rules).
- Signing in by email. We email you a single-use sign-in link, valid for 15 minutes, together with a one-time code you can enter instead of opening the link. A short-lived cookie ties the link and the code to the browser or app that asked for them.
- Signing in with Google or Discord. If you choose this, the provider tells us your account identifier, your verified email address, your name and your profile picture. We do not receive your password, and we accept only an email address the provider has verified.
- Signing in with Apple (iOS app). If you choose Sign in with Apple, Apple tells us the identifier of your Apple account for our app, your email address (or, if you choose “Hide My Email”, a private relay address at privaterelay.appleid.com that forwards to you) and, the first time only, the name you choose to share, which we use as your profile name. Apple also gives us a token that we store in encrypted form and use only to revoke our access to your Apple account when you delete your account. We do not receive your Apple ID password.
- Our Discord community server. When you sign in with Discord, Discord also lets us add you to the status403 community server, once (if you leave it, we do not add you back). We record whether you joined it (added on sign-in, or by opening the invite from the app) and when you last answered “Not now” to our invitation, so we ask you again at most every two weeks.
- Two-factor authentication. If you enrol an authenticator app, we store its secret in encrypted form and your recovery codes only as keyed hashes.
- Sessions. For each browser you are signed in on, we keep the time it was created and last used, its user agent and its IP address, so you can review and sign out your sessions in Settings and so we can protect your account.
- Pictures from other servers. Event and venue images, and profile pictures from Google or Discord, load in the web app directly from the servers that host them, which receive your IP address as with any request.
- Organisations and invitations. When someone invites you to an organisation, we process your email address, the role offered and who invited you. Within an organisation, an audit log records security-relevant actions (for example inviting a member or creating an API key) with the member who performed them and their IP address; the organisation’s owners and admins can read it.
API keys and usage
For each API key we keep its name, scopes, optional IP allowlist and expiry, and the time and IP address of its last use. The secret part of a key is never stored, only a keyed hash of it. We count API requests per minute for each organisation, key and group of endpoints, to enforce plan quotas, bill usage where your plan includes it and show you your usage.
Notifications you set up
If you add a notification channel — an email address, a Discord, Slack, Microsoft Teams or Google Chat webhook, a Telegram chat, a browser push subscription or a webhook endpoint of your own — we store its details in encrypted form and send alert messages there when your alert rules fire. The service you send them to (for example Discord, Slack, Telegram or your browser vendor’s push service) handles them under its own terms. We keep a log of alert firings and webhook deliveries so you can see what was sent.
If you turn on notifications in the iOS app, we store the device token Apple issues for your iPhone or iPad, and the environment it belongs to, in encrypted form, and send alerts to it through Apple Push Notification service. The token belongs to you and to the signed-in session of the app that registered it. The app deletes it when you turn notifications off in its Settings. When you sign out, we stop sending notifications to it, because it is tied to that session; it is deleted when you leave the organisation or delete your account.
If an organisation adds our Slack app to a Slack workspace or links a Discord server to use our bot’s commands, we store the workspace or server and channel identifiers, for Slack the app’s access token in encrypted form, and the identifier and display name of the Slack or Discord user who links their account or connects the server, so that commands and alerts reach the right organisation.
Payments
Subscriptions are paid through Stripe. When you start a checkout, we give Stripe the email address of the person paying, the organisation’s name and our internal identifiers. You enter your payment details on Stripe’s own pages; we never see or store your card number. Stripe tells us the subscription’s plan, status, number of seats and billing period.
We issue VAT invoices through FakturaXL, an invoicing service, using the buyer’s name, address, tax identification number and email address, and email the buyer a link to each invoice. Where Polish law requires it, the invoice is also sent to the National e-Invoice System (KSeF) run by the Polish Ministry of Finance. Invoices and payment records are kept for as long as tax and accounting law requires.
Emails we send
We send transactional emails only: sign-in links with their one-time codes, organisation invitations, VAT invoices and the alert emails you set up. Stripe sends receipts and billing notices. We do not send newsletters or marketing emails. If you signed in with Apple using “Hide My Email”, we send these emails to your private relay address and Apple forwards them to you.
Writing to us
If you email us, we process your address, your name if you give it, and the content of the correspondence, to answer you and to handle whatever the message is about.
Error reports
When the web app or our servers hit an error, a report is sent to an error tracker we host ourselves. Reports are built to leave personal data out: they carry no user identity, cookies, request bodies or query strings, email addresses in them are masked, and the only request header kept is the browser’s user agent.
Exports
Files you export (CSV or JSONL) are kept on our servers for 7 days so you can download them, through links that are valid for 15 minutes.
Legal bases
We process personal data under the GDPR, specifically:
- Art. 6(1)(b) — performing the contract with you, and steps taken at your request before entering into it: your account, sign-in, the features of your plan, notifications you set up, billing and support.
- Art. 6(1)(f) — our legitimate interests, and those of our customers: providing the Service to the members a customer invites to its organisation, keeping the Service and accounts secure (sessions, audit log, rate limits, error reports), measuring API usage, delivering the website, answering correspondence, and establishing, exercising or defending legal claims.
- Art. 6(1)(a) — your consent: Google Analytics and Google Ads on the website and the docs, and the cookies they set. You can withdraw consent at any time; withdrawal does not affect the lawfulness of what happened before it.
- Art. 6(1)(c) — legal obligations, above all tax and accounting rules for invoices and payments.
Providing your email address is necessary to have an account. Everything else in your profile is optional.
How long we keep data
| Data | How long |
|---|---|
| Sign-in links and codes | Deleted one day after they expire (they are valid for 15 minutes). |
| Sessions | 30 days from last use, then deleted 30 days after they expire or you sign out. |
| Invitations | Valid for 7 days; deleted 30 days after they expire. |
| Audit log | For the life of the organisation. If a member’s account is deleted, the entries remain without a link to that person and without their IP address. |
| API usage counters | 400 days. |
| Alert firings and deliveries | 90 days. |
| Webhook delivery logs | 30 days. |
| Exports | 7 days. |
| Payments and invoices | As long as tax and accounting law requires, generally five years from the end of the year in which the tax became due. |
| Correspondence | While the matter is open, then for as long as claims could arise from it — generally no longer than three years from our last contact. |
| Server logs | Rotated automatically by size; kept only as long as they are needed to run and secure the Service. |
| Backups | Database backups roll over within about three months, after which deleted data is gone from them too. |
| Your cookie choice | In your browser until you change it or clear your browser data. |
| Google Analytics | Event-level data is retained by Google for 14 months, aggregated reports for longer. |
You can delete your account yourself at any time in Settings → Privacy in the web app, or ask us to do it by writing to [email protected] from the address the account uses. If you are the only owner of a team organisation that has other members, transfer ownership or remove them first. If an organisation that would be deleted with your account has a subscription, cancel it in Settings → Billing first; deleting the account then ends it at once, without a refund for the rest of the period.
Who we share data with
We do not sell personal data for money, and we do not disclose it for purposes not described here. The Service runs on servers we operate ourselves; the database, exported files and backups are held there. We use the following providers, which process data on our behalf under data processing agreements:
- Cloudflare, Inc. — delivery and protection of all our domains (traffic passes through Cloudflare encrypted, and Cloudflare terminates the HTTPS connection), and, where we use it, storage of backup copies that are encrypted before they leave our servers.
- Stripe Payments Europe, Ltd. — payment processing and subscription billing. Stripe is also an independent controller for some processing, such as fraud prevention, under its own privacy policy.
- Resend, Inc. — sending sign-in, invitation, invoice and alert emails.
- Google Ireland Limited — Google Workspace (our own email), Google sign-in if you choose it, and, with your consent, Google Tag Manager, Google Analytics and Google Ads.
- FXL Sp. z o.o. (Bielsko-Biała, Poland) — FakturaXL, the service we issue VAT invoices with.
If you sign in with Discord, Discord Inc. processes your sign-in under its own terms; the same applies to Google sign-in and to Sign in with Apple, which Apple processes under its own terms. Notifications to the iOS app are delivered through Apple Push Notification service, so Apple receives your device token and the notification’s text. Invoices are sent to the Polish tax administration through KSeF where the law requires it. Data may also be disclosed to public authorities entitled to it under the law, if they request it.
Transfers outside the European Economic Area
Cloudflare, Stripe, Resend and Google are part of groups headquartered in the United States, so data may be transferred outside the EEA. Each of them is certified under the EU–US Data Privacy Framework, the European Commission’s adequacy decision for the United States; where a particular transfer is not covered by it, it is based on the Commission’s standard contractual clauses. You can ask us which mechanism applies to a given provider.
Cookies and local storage
Cookies are small files a website stores in your browser. Polish law (Art. 399 of the Electronic Communications Law) and the GDPR allow them to be stored only after you have been told what they are for and have agreed, unless they are necessary to provide the service you asked for. The same applies to local storage.
On the website and the docs
Our own pages set no cookies. They store a few entries in your browser’s local storage, which are never sent to our servers. Google’s cookies are set only after you allow the corresponding purpose:
| Name | Purpose | Set by | Lifetime | Requires |
|---|---|---|---|---|
s302-consent |
Remembers your cookie choices (local storage) | status302 | Until you change or clear it | Nothing — necessary |
starlight-theme |
Remembers the docs’ light or dark theme, if you pick one (local storage) | status302 | Until you clear it | Nothing — necessary |
scalar-reference-auth |
Keeps the API key you enter in the API reference to try requests, so a reload keeps it (local storage) | status302 | Until you clear it | Nothing — you enter it |
_ga, _ga_* |
Distinguishes visitors and sessions in Google Analytics | 2 years | Analytics consent | |
_gcl_au |
Measures the effectiveness of Google Ads campaigns | 3 months | Advertising consent |
Until you choose, both purposes are treated as refused. You can change or withdraw your choice at any time with Your privacy choices in the footer of every page (on the API reference, in its top bar); withdrawing a purpose also deletes the Google cookies set for it. If your browser sends a Global Privacy Control signal, we treat it as a refusal of the advertising purpose and do not offer it while the signal is on.
In the web app and the API
The web app uses only what it needs to work. It sets no analytics or advertising cookies:
| Name | Purpose | Lifetime |
|---|---|---|
status302_session |
Keeps you signed in (cookie, HttpOnly) | 30 days, renewed while you use it |
status302_csrf |
Protects your account against cross-site request forgery (cookie) | 30 days |
status302_magic |
Ties an emailed sign-in link to the browser that asked for it (cookie, HttpOnly) | 15 minutes |
status302_oauth |
Protects a Google or Discord sign-in in progress (cookie, HttpOnly) | 10 minutes |
status302:theme |
Your light or dark theme (local storage) | Until you clear it |
status302:recent-searches |
Your last searches in the command palette (local storage) | Until you clear it |
status302:feed-notify |
Your sound and desktop notification settings for the live feed (local storage) | Until you clear it |
status302.billingBanner.dismissed |
Hides a billing notice you dismissed (session storage) | Until you close the tab |
All of these are necessary for a feature you use, so they need no consent. You can delete cookies and block new ones in your browser’s settings — the browser decides the conditions under which information is stored on your device — but without the session cookie you cannot stay signed in.
Profiling and automated decisions
We do not make decisions about you that produce legal or similarly significant effects by automated means. Google may use the advertising data described above to personalise ads, but only if you have allowed the advertising purpose.
Your rights
In connection with our processing you have the right to:
- access your data and receive a copy of it,
- have inaccurate data corrected and incomplete data completed — your name and profile picture you can change yourself in Settings,
- have your data erased, including your whole account, where we have no basis to keep processing it,
- restrict processing,
- receive the data you gave us in a portable format and have it transmitted to another controller,
- object to processing based on our legitimate interests,
- withdraw consent at any time, without affecting the lawfulness of processing before the withdrawal.
You can exercise two of them yourself in Settings → Privacy in the web app: Download your data gives you a copy of the personal data your account holds as a JSON file, and Delete account erases your account as described under “How long we keep data”. For anything else, or if you prefer, write to [email protected]. We respond without undue delay and at the latest within one month; where a request is complex, we may extend that by up to two further months and will tell you why within the first month.
If you believe we process your data unlawfully, you have the right to lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl, or with the supervisory authority of the EU member state where you live or work.
Additional information for residents of US states
This section applies if you live in California or in another US state with a comprehensive privacy law (such as Colorado, Connecticut, Oregon, Texas, Utah or Virginia), and supplements the rest of this policy. It uses the terms those laws use.
What we collect. In the past 12 months we have collected these categories of personal information, from the sources and for the business purposes described above:
- Identifiers — your name, email address, account and provider identifiers, IP address and, on the website with your consent, Google’s online identifiers. Sources: you, your browser, Google or Discord sign-in, and the organisation that invites you.
- Commercial information — your organisation’s plan, subscription and invoices. Sources: you and Stripe.
- Internet or other electronic network activity — sessions, user agents, API usage, the organisation audit log and, with your consent, website analytics. Source: your browser and your use of the Service.
- Approximate location — derived from your IP address by Google Analytics, only with your consent. We do not collect precise geolocation.
- Professional information — the organisations you belong to and your role in each.
We do not collect sensitive personal information as these laws define it, and we do not draw inferences about you to create a profile.
Disclosure, sale and sharing. We disclose the categories above to the service providers listed under “Who we share data with”, for the purposes described there. We do not sell personal information for money. If you allow the advertising purpose on our website, Google’s advertising cookies and the data they collect may count as “selling” or “sharing” personal information for cross-context behavioural (“targeted”) advertising under these laws. This happens only with your opt-in, never in the web app or the API, and you can opt out at any time with Your privacy choices on any page of the website. We honour Global Privacy Control as a valid opt-out of sale, sharing and targeted advertising. We do not knowingly sell or share the personal information of anyone under 16. We do not disclose personal information to third parties for their own direct marketing (California Civil Code § 1798.83).
Your rights. Subject to the exceptions in your state’s law, you have the right to know what personal information we collect, use and disclose and to receive a copy of it in a portable format; to have it deleted; to have inaccurate information corrected; and to opt out of its sale, of sharing for cross-context behavioural advertising, of targeted advertising and of profiling with legal or similarly significant effects (we do not engage in such profiling). We will not discriminate against you for exercising any of these rights.
How to exercise them. Use Download your data and Delete account in Settings → Privacy, Your privacy choices on the website, or write to [email protected]. Requests made while signed in are verified by your session; for emailed requests we verify that you control the email address of the account, and may ask for further information if needed. You may use an authorised agent: we will ask for your signed permission and may ask you to verify your identity directly. We confirm receipt within 10 business days and respond within 45 days, which we may extend by a further 45 days where reasonably necessary, telling you so.
Appeals. If we decline your request, you may appeal by replying to our decision or writing to [email protected] with “Appeal” in the subject. We answer appeals within 45 days. If you are not satisfied, you may contact your state’s Attorney General.
Do Not Track. Browsers’ “Do Not Track” setting has no agreed meaning, so we do not respond to it; we honour Global Privacy Control instead, as described above.
Security
The Service is available over HTTPS only. Session tokens, sign-in links and API key secrets are stored only as hashes; authenticator secrets and notification channel details are encrypted; our servers’ disks are encrypted. Access to the systems and provider accounts that hold personal data is limited to the people who need it for the purposes above. You can protect your own account further with two-factor authentication and by reviewing your active sessions in Settings.
Children
The Service is intended for businesses and is not directed at anyone under 18. We do not knowingly collect data from children. If you believe a child has given us personal data, let us know and we will delete it.
Links to other sites
The Service links to and shows content from sites run by others, including the ticket marketplaces its data describes. Their processing is governed by their own policies.
Changes to this policy
We will update this policy when the Service, the providers we use or the applicable law change. The date of the last update is shown at the top of the page; if a change affects how we use the data of existing account holders, we will also tell them by email or in the app. The policy’s canonical location is https://status302.com/privacy-policy/.