privacy

the short version

• What you write in init.Tasks is encrypted on your devices with a key we don't have. Our server stores ciphertext, ids and timestamps. The closed list of what it can see is below.
• If you connect an AI tool or another app, our server decrypts your data for that connection, and the app receives what it asks for within the access you gave it. You choose what to connect, and you can end a connection at any time.
• If you lose all your devices and your recovery key, we can't recover your data. Nobody can.
• We collect usage analytics about which features are used, never what you wrote. They are linked to your account.
• Nothing you write is shared with other people. init.Tasks has no shared lists and no public links.
• No ads, no data sold, no tracking across other companies' apps or websites.

---

what we collect

Where we say "the apps" we mean the iPhone, Mac and Android apps and the web app together, unless we single one out. Their widgets, the Mac menu bar and the share extensions are part of the apps.

website (inittasks.com, devs.inittasks.com)

Beta list. When you join the beta list we collect your email address, the platforms you picked, whether you asked for development updates, and the signup date. They are stored on our own server in the EU, where we also keep a log of each signup. Emails are delivered by Resend, which records deliveries, opens, clicks and bounces, and sends us a copy against your address.

Your IP address is used briefly to limit repeated signups and isn't stored with your email address.

Page analytics. inittasks.com and its blog use Umami, a cookieless analytics tool we run on our own server in the EU. It records the page, the referring site, your browser, operating system, device type, screen size and language, and an approximate location (country, region and city) worked out from your IP address. It doesn't store the IP address. devs.inittasks.com has no analytics.

Discord member count. The website shows how many people are in our Discord. Your browser asks discord.com for that number directly, so Discord sees the request as it would any visit.

the beta (Discord, TestFlight, Google Play)

If you join the beta through our Discord server, we store your Discord id and username, the email address and status for each platform you test on, any invite code, and your account id if you use a web invite. We use this only to run the beta. What you post on Discord is visible to the server, under Discord's terms.

To invite you, we give your email address to Apple (TestFlight) or Google (Google Play testing). They can give us crash reports, performance figures and feedback you send through them, under their own terms.

your account

You can use the iPhone, Mac and Android apps without an account, and everything then stays on that device. To sync between devices, use the web app, or connect the API, you create an account. There are three ways to do that:

• Email and password (all platforms): we store your email address and a secure hash of your password. We never store your password in plain text.
• Sign in with Apple (iPhone, Mac, web): we receive a stable identifier from Apple and, if you allow it, an email address (which may be an Apple private-relay address). We do not store your name.
• Sign in with Google (all platforms): we receive a stable identifier from Google and your email address. We do not store your name or picture.

For Apple and Google accounts we may also keep a token from them, used only to withdraw our access when your sign-in account is removed. Sign-in screens are run by Apple and Google under their own terms. The web app's sign-in page loads Apple's and Google's sign-in scripts from their servers, so they see that request.

One account for init.Tasks and init.Habits. Both are init.Made apps and share one sign-in account, and each keeps its own data. Deleting your account in init.Tasks removes your init.Tasks data and leaves init.Habits as it is (see "your rights").

Account emails. We send emails to verify your address and reset your password. They are delivered by Resend, with the same delivery, open and click records as above.

Sessions. Each signed-in session records the IP address it was created from, the country worked out from it, and the device, operating system or browser. You can see your sessions in settings › devices and sign any of them out.

your content: end-to-end encrypted

Everything you create in init.Tasks is encrypted on your device before upload, with AES-256-GCM and a key made on your first device. This covers to-dos, subtasks, projects, areas, headings, the inbox, notes and their versions, folders, note links, tags, filters, attachments and their names, dates, schedules, reminders, your settings, and your device names.

What our server can see. To sync and keep your account secure, our server sees these things, and no more of your content:

• your email address, how you sign in, and your sessions (above)
• that each item exists, its type, that it is yours, and when it was created, changed or deleted
• the size of each encrypted value and file, which roughly shows how long something is
• that two items share a tag or a saved filter, but not what it is
• how many devices you have and when each was last active, and a new device's name and platform while it is being added (up to 10 minutes)
• which apps and AI tools you connected, what each may access, and when each was last used
• the addresses of your webhooks
• where a device uses push, its push address and the times of its reminders and briefings
• while you use them, what link previews through our server and your connections need (below)

Your recovery key. When you set up encryption you get a recovery key, the only way back to your data if you lose every device. We store a copy of your encryption key that only the recovery key can open, and a short fingerprint to catch typos. If you lose all your devices and your recovery key, we can't recover your data. Nobody can. Resetting your password doesn't help, because your encryption key is separate from it. If you lose both, you can reset encryption, which deletes your content and starts again.

In the web app, encryption runs in your browser using code our server sends. That is as strong as our deployment is honest, the same limit every browser-based encrypted service has. If that matters to you, use the native apps.

If something is compromised. Change your encryption key in settings. Everything is re-encrypted, every API key and AI connection ends, and old copies of the key stop working.

files and attachments

Files you attach, and their thumbnails, are encrypted on your device with a key of their own before upload, and stored encrypted in Germany (Hetzner).

