Privacy Policy

3.1 Account

• Email and password sign-in: your email address and password. The password is stored encrypted by our sign-in provider (Supabase); we cannot see it.
• Google sign-in: Google shares your name, email address and a link to your profile picture. We use your name and email.
• Why: to identify you, protect your account, sync between devices and send messages you asked for. We send one welcome email after sign-up.
• Several accounts on one device: if you add several accounts, their sign-in sessions (not passwords) are kept on that device. An account not opened for 30 days is signed out.

3.2 Profile and settings

• The name you chose, a character or emoji, and, if you upload one, a profile photo, stored as a small copy.
• Language, theme and other app settings.
• When you are signed in, some settings are saved in your cloud profile so another device can continue where you left off, for example calendar settings, parts of the day and the task running now.

3.3 Tasks and routines

• What: tasks, times, durations, icons, routines, templates, parts of the day, folders, subtasks, repeats and reminders. A routine can also hold a place, a description, a color and links to Google Drive files. Also your progress in the rewards game.
• Where: on your device. If cloud sync is on (part of Focora Pro; you can turn it off in Settings), it is also stored in our database so it appears on all your devices. Without sync, tasks stay on your device, except as described in the sections on Luna, reminders and sharing.
• A task you delete stays in the cloud marked "deleted" so your other devices know and it can be restored. These marks are erased when you delete your account.
• Tip: task titles may reach Luna, reminders and emails. Better not to put sensitive details, such as medical ones, in them.

3.4 Luna, the voice assistant

• Luna is an AI assistant, and her voice is computer-generated. She can make mistakes.
• Sent to Anthropic (Claude model) with each request to Luna: what you said or typed to her (after speech became text), the current conversation, your profile name, today's tasks from now on (up to 16, with times and routine names), the names of up to 12 templates, the language and the open screen. Requests pass through our server, which does not store the conversation content.
• When you ask Luna to find, move or change a task: the tasks found for that request (title, date and time, up to 30), including tasks on other days, and the names of matching routines are also sent.
• Calendar meetings: a meeting you pinned as a task is a task like any other, and it is sent to Luna together with the rest of the day's tasks. Other calendar events are not sent to Luna (section 3.7).
• Luna's voice (premium voice): the text Luna speaks is sent to OpenAI to generate audio. The audio is cached on your device so it is not generated again. Some fixed phrases are pre-recorded. With the standard voice, your device reads the text itself and nothing is sent.
• Building a routine from a description: when you describe a routine in words or by voice, the text is sent to OpenAI to split it into steps, durations and icons.
• At the providers: under their terms, Anthropic and OpenAI do not train models on this data. They usually delete it within 30 days. Anthropic may keep content flagged by its safety systems for up to two years, and OpenAI may keep data longer if the law requires.
• Conversation history (the last 60 messages) is stored only on your device. The "Clear" button in the chat deletes it.
• Your own key: if you enter your own Anthropic API key, requests go directly from your device to Anthropic under your agreement with Anthropic. The key is stored only on your device.
• Reporting a reply: you can report a Luna reply by email to hello@focora.io.

3.5 Microphone and voice

• The microphone is on only when you tap it or talk to Luna. We do not record or store audio.
• Speech is turned into text by the system's recognition service: on iPhone, Apple speech recognition; in a browser, the browser's service (for example Google in Chrome, Apple in Safari); on Android, the system service. These services may process audio on their servers under their own terms. We receive only the text.
• While listening, the app measures loudness on the device to show an indicator. This is not stored.

3.6 Reminders and notifications

• Browser notifications: your device's notification address, reminder times and their text (usually the task title) are stored on our server (Upstash) until sent, then deleted. Your browser's push service (Apple, Google or Mozilla) delivers the notification. Turning notifications off deletes the address from the server.
• In the iPhone app reminders are scheduled on the device itself.
• Lock-screen timer (Live Activity): during Focus, our server receives the titles, icons and durations of the current and next tasks and your device's notification token. This is kept for up to 24 hours and delivered through Apple's push service.
• Email reminders (off until you turn them on): your email, task titles and times are queued (Upstash) until sent. Emails are sent through Resend.

3.7 Calendars

Google Calendar

