Privacy policy
The short version
- okoro works without an account. Then everything you keep stays on your device, and okoro has no copy of it.
- With an account, your days are kept on okoro’s server in the EU, so your devices can meet there.
- An account needs only an email address. No ads, no tracking, and nothing is ever sold.
- You can take everything with you, or delete your account, from Settings at any time.
Who is responsible
okoro is made by Edoardo Feuillardin, who is the controller of your personal data under the EU General Data Protection Regulation (GDPR). For anything about your data, write to hello@getokoro.com.
Using okoro without an account
Your tasks, events, notes, pictures, files, highlights and settings are kept in your browser’s storage on your device. okoro can’t see them. Only these leave your device:
- What okoro fetches for you. The sites you follow in Read, the articles you open and the calendars you subscribe to are fetched by okoro’s functions, so the sites see okoro’s address, not yours. Pictures and site icons load straight from their sites, which see your address but not the page you came from.
- Places. What you type to find a place in Where goes to Geoapify, with the town your connection appears to come from. Never your device’s own location, and never who asked.
- Errors. When something breaks, okoro tells Sentry what went wrong in its code, your browser and the room you were in. Never your address, your email or anything you wrote.
- Visits. Cloudflare Web Analytics counts visits to okoro and to this site without cookies and without telling one person from another.
With an account
An account lets your devices share the same days. To make one, okoro asks only for your email address. Then okoro keeps:
- your email address, and when you joined;
- everything you keep in okoro, as your devices send it: tasks, events, notes, pictures, files, highlights, the sites you follow and your settings;
- the devices you signed in on, each with a name such as “iPhone · Safari” and when it was last seen;
- for each sign-in, the IP address and browser it came from, kept by Supabase with that session and in its log of sign-ins;
- if you turn reminders on, each device’s address for notifications and the reminders of the next 30 days, with their titles (those of a calendar you subscribe to as well, if you turn its Reminders on).
Signing in uses a code okoro sends to your email, so there’s no password to keep or leak. If you choose Continue with Google, Google confirms who you are and shares your Google account’s email address, name and picture. okoro’s server keeps them with your account; okoro uses only the email address.
Who helps okoro run
Supabase, Cloudflare, Resend, Sentry and Geoapify process data for okoro under a data processing agreement, each only for the job named here. Google, GitHub and the services that deliver notifications handle what passes through them under their own terms.
| Who | What for | Where |
|---|---|---|
| Supabase | Accounts, the database, files, sync and reminders | EU (Frankfurt) |
| Cloudflare | Serving okoro and this site, okoro’s functions, the check that tells people from bots at sign-in (Turnstile), counting visits, the nightly backup copies | Worldwide network; backups in the EU |
| Resend | Sending the sign-in codes by email | United States |
| Sentry | Error reports, without anything you wrote | EU |
| Geoapify | Finding places in Where | EU (Germany) |
| Sign-in with Google: its button loads when you open Sign in, so Google sees your IP address then; your Google account is shared with okoro only if you choose Continue with Google | United States | |
| GitHub | Running okoro’s nightly jobs: the backup copy passes through its machines and isn’t kept there | United States |
| Apple, Google, Mozilla, Microsoft | Delivering reminders to your device, each sealed for that device so they can’t read it | Their own networks |
Where data leaves the EU, it does so under the safeguards the GDPR requires, such as the European Commission’s Standard Contractual Clauses or the EU-US Data Privacy Framework.
Calendars you subscribe to
A calendar you subscribe to by its secret address (Google’s “Secret address in iCal format”, Outlook’s published link) works like a key: whoever has the address can read that calendar. So, plainly:
- The address is part of your data. With an account it syncs to okoro’s server with the rest of your data, and only you can reach it.
- okoro’s functions ask for the calendar about every hour, and Cloudflare keeps a copy of it for up to a week, so okoro still works when the calendar’s service doesn’t. Once the address stops working, for instance when you reset it, the copy is let go the next time okoro asks for it, and within a week in any case.
- The events that come are kept on your device. If you turn Reminders on for that calendar, the titles and times of its reminders for the next 30 days are kept on okoro’s server, as your own are.
If you stop trusting an address, reset it in your calendar’s own settings: the old one stops working everywhere at once.
How long things are kept
- Your account and what you keep: as long as you have the account.
- What you delete: it waits 30 days in Recently deleted, so you can bring it back. Then only a marker without its content stays on the server for 180 days, so your other devices learn it was deleted. Pictures and files you remove stay in your account’s folder on the server until you delete the account.
- Your account, when you delete it: syncing stops at once. For 30 days you can still change your mind with Keep account; then everything on the server is deleted, files too. What’s on your devices stays there until you remove it.
- An address typed at Sign in and never confirmed: 7 days.
- Sign-ins: the IP address and browser of a session as long as it lasts, until you sign out; Supabase’s log of sign-ins, 90 days; its log of requests to the server, with IP addresses, a day.
- Reminders: the next 30 days; one that was sent is kept for two days.
- Backup copies of the server’s data: at most 30 days, after which a deleted account leaves the last one.
- Error reports: about 30 days at Sentry.
- What okoro fetches for you: a feed, an article or a calendar stays in Cloudflare’s cache for up to a week, and a place search for a day, shared by everyone who asks and without a word of who did.
Why okoro may use your data
- To give you the service you asked for (GDPR article 6.1.b): your account, sync, reminders, and fetching what you follow.
- To keep okoro secure and working (article 6.1.f, legitimate interests): error reports, limits against abuse, and counting visits without cookies.
- When the law requires it (article 6.1.c).
okoro doesn’t use your data for advertising, doesn’t profile you, and doesn’t sell or share it with anyone beyond the companies above.
Your rights
You can ask to see, correct, delete or take a copy of your data, to limit how it’s used, or object to its use. Most of it you can do yourself:
- A copy of everything: Settings › Account › Export everything, or Settings › Your data without an account.
- Deleting your account: Settings › Account › Delete account.
For anything else, write to hello@getokoro.com; you’ll have an answer within a month. You can also complain to a data protection authority: in Italy the Garante per la protezione dei dati personali (garanteprivacy.it), or the one where you live.
Security
Everything travels encrypted (HTTPS) and is encrypted where okoro’s server stores it; on your device, it’s as safe as your device is. On the server, each person can reach only their own rows, and the rules that ensure it are tested on every change. okoro runs its own code in your browser, plus Cloudflare’s count of visits and, at sign-in, Cloudflare’s and Google’s checks. No secret key of its services is ever in the page.
Your data isn’t end-to-end encrypted: reminders and calendars need the server to read what they carry. No one at okoro looks at what you keep, unless you ask for help and allow it.
Age
You must be at least 16 to create an account.
Cookies and storage
okoro and this site set no cookies. okoro keeps your data, and your sign-in when you have an account, in your browser’s own storage on your device. When you open Sign in, Google’s sign-in button and Cloudflare’s check load from their own sites, which see your IP address and may use their own cookies.
Changes
If this policy changes, the date at the top changes with it. If a change matters, okoro will tell you before it takes effect.