How your data stays yours.
Duqo collects what it needs to remind you of things. We never sell your data. You can export it or delete your account from Settings, without asking us.
Who we are and what this covers.
Duqo is operated by Duqo, Inc., a Delaware corporation (“we,” “us,” “our”), which is the data controller for the information described here. This policy covers the Duqo iPhone app, the web app at app.duqo.app, and the website at duqo.app.
Duqo works by holding onto your commitments and following up on them, so it necessarily holds the content of those commitments: your tasks, your messages to it, and the timing patterns it uses to decide when to reach you. This policy says where that data goes, how long it stays, and what you can do about it.
What Duqo collects.
Account Information
Email address and name
Collected when you sign up with email, Google Sign-In, or Sign in with Apple. Used to authenticate you, run your account, and send service messages.
Password
If you sign up with email, your password is hashed and we cannot read it. If you use Google or Apple, we store the account identifier they give us and never see a password.
Your Content
Tasks and reminders
Titles, notes, dates, deadlines, priorities, recurrence, subtasks, and whether something is done.
Chat and conversation history
Messages you exchange with Duqo, and the replies it sends you. Kept so the conversation makes sense next time.
Photos you send to chat
If you attach a photo, the full image is sent to our AI provider to read it and held briefly in temporary storage to complete that request. A small compressed thumbnail stays attached to the message in your history so the chat still makes sense when you scroll back.
Voice input
Speech is turned into text on your own device or in your browser. The audio never reaches our servers — only the resulting text, treated the same as anything you type. On iPhone, transcription uses Apple’s speech recognition, which may process audio on Apple’s systems under Apple’s privacy policy.
Voice calls
When you call Duqo from the iPhone app, your phone sends the call audio directly to OpenAI, which transcribes it and speaks the reply. The audio does not pass through our servers and we never keep a recording. What we store is text: the transcript joins your chat history, together with a summary of what the call changed and the start time, length, and outcome of the call.
How You Use Duqo
Activity and timing patterns
When you complete things, when you reply, and which reminders land. This is what lets reminder timing improve instead of staying generic.
Feature usage counts
A per-day count of how many times you use metered features such as AI chat, stored with the date and the timezone the day was counted in. This is what enforces plan allowances and tells us what the Service costs to run.
Safety records
If an automated check flags a message as abusive or unsafe, we keep a short excerpt of it with the reason, so the same pattern can be recognised again.
Settings and Device Information
Preferences
Timezone, language, notification settings, quiet hours, check-in time, and your AI feature choices, including when you agreed to AI processing.
Device tokens
Identifiers used to deliver push notifications to your devices. You can unregister a device at any time.
Approximate country
Cloudflare provides a country code inferred from your network location so the pricing page can select a regional price by default. You can change the displayed schedule, and Duqo does not store this country code for pricing.
Purchase and subscription information
The product purchased, trial or subscription status, purchase and renewal dates, App Store transaction or receipt identifiers, and an anonymous or Duqo account identifier used to restore access across devices. RevenueCat may also process basic device and operating system information needed to validate purchases. We never receive your payment card details.
Calendar Data (Optional)
If you connect a calendar, we read event titles, times, attendee counts, and free/busy status so reminders avoid your existing commitments. See Calendar Integration for what we can and cannot do with it.
Put to work for your reminders.
We use what we collect to:
- Run your account and sign you in
- Store and show your tasks, notes, and reminders
- Decide when to remind you, and send the reminder
- Answer you in chat, read photos you send, and turn what you write into tasks
- Keep your data in sync across your devices
- Schedule around your calendar, if you have connected one
- Learn your patterns over time so the timing gets better rather than staying generic
- Apply your plan’s allowances, and handle subscriptions and purchases
- Send service and security messages
- Keep the Service working, and prevent abuse of it
Our legal grounds. Most of this is because we need it to give you the service you asked for. Keeping the Service reliable, preventing abuse, and understanding what features cost rest on our legitimate interests. AI processing of your content rests on your consent, recorded when you accept it, and you can stop it by turning AI features off or closing your account. Where we must keep records for tax or accounting, the ground is our legal obligation.
Automated decisions. Duqo decides when to contact you automatically, using your tasks, deadlines, past responses, and calendar. It affects the timing and wording of reminders and nothing else — no decision about you is made that has legal effect. You can turn reminders off, change quiet hours, or set exact times yourself, and you can ask us to review any automated outcome.
We do not use your personal information for advertising. We do not sell, rent, or trade it.
AI is built in.
What is sent, and to whom. To answer you or decide when to remind you, Duqo sends the relevant content — your message, the tasks in question, and any photo you attached — to our AI providers, Anthropic and OpenAI, over encrypted connections. They return a response and we act on it. That is the only reason your content leaves our systems for them.
Your content is not used to train AI models. Under the API terms we use, Anthropic and OpenAI are not permitted to train models on data we send them, and we do not train models on your content either.
They may hold it briefly. Being barred from training is not the same as keeping nothing. Under their current API terms these providers may retain what we send for a limited period — up to 30 days at the time of writing — to monitor for abuse and to meet their own legal obligations, then delete it. Content they flag as unsafe may be kept longer under their policies. We do not control those windows.
Voice calls. A call is the one place your audio leaves your device. When you call Duqo from the iPhone app, your phone opens a direct connection to OpenAI and streams the call audio there; OpenAI transcribes what you say and generates the spoken reply. That audio never passes through or is stored on our servers, and we never keep a recording. We identify the call to OpenAI with a hashed identifier rather than your account details. The retention and no-training terms above apply to what it processes. What we save is text: the transcript joins your chat history like a typed message, with a summary of what the call changed.
Memory. Duqo may save durable facts and preferences it learns from your conversations as “memories,” and use them to personalise later replies and timing. They belong to your account and are never shared with other users. You can read, correct, or delete any of them on the Memory screen.
What your plan changes. Some AI features are part of Duqo Pro. On the free plan those features do not run, which means less of your content is processed — for example, memories are not created or used to personalise, and calendar-aware planning does not happen. Existing memories stay readable and deletable either way.
Your calendar stays yours.
Connecting a calendar is optional. It exists so reminders land between your commitments instead of on top of them.
What we can access
- Read access to your events — titles, times, attendee counts, free/busy status — to understand your schedule
- Write access limited to a calendar Duqo creates. We ask Google only for permission to manage the “Duqo” calendar we make ourselves
How calendar data is used
- To show your schedule alongside your tasks
- To avoid reminding you during a meeting or busy block
- To suggest times that are actually free
- To give the AI assistant enough context to schedule sensibly
Your control
- Connecting requires your explicit consent through Google, and you can disconnect at any time in Settings
- When you disconnect, we stop syncing, delete the calendar events we had synced, and delete the connection along with the access token we held
- Disconnecting does not itself withdraw the permission at Google. To remove it there as well, visit your Google account permissions. Deleting your Duqo account withdraws it for you
- On iPhone, Duqo can instead read your device calendar with your permission. It stores only event titles, times, and the calendar name, and you can revoke it in iOS Settings
Duqo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Who else sees what.
These companies process data on our behalf. Each receives only what its job requires.
Anthropic and OpenAI
AI providers. Receive the task content, messages, and photos needed to generate a reply or a schedule. Not permitted to train models on it. See AI Features.
Google Sign-In
Authentication. Receives nothing from us; gives us your email and profile name if you choose it.
Google Calendar
Optional calendar sync. Read access to your calendars, write access only to the calendar Duqo creates.
OpenAI Realtime
Voice calls. Receives the call audio directly from your phone, transcribes it, and speaks Duqo's reply. We never receive or store a recording. See AI Features.
ElevenLabs
Voice generation. Receives the text of a reply when Duqo speaks it aloud. Never receives your recordings.
Firebase Cloud Messaging
Push notification delivery. Receives device tokens and the content of the notification.
Apple App Store & RevenueCat
Subscription processing. Apple takes the payment. RevenueCat validates App Store purchase and receipt data and tracks subscription status for us, along with an account identifier so access can be restored across devices. We do not send payment card details to RevenueCat, and Apple does not share them with us.
Sentry
Error monitoring. Error reports may include your user ID, email, and IP address so we can reproduce what broke for you.
PostHog
Product analytics. We count visits and measure which parts of a page are clicked and scrolled to. In the UK and the European Economic Area we ask first, and store nothing on your device unless you allow it. Elsewhere that storage is on by default: an analytics identifier in your browser, and a recording of how pages on this site are used, with anything you type hidden. Privacy choices in the footer changes this at any time. In the apps, analytics and session recording are linked to your account, and text you type is hidden. Your conversations with the AI are never sent to PostHog.
Hosting and infrastructure
Our servers run in Germany and our database is managed by PlanetScale. Cloudflare delivers this website and the web app, and processes network information to do it.
Resend
Transactional email. Receives your email address and the contents of the message we send you.
How long we keep it.
Most of your data is kept for as long as your account exists, because that is what makes Duqo useful over time. Where something is deleted on a schedule instead, here it is:
- Tasks, chat history, and memories are kept until you delete them or close your account. Two exceptions run automatically: observations Duqo inferred about you expire after about 90 days unless they are still relevant, and synced calendar events are removed about 30 days after they pass
- AI request records keep the text sent to and returned by the AI for 30 days, then that text is deleted. We keep the model name, token counts, and cost after that so we can track what the Service spends
- Error logs are kept for 90 days, and operational logs for around two weeks
- Calendar data is deleted when you disconnect the calendar or close your account
- Device tokens are removed when you unregister a device or close your account
When you close your account, we delete your account and the content attached to it — tasks, messages, memories, calendar data, devices, and the search indexes built from them — and we withdraw the calendar permission you gave Google. Residual copies in encrypted backups expire on our provider’s rotation, normally within 30 days.
Two things outlive the account, deliberately. We keep purchase and subscription records, and records of abuse or safety enforcement, because we need them for accounting, to handle refunds and disputes, and to stop someone from evading a ban by signing up again. These are kept no longer than those purposes require. Separately, Apple and RevenueCat may retain transaction records under their own policies where required for payment processing, fraud prevention, tax, disputes, or other legal obligations.
How we protect it.
Data is encrypted in transit and at rest. Passwords are hashed, so we cannot read them. Access to production data is restricted to the people who need it, credentials are never shipped in the app or the website, and sessions expire and can be revoked.
No system is perfectly secure. If a breach affects your data, we will tell you and the relevant authority without undue delay, and in any event within the time the law allows.
Your controls.
These rights apply to everyone who uses Duqo, wherever you live, and most of them are buttons rather than requests:
Access and export
Download everything in your account as a JSON file from Settings, on web and on iPhone.
Delete your account
Delete it yourself in Settings, on web and on iPhone. This is immediate and cannot be undone; see Data Retention for the two categories that survive it.
Correct what Duqo remembers
Read, edit, or delete any memory on the Memory screen. You can correct your name and preferences in Settings.
Turn off AI processing
Withdraw your consent to AI features in Settings. Duqo keeps working as a reminder app.
Disconnect your calendar
Disconnect in Settings at any time. Synced events are deleted.
Manage notifications
Control reminders, quiet hours, pauses, and registered devices in Settings.
Analytics choices
Use Privacy choices in this site’s footer for the website. In the apps, analytics currently follows the account and cannot be switched off separately — email us and we will exclude you.
You can also object to or ask us to restrict a particular use of your data, or ask for it in a portable form. Email legal@duqo.app and we will reply within 30 days. We will not treat you differently for exercising any of this.
If you think we have got it wrong, you may complain to the privacy or data protection regulator where you live. We would rather you told us first so we can fix it.
Not for children.
Duqo is for people aged 13 and over, or 16 and over in Europe. We do not knowingly collect data from anyone younger. If we learn that we have, we delete it. If you believe a child has given us their information, email legal@duqo.app and we will remove it.
Where your data lives.
Your data is stored on servers in Germany. Some of the companies in Third-Party Services process it elsewhere, mainly in the United States — our AI providers and error monitoring among them. That means your data crosses borders, including out of your country and out of the European Economic Area.
Where it does, we rely on the transfer terms in our agreements with those companies, which use the standard contractual clauses approved for this purpose, to hold them to the protections described in this policy.
When this changes.
We update this policy when what we do changes. If a change materially affects how we handle your data, we will tell you by email or in the app at least 30 days before it takes effect, so you have time to look at it and leave if you disagree.
The “Last updated” date at the top tells you when this was last revised.
Questions? Tell us.
For anything about this policy or your data, including any of the requests above:
- Operator
- Duqo, Inc.
- legal@duqo.app
- Website
- duqo.app