• Why: to show your events on your Focora schedule.
• Read-only. We never write to or change your calendars.
• What we keep: your calendar list (name, color, ID; your primary calendar's ID is your email address) and events: title, start and end, all-day, busy or free, color, and whether it was cancelled. We read one month back to one year ahead. Events are stored in our database, and each user can access only their own.
• What we don't keep: descriptions, locations and attendees. Google sends them to our server with the event, and we discard them immediately without saving.
• Your access token is stored encrypted, and the encryption key is not in the database.
• What we don't do: we don't sell it, use it for ads, pass it to others or use it to train models. Events that are only displayed are not sent to Luna or to any other AI. No one on our team reads them unless you ask (for example, to fix a problem), for security, or when the law requires.
• An event you turn into a task: if you pin a meeting as a Focora task, yourself or with the "pin automatically" setting, its title and time become your task. From then on it is handled like any task: sync, reminders, and when you talk to Luna it is sent to her together with the rest of the day's tasks (section 3.4).
• How long: cancelled events are deleted after 30 days; past events 90 days after they end. Disconnecting a calendar or deleting your account deletes everything at once.
• How to disconnect: Settings, "Connect calendars", choose the source, "Disconnect". For Google we also revoke access at Google. You can also revoke Google access at myaccount.google.com/permissions.
• Google: Focora's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Section 12 gives the full details.

3.8 Google Drive files

• You pick files in Google's window. Access covers only the files you pick.
• The access token is kept only in browser memory, for about an hour, not by us.
• We store the link, file ID, name and type as part of the routine. We do not copy the file's content.
• You can revoke access at myaccount.google.com/permissions. Section 12 gives the full details.

3.9 Sharing a routine by link

• When you share a routine, our server stores the routine (step names, durations, icons and repeats) and your name. If you haven't set a name, the part of your email before the @ is shown.
• Anyone with the link can see the routine and the name. When someone accepts it, their email may be stored with the share.
• You can delete the link.

3.10 Age

• If you were asked for your year of birth, it is stored only on your device. Only your age group (under 13, 13 to 15, 16 and over) is sent to our server, and only when needed to open or close age-limited parts.

3.11 Technical data

• Our hosting provider (Vercel) logs server requests, including IP address, browser type and time, for security and operations, briefly and under its own rules.
• To prevent abuse, we count requests per IP address for about an hour. A sign-in check result is kept for up to 5 minutes.
• Fonts load from Google Fonts and the sign-in library from jsDelivr; their servers see your IP address when these load. Music plays from our own storage.
• The app has no analytics, ad networks or tracking across other sites and apps. We do not sell data.

3.12 Stored only on your device

Tasks and settings (without sync), your Luna conversation history, the voice cache, an audio file you chose for music, your year of birth, and sign-in sessions of other accounts on the device. "Delete everything from this phone" in the "Danger zone" in Settings removes them from the device.

What we access and why

Google Calendar (read-only)

• Your calendar list (scope calendar.calendarlist.readonly): the name, color, time zone and your access level of each calendar in your Google account, and its ID. The ID of your primary calendar is your email address, and we use it to label the connection. We use the list so you can choose which calendars appear in Focora.
• Your events (scope calendar.events.readonly): events in the calendars you choose to show, from 30 days in the past to 365 days ahead. From each event we keep only its title, start and end (or dates for all-day events), whether it shows you as busy or free, its color and time zone, whether it was cancelled, and the technical identifiers needed to keep the copy up to date (event ID, iCalendar UID, recurring event ID, version tag and last update time).
• Why: to show your events on your Focora calendar next to your tasks, so that your tasks and routines are not planned on top of your meetings.
• What we do not keep: event descriptions, locations, attendees, attachments and conference links. Google includes some of these when it sends an event to our server; we discard them in memory and never save them.
• We never write to your calendar. Focora does not create, change or delete anything in Google Calendar.

Turning an event into a task (your choice)

If you tap an event and choose "Make it fixed", or turn on "Fixed automatically" for a calendar (this pins timed, busy events of that calendar in the next 30 days), Focora creates a Focora task with the event's title and time and keeps a link to the event (calendar ID, event ID and iCalendar UID), so the task follows the meeting if it is moved or cancelled in Google Calendar. From then on it is one of your tasks and is handled like any task you create yourself: see "Who receives it" below.

Google Drive (scope drive.file)

• Used only when you tap "Add Google Drive attachment" in a routine. Google's file picker opens, and Focora gets access only to the files you pick there, never to the rest of your Drive.
• We store the file's ID, name, link and a file-type icon as part of the routine. We never read, download, copy, change or delete the file's content. Opening the attachment opens the file in Google Drive under your own Google account.
• The Drive access token stays in your browser's memory for about one hour. It is never sent to or stored on our servers.

Sign in with Google (if you use it)

Google shares your name, email address and profile picture link. We use your name and email address to create and identify your Focora account.

How we store and protect it

• Calendar lists and event copies are stored in our database (Supabase). Access rules in the database let each account read only its own rows.
• To keep your calendar up to date without asking you to sign in again, Google gives us a refresh token. We encrypt it with AES-256-GCM before saving it. The encryption key is kept in our server environment, not in the database, and each encrypted token is bound to your account. The token is decrypted only on our server, only to fetch updates from Google, and never leaves our server in readable form.
• While you connect, a one-time ticket with the encrypted token and your calendar list is held in our server cache (Upstash) for at most 10 minutes, and is deleted as soon as the connection completes.
• The connection is protected with a signed one-time state value and PKCE. All traffic uses HTTPS.

How long we keep it

• Event copies: cancelled events are removed 30 days after cancellation, and past events 90 days after they end. This clean-up runs when your calendar syncs with Google.
• If you disconnect Google Calendar in Focora or delete your account, we delete the connection, the encrypted token, your calendar list and all event copies immediately.
• If you remove Focora's access on Google's side instead, we can no longer read your calendar and Focora shows "Reconnect needed". Copies already stored stay until you tap "Disconnect" in Focora or delete your account.
• Drive attachment details stay with the routine until you remove the file from the routine, delete the routine or delete your account.
• Tasks you created from events stay until you delete them, like any other task. Disconnecting a calendar does not delete them.

How to revoke access and delete your data

• In Focora: Settings, "Connect calendars", Google, "Disconnect" (tap twice to confirm). We revoke Focora's access at Google and delete the data listed above.
• At Google: open https://myaccount.google.com/permissions, choose Focora and remove access. This works for Calendar and Drive.
• Drive attachments: "Remove file" next to the attachment in the routine deletes the stored link and name.
• Delete your account: Settings, "Danger zone", "Delete account". Everything is deleted and Google Calendar access is revoked at Google.
• Or email hello@focora.io and we will do it for you.

Who receives it

• We never sell Google user data, never use it for advertising (including retargeting, personalized or interest-based ads), never transfer it to advertising platforms, data brokers or information resellers, and never use it to determine credit-worthiness or for lending.
• We never use Google user data to create, train or improve any artificial intelligence or machine learning model.
• Service providers that store or process it only to run Focora for you: Supabase (database), Vercel (our servers) and Upstash (the 10-minute connection ticket).
• Events you have only displayed are not sent to Luna or any other AI service, and are not included in emails or notifications.
• Tasks you created from events are handled like your other tasks. Their title and time may be sent: to Anthropic when you talk to Luna, and to OpenAI to voice Luna's premium speech, only if you agreed to Luna's data use (these providers process API data under terms that do not allow training their models on it); to Resend, and to the push services of Apple, Google or Mozilla, when you turn on reminders, notifications or the lock-screen timer; and to other people only if you include those tasks in a week or routine that you choose to share or publish.
• People: no one at Focora reads your Google user data unless you ask us to (for example, to fix a problem with your calendar), it is needed for security (such as investigating abuse or a bug), or the law requires it. Content you choose to publish to the community is reviewed by our moderators before it appears.
• We transfer Google user data only as needed to provide these features, for security, to comply with the law, or, with your explicit prior consent, as part of a merger, acquisition or sale of assets.

Limited Use

Focora's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace APIs (Google Calendar and Google Drive) will also adhere to the Google Workspace API User Data and Developer Policy.

What we collect

Through the website we actively collect only your email address, which you submit through the waitlist form.

We also receive limited technical data automatically, through the visit statistics described under "Cookies" below: approximate country, browser and its language, device type, referrer and the pages you open. We look at it as totals to understand how the site is used, not to find out who you are.

Why we collect it, and our legal basis

We process your email based on your explicit consent (Section 11 of Israel's Protection of Privacy Law, 5741-1981, as amended by Amendment 13; and Art. 6(1)(a) GDPR where applicable). We use it to:

• send you updates about the Focora launch and early-access invitations;
• send transactional messages (confirmation of signup, account notifications).

Service providers for the website

To run this site and the waitlist we rely on:

• Lovable (lovable.dev): website hosting, builder, and visit statistics (run on Tinybird; see "Cookies" below);
• Supabase: the database where your email is stored;
• Resend (resend.com): sending you emails;
• Cloudflare: content delivery and security for the site;
• Google Fonts: serves the site's typefaces; Google sets no cookies for this, but its servers receive your IP address when the fonts load;
• Namecheap: domain registration and DNS.

Some of these providers store or process data outside Israel, primarily in the EU and the US. Where data leaves Israel, we rely on adequacy decisions, the EU Standard Contractual Clauses (SCCs), or equivalent safeguards required by Amendment 13.

How long we keep your waitlist email

We keep your email until the earlier of:

• you ask us to delete it or unsubscribe; or
• 24 months pass with no interaction from you, after which we delete it automatically.

Security of the website

Your data is transmitted over HTTPS/TLS and stored encrypted at rest in our providers' systems. Our database tier is operated in line with Israel's Privacy Protection (Data Security) Regulations, 5777-2017, to the extent applicable. If a personal-data breach occurs that is likely to affect you, we will notify you and the Israeli Privacy Protection Authority without undue delay.

Marketing emails and unsubscribe

Every marketing email we send includes a clear sender identification and a one-click unsubscribe link. Where Israel's “Spam Law” (Amendment 40 to the Communications Law, 5742-1982) applies, we mark promotional subjects accordingly and provide a Hebrew unsubscribe option.

Site content loads from Supabase, which sets its own __cf_bm security cookie.

Fonts load from Google Fonts. Google sets no cookies for this, but its servers receive your IP address when the fonts load.

We do not use the statistics to find out who you are, and we do not use cookies for advertising or for tracking you on other sites. You can block or delete cookies in your browser settings; the site works without the statistics cookie.