Privacy notice
How DueReason handles personal data: what we process as controller and as processor, why, for how long, who helps us, and how to use your rights.
Last updated
Operator
- Company
- Override Technologies
- hello@duereason.com
In this notice, "we" are the operator of DueReason named at the top of this page, and "the service" is DueReason at duereason.com: the console, the REST API and MCP endpoint, the worker portal and these public pages. This notice follows Articles 13 and 14 of the General Data Protection Regulation (EU) 2016/679 (GDPR).
Two roles
DueReason holds two kinds of personal data, and our role is different for each.
- We are the controller for data about the people who visit this website and use the service: accounts, sign-in security, billing, contact requests, in-app feedback and the technical operation of the service. Most of this notice is about that data.
- We are a processor for the data our customers put into DueReason or produce with it: approval requests, their payloads, answers, comments and evidence submitted by the customer, and the customer's audit log. If an organization enables DueReason's platform-work module, this can also include records about workers and other people affected by its decisions, statements of reasons and reviews. If it enables the DSA notice-and-action module, this can also include DSA notices. The customer (the organization that uses DueReason) is the controller of that data and decides what it is used for. We process it only on the customer's instructions, under our data processing agreement.
If a customer keeps data about you in DueReason (for example, you work through a platform that uses it, you are named in an approval request, or you sent a DSA notice), the customer's own privacy notice applies. See If a customer holds your data below.
What we process as controller, and why
| Data | Purpose | Legal basis |
|---|---|---|
| Account: name, email address, password (stored only as a salted hash), language, memberships and roles in organizations, invitations | Providing the service your organization uses, signing you in, sending account emails (confirmation, password reset, invitations) | Art. 6(1)(b) GDPR where you are our customer; otherwise Art. 6(1)(f), our legitimate interest in providing the service your organization has ordered |
| "Continue with Google" sign-in, if you choose it instead of a password: the name, email address and whether Google says that address is verified, and a profile picture URL (stored as your account's avatar) that Google gives us; the Google account id and the access token (and, if Google issues one, a refresh token) our sign-in library stores to keep the connection working | Creating or signing in to your account without a separate password | Art. 6(1)(b) GDPR where you are our customer; otherwise Art. 6(1)(f), as for the account row above |
| Two-factor authentication: the authenticator secret and single-use backup codes, if you turn it on | Protecting your account | Art. 6(1)(b) or (f) as above, and Art. 32 GDPR |
| Sessions: IP address, browser (user agent), times | Keeping you signed in and letting you see and end your sessions | Art. 6(1)(b) or (f) as above |
| Authentication events: sign-up, sign-in (successful or failed, with the reason), sign-out, password reset and change, email confirmation and two-factor events, with the email address used, IP address, browser and time | Detecting and investigating attacks on accounts and locking sign-in after repeated failures | Art. 6(1)(f): our legitimate interest in keeping accounts secure; Art. 32 GDPR |
| Billing, where an organization pays by card through the service: its Stripe customer and subscription identifiers, plan, status and billing period | Running the subscription | Art. 6(1)(b); keeping invoices and accounting records: Art. 6(1)(c) |
| Contact requests: name, work email, company, topic, message, language and the time you agreed | Answering you and preparing a pilot or a demo | Art. 6(1)(a): your consent, which you can withdraw at any time |
| Where a request came from: for a contact request, a newsletter sign-up, a sandbox start or a sign-up, the campaign tag from the link you followed (if any) and the referring website's domain (if any) — never a cookie, never linked to your name, email or account | Measuring which channels bring people who ask to talk to us, so we can tell which ones are worth repeating | Art. 6(1)(f): our legitimate interest in understanding our own marketing |
| Product newsletter: email address, first name, language, subscription status, and the consent record (date, source, wording version, and the IP address and browser used at the time of consent) | Sending DueReason product news | Art. 6(1)(a) GDPR and Art. 398 of the Polish Law on Electronic Communications (Prawo komunikacji elektronicznej): your consent, which you can withdraw at any time — the unsubscribe link in every newsletter email, the toggle in account settings, or the unsubscribe page |
| In-app feedback: the kind (bug, idea, question, praise), your message, the page and, where the page set one, the feature it was about, language, your account (if signed in) and email address only if you tick "you may contact me about this" | Reading and acting on feedback about the product | Art. 6(1)(f): our legitimate interest in improving the service; Art. 6(1)(a) for the email address, which is given only with your consent |
| Browser notifications, if you turn them on: the push address and keys of that browser, and its name | Telling you that an approval is waiting for you | Art. 6(1)(b) or (f) as above |
| Correspondence with us by email | Answering you and keeping a record of what was agreed | Art. 6(1)(b) or (f) |
| Technical logs: when an error occurs, the error, the page or API path (without its query string) and the time; database errors without the query or its values | Running the service, finding and fixing faults, security | Art. 6(1)(f): our legitimate interest in a working, secure service |
| Website statistics, where enabled: page views counted by Umami, which we host ourselves, without cookies and without storing IP addresses; visitors who send Do Not Track are not counted | Learning which pages are read | Art. 6(1)(f): our legitimate interest in improving the website |
| Cloudflare Turnstile, on the sign-up, sign-in and password-reset forms: your IP address and the browser/device signals Cloudflare's widget reads to tell a person from a bot (never the contact form or the in-app feedback form, which carry no bot check) | Stopping automated abuse of sign-in | Art. 6(1)(f): our legitimate interest, and our customers', in keeping accounts secure |
The public forms (this site's contact form and customers' DSA notice forms) turn your IP address into a keyed hash to limit how many messages one address can send in ten minutes. The address itself is not stored, and the counters are deleted within the hour.
You do not have to give us any data to read this website. Without an email address and a password we cannot create an account, and without a name, an email address and a message we cannot answer a contact request.
We do not make decisions about you based solely on automated processing, we do not sell personal data, and we do not use it for advertising.
The product newsletter carries no open or click tracking: we do not record whether, or when, you opened a newsletter email or followed a link in it.
Cookies
We use only the cookies the service needs to work. There are no advertising, tracking or analytics cookies, and because every one of them is strictly necessary for the service you asked for, we do not need your consent to set them (Art. 399(3) of the Polish Law on Electronic Communications, implementing the ePrivacy Directive's Art. 5(3) exemption for strictly necessary cookies) and show no cookie banner.
| Cookie | Purpose | Lifetime |
|---|---|---|
better-auth.session_token (__Secure-better-auth.session_token over HTTPS) | Keeps you signed in | 14 days, renewed while you use the service; removed when you sign out |
better-auth.two_factor | Remembers, between the password and the code, that the password was correct | Up to 10 minutes |
better-auth.state (__Secure-better-auth.state over HTTPS) | Protects the redirect to and from Google against forgery while you sign in with "Continue with Google" | Up to 5 minutes, removed once you return from Google |
locale | Remembers the language you chose, or that you opened the Polish pages | One year |
Cloudflare Turnstile, the bot check on sign-up, sign-in and password reset, runs in an iframe served from Cloudflare's own domain and does not set any cookie on duereason.com; any cookie it uses belongs to Cloudflare and is covered by its own policy.
How long we keep it
| Data | Kept |
|---|---|
| Account | As long as the account exists. You cannot yet delete an account yourself: write to us and we delete it within one month, unless you still own an organization (delete or hand over the organization first) |
| Sessions | Valid for 14 days without use; ended when you sign out, reset your password or the account is deleted |
| Authentication events | 400 days (a year of history and a month's margin), then deleted automatically. They are kept for that period after an account is deleted, as the record of attempts to get into it |
| Emails that belong to no organization (password resets, confirmations, contact request notifications) | The delivery record is deleted 30 days after sending |
| Contact requests | 12 months, then deleted automatically; sooner if you ask or withdraw your consent |
| Where a request came from | 13 months, then deleted automatically |
| Product newsletter | Kept while you stay subscribed; a sign-up left unconfirmed for 30 days is deleted automatically; once you unsubscribe, we keep only the address, status and dates as a do-not-contact record, as proof of your consent and withdrawal (Art. 6(1)(f)) |
| In-app feedback | 12 months, then deleted automatically; sooner if you ask |
| Browser notifications | Until you turn them off in that browser, the push service reports the browser gone, or the account is deleted |
| Billing | Subscription records as long as the organization exists; invoices and accounting records as long as tax law requires (in Poland, five years from the end of the year in which the tax was due for payment) |
| Technical logs | On our own monitoring system, only as long as needed to find and fix faults |
| Backups | Hourly database backups are kept 48 hours and one a day 14 days on our servers; a continuous point-in-time archive of the database is kept 14 days in Contabo Object Storage in the EU; an encrypted off-site copy is locked against deletion for 14 days and then removed. Deleted data therefore leaves every backup within 17 days |
For the data we process for customers, the customer sets the retention: closed approval requests with their answers and evidence, closed decisions and idle worker contacts are deleted after a period the customer chooses between 24 and 120 months (72 by default), and a customer can delete its whole organization at any time. Details are in the data processing agreement.
Who receives it
Our own staff, only as far as their work needs it, and the service providers that process data for us under a data processing agreement: hosting in Germany, email delivery, card payments, file storage in Amsterdam, and the bot check on our sign-in forms. The current list, with locations, is on the subprocessors page.
Some recipients are chosen by a customer or by you, not by us:
- If a customer connects Slack or Microsoft Teams, notifications about its approval requests (the request title, the action, the step or the outcome and a link; never the payload, the reason, comments, evidence or anyone's name or email address) go to that customer's workspace. Webhooks go to addresses the customer sets.
- If you choose "Continue with Google" to sign in, Google receives your request directly as an independent controller you chose, under its own privacy policy, not on our instructions; we only receive back what the account row above lists.
- If you turn on browser notifications, the push service of your browser (Apple, Google, Mozilla or Microsoft) delivers them. The content is end-to-end encrypted; the push service sees only the address, size and time.
We disclose data to public authorities only where the law requires it.
Transfers outside the EEA
The service and its database are hosted in Germany, and we do not intend to transfer personal data outside the European Economic Area. A transfer can happen only through providers named on the subprocessors page that are based in, or use companies in, the United States (email delivery, card payments, file storage, the sign-in bot check), and through recipients a customer or you choose (Slack, Microsoft Teams, Google when you sign in with it, browser push services). Such transfers rely on the European Commission's adequacy decision for the EU-US Data Privacy Framework, for certified recipients, or on the Commission's standard contractual clauses. You can ask us for a copy of the safeguards.
Security
All connections to the service are encrypted (HTTPS). Passwords are stored only as salted hashes, two-factor authentication is available to everyone and can be required by an organization, and sign-in is locked for 15 minutes after five wrong passwords. Permissions are checked on the server for every request. The audit log and the authentication events cannot be changed after they are written, and approvals and decisions are recorded on hash chains that are verified regularly. The full list of measures is in the annex of the data processing agreement.
Your rights
You have the right to access your data (Art. 15 GDPR), to have it corrected (Art. 16), erased (Art. 17) or restricted (Art. 18), to receive it in a portable format (Art. 20), and to object to processing based on our legitimate interests (Art. 21). Where we rely on your consent, you can withdraw it at any time, without affecting what was done before.
To use a right, write to the email address at the top of this page. We answer within one month, and may ask you to confirm your identity first.
You can also complain to a data protection authority: in Poland, the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl), or the authority where you live or work.
If a customer holds your data
A customer that keeps data about you in DueReason is its controller, and you exercise your rights with the customer:
- People named in an approval request or shown in evidence (for example, a payee on a payment request) contact the organization that asked for the approval.
- Workers of a platform, if the organization enables the platform-work module, receive each statement of reasons through a personal link (the worker portal). There you read the statement and the name of the contact person, and you can ask for a human review, without an account. Questions about your data go to that contact person or to the platform.
- People who sent a DSA notice, if the organization enables the DSA notice-and-action module, contact the organization that received it.
If you write to us about data a customer holds, we pass your request to that customer without delay and help it answer. We cannot decide about the customer's data ourselves.
Changes
We update this notice when the service or the law changes; the date at the top shows the latest version. We tell account holders about material changes by email before they take effect.
Contact
Write to the email address at the top of this page, or use the contact form.