sharing

init.Tasks has no shared lists, no collaboration and no public links. Your content leaves your account only when you send it somewhere:

• when you connect an app or AI tool, or add a webhook (below)
• when you export your data, or share or download a file or a note through your device's share sheet or your browser. Those copies are not encrypted by us, and what happens to them is up to you and the app you send them to

on your devices

The apps keep a working copy on each device so they work offline. That copy isn't protected by init.Tasks' encryption, only by your device's own security, such as its passcode. Your encryption key stays in your device's secure storage and is never included in iCloud Keychain or device backups.

• Backups. The setting "include in backups" (on Android, "include in Google backups") controls whether that copy goes into your iCloud, Finder, Time Machine or Google backups. While it is on, your data is in those backups unencrypted by us. It is off by default while you are signed in, and on while you are signed out.
• Widgets. Widgets keep a small copy of the titles and counts they show on the device. On a locked iPhone you can hide them with the widget's setting.
• The web app. Your data is held in memory while the tab is open. Attachments may be cached in your browser, encrypted. The text of upcoming notifications is stored in your browser, unencrypted, so it can show them when the tab is closed.
• Things you share into init.Tasks wait on your device, unencrypted, until the app next opens and uploads them.
• Signing out removes your data and your key from that device. If a device is signed out from elsewhere or its session ends, this happens the next time it opens or reconnects.

permissions on your device

init.Tasks asks only when you use the feature that needs it. You can turn any of these off in your device's settings.

• Calendars. To show your events next to your tasks and in briefings. Events are read on your device, never sent to us, and never changed. Only which calendars to show and their colours syncs, end-to-end encrypted.
• Camera. To scan QR codes, and documents on iPhone. No image is sent except a scan you attach.
• Photos and files. Through the system's picker, only what you choose.
• Notifications. For reminders and briefings.
• Screen recording (Mac). Only for "take a screenshot" from the menu bar, of the area you pick.
• Clipboard. Read only when you paste.

Document scanner (Android). This is Google's scanner in Google Play services. It works on your device and Google states that images aren't sent to its servers, but it sends Google metrics about how the feature performs and is used.

link previews

When you save a link, init.Tasks shows the page's title and icon. The native apps fetch them from that website directly, so the website sees an ordinary visit from your device. The web app, and captures made through the API, ask our server to fetch them. Our server passes the title back and keeps neither the address nor the title.

reminders and briefings

The text of a reminder or briefing is written on your device, never by our server, and can appear on your lock screen depending on your settings. On iPhone, Mac and Android, reminders are scheduled on the device.

Push. The web app can ring while its tab is closed. Your browser gives us a push address and the times it needs waking. At those times our server sends a push with no title, no text and no id of anything of yours, through your browser maker's push service (Google, Mozilla, Apple or Microsoft). We remove the address when you turn notifications off, sign out, or delete your account, or once its session has ended.

API keys and AI connections

You can create API keys, and connect AI tools (such as Claude, ChatGPT or Cursor) or other apps through our API and MCP server. You approve each one from your own device and choose what it may access. Read-only is the default.

What happens to your data. An app can't read your encrypted data on its own. When you approve it, your device gives our server your encryption key, sealed for that connection, so our server can decrypt what each request needs and send it to the app. Decrypted data is held briefly in memory and never written to disk.

The app receives your data. What an AI tool reads goes to its provider, under its terms and privacy policy, not ours. It can also change or delete data if you gave it write access.

We store each connection's details, such as its name, what it may access and when it was last used, and log each request without its content. You can end any connection or key in settings at any time. API keys expire after the period you choose, at most a year, and AI connections have to be approved again at least once a year.

If you run our MCP server on your own computer, it acts as one of your devices and holds your key there. The AI tool you use it with still receives what it reads.

webhooks

If you set up a webhook, our server sends a short notice to your address when something changes: the kind of change, the id of what changed, and when. A webhook never contains your content. We store the address and its signing secret encrypted with our server's key, and a log of the last 100 deliveries for up to 30 days. The service at that address handles the notice under its own terms.

analytics in the apps

The apps send usage events to Aptabase, an analytics tool we run on our own server in the EU, in the same system as init.Habits but kept apart by app.

What is sent. Which pages and features are used, and how: for example that a to-do was completed from a widget, that a search returned 4 results, or how many projects you have (a daily summary of counts and settings). Also error codes, and sizes rounded into ranges.

What is never sent. The title or name of anything, the text of notes or descriptions, what you search for, links, file names, device names, your email address, the ids of your items, keys, or error messages. Each app drops any event that doesn't fit a fixed list, before it is sent.

What comes with every event. A random id for this install, the app version, the operating system and its version, the device model, your language, and which platform it is. While you are signed in, also your account id, the same one init.Habits sends, so we can see how one account uses our apps across devices. Our analytics server works out your approximate location (country and region) from your IP address and doesn't store the address.

This is pseudonymous, not anonymous: it is linked to your account. Deleting your account doesn't delete past events, and once your sign-in account is gone the id no longer points to anyone. You can object at any time by writing to hello@inittasks.com.

The apps contain no crash-reporting tool and no advertising or third-party tracking code. Crash reports you agreed to share with Apple or Google reach us through them.

server logs

Our web servers record each request, including the IP address, time, address requested and browser type. Our account system logs account events, such as a sign-in, with the IP address and browser type. We use these logs to keep the service secure and working.

---

why we collect

• Your email (website and beta) is used to send you beta invites, updates, and news about init.Tasks and other init.Made apps. You can unsubscribe at any time.
• Account data is used to provide your account, sync and the web app, and to send account emails.
• Your encrypted content is stored so it can sync between your devices.
• Session, device, connection, push and webhook data is used to keep your account secure and provide the features you set up.
• Logs and analytics are used to keep the service working, find problems and prioritise improvements.

---

legal basis

We rely on these legal bases under the GDPR:

• Contract (Art. 6(1)(b)): your account, sync, the web app, reminders, the API, MCP and webhooks, which are the service you signed up for.
• Consent (Art. 6(1)(a)): the beta list; the calendar, camera, notification and screen recording permissions your device asks you for. You can withdraw consent at any time.
• Legitimate interest (Art. 6(1)(f)): security (sessions, logs, rate limits), running the beta, website and app analytics, and understanding how init.Tasks is used. You can object at any time.

We are based in the Netherlands. This policy is written to meet GDPR requirements.

---

where your data is, and who helps us

Your account data, encrypted content and beta list are stored on our own server, hosted by Netcup in Nuremberg, Germany. Encrypted files and backups are stored with Hetzner in Germany. These companies host our systems. They can't read your content, which is end-to-end encrypted.

Where personal data goes outside the EEA, we rely on appropriate safeguards, such as the European Commission's Standard Contractual Clauses or the provider's participation in the EU–US Data Privacy Framework.

Apps and AI tools you connect, and the services behind your webhook addresses, are not our providers. You choose them, and they receive data on your instruction under their own terms.

We never sell your data and never use it for advertising.

---

payments

init.Tasks is free while it is in beta, and we collect no payment information. Before anyone is charged, we will update this policy to describe paid plans and the payment providers involved.

---

how long we keep it

---

security

Data is encrypted in transit (HTTPS/TLS), your content is end-to-end encrypted as above, passwords are stored only as secure hashes, and backups are encrypted. No system is perfectly secure, but we take reasonable technical and organisational measures. To report a security issue, write to hello@inittasks.com (see also inittasks.com/.well-known/security.txt).

---

your rights

Under the GDPR you have the right to access, correct, delete, restrict or object to the processing of your data, and the right to data portability. You can also withdraw consent at any time.

Access and portability. Because we can't read your content, you export it yourself: settings › data › export saves all of it, with your files, in an open format. For the other data we hold about you, write to us.

Deleting your data.

• To delete items, delete them and empty the trash.
• To delete everything in init.Tasks, use "delete account" in settings on any platform. This permanently removes your init.Tasks data, files, encryption data, devices, API keys, AI connections, webhooks and push addresses from our servers (backups rotate out as above). Your other devices remove their copy the next time they open or reconnect, and changes on them that hadn't synced are lost.
• Your init.Habits data and sign-in stay if you use init.Habits, and you could sign in again and start empty, with a new recovery key. Otherwise your sign-in account is removed too. Deleting your account in init.Habits doesn't delete your init.Tasks data. Your sign-in goes once you have deleted both.
• If you can't open the apps, write to hello@inittasks.com from your account's address and we will delete your account within 30 days.
• Sign out before you uninstall, because on iPhone and Mac deleting the app alone may leave its key or data on the device. To leave the beta list or the Discord beta records, which account deletion doesn't touch, use the unsubscribe link in any email or write to us.

Complaints. You have the right to lodge a complaint with your local data protection authority. In the Netherlands, that is the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl).

Automated decisions. We do not use your data for automated decision-making or profiling that produces legal or similarly significant effects.

Contact: hello@inittasks.com

---

children

init.Tasks is not directed at children. You must be at least 16 years old to use init.Tasks or create an account. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us personal data, contact us and we will delete it.

---

data controller

The data controller is Vladyslav Glogus, an individual operating init.Tasks (part of init.Made) from the Netherlands. For any privacy question or request, contact hello@inittasks.com.

---

changes

We may update this policy from time to time. When we do, we will update the date at the top of this page, and for material changes we will tell you in the app or by email before they take effect.

---

cookies

inittasks.com and devs.inittasks.com use no cookies. Your theme choice is stored in your browser and never sent to us.

The web app uses no advertising or tracking cookies, and none from other companies. It stores these in your browser:

• what it needs to work: your sign-in session, a device key that never leaves your browser, a small background script that shows notifications and, during the private beta, a cookie that remembers your access for up to a year
• your preferences, random ids for this browser (for push, note versions and analytics), and a list of file ids still to be removed from our server
• an encrypted cache of your attachments, and the text of upcoming notifications

Signing in with Apple or Google may set their own cookies on their own sites.