Back to foconotes
Updated 16 November 2026

Privacy

What the preview does with your data today, what the production service will collect, and the lines foconotes does not intend to cross.

This is a frontend preview. There is no account, backend, payment processor, or live Google connection in this build. The policy below describes both what the preview does today and what the production service is designed to do.

The short version

foconotes is built around a local-first workspace. The dashboard, timer, tasks, notes, and money view should work with the smallest amount of data that the job needs. Cloud services are optional, and the password vault is designed so the server cannot read it.

In this preview, there is no account, no backend, no analytics, and no advertising. Demo data stays in your browser.

What this preview stores

  • Tasks, calendar events, expenses, budgets, notes, focus sessions, and settings are stored in localStorage on this device so the demo survives a refresh.
  • Your theme, scene, accent, and quote-pack choice are also stored locally.
  • The password vault is kept in memory only. It resets when you refresh or close the tab.
  • No email address, name, or vault item is sent to a server in this build.

Clearing site data for foconotes removes the demo workspace. The Settings screen also has a reset control.

What the production service is designed to collect

  • Account identity: an email address or Google sign-in identifier, a display name, and session metadata needed to keep you signed in.
  • Calendar metadata: the Google calendars you choose to connect, event fields needed to display and sync them, and OAuth refresh tokens stored server-side.
  • Encrypted workspace data: tasks, events, focus history, expenses, notes, and vault ciphertext. The server should store bytes it cannot read where the feature allows it.
  • AI assistant requests: the message you send and the command result needed to answer it. The assistant should never read the vault, and should read notes only when a note command is explicitly chosen.
  • Billing metadata if a paid plan launches: plan status, renewal date, and a customer identifier. Card details would be handled by the payment provider, not foconotes.

Google Calendar

The calendar is designed to use Google Calendar as the event backend. Connecting would use Google OAuth with the calendar scope only. The refresh token would be kept in a server-side secret store and never in the browser or a mobile app bundle. You would be able to disconnect and revoke access from your Google account at any time.

This preview has no Google Cloud project, OAuth client, or live calendar connection. The status card in the calendar screen says so.

The AI assistant

The assistant is designed around a small decision model and a fixed set of commands. It reads one data category per conversation session, caches the result, and asks before writing calendar events. The production service would send only the selected command result and the written summary context to the language model.

The vault is excluded. Notes are not sent unless a note search command is chosen. No model provider should train on your content under the intended commercial terms; the provider configuration must be confirmed before launch.

Passwords and the vault

The preview vault is a design demonstration. Do not enter real passwords into it. The production architecture is planned around scrypt for key derivation, AES-256-GCM per item with a random nonce, and ciphertext-only storage. The PIN is never stored or transmitted. There is no recovery path for a forgotten PIN, and the setup screen must state that clearly.

Analytics, ads, and sharing

  • No advertising and no sale of personal data.
  • No third-party analytics scripts in this preview.
  • No training on your notes, vault, or calendar content.
  • If product analytics are added, they should be aggregate, minimal, and disclosed here before launch.

Retention and deletion

Preview data stays in your browser until you clear it. In the production service, account deletion should remove workspace data, encrypted backups, and calendar tokens within a disclosed window. Encrypted backup versions may persist for a short retention period before they age out. Billing records may be kept longer where tax law requires it.

Security

Encryption in transit, encryption at rest, row-level access controls, input validation, and least-privilege service keys are the baseline for the production build. No system is perfectly secure, and foconotes should not promise otherwise. Security issues can be reported to hello@foconotes.com.

Children

foconotes is intended for students and general productivity use. The production service should require users to be at least 13, or the higher minimum age required in their country, and should not knowingly collect data from younger children.

Media credits

The ambient café background in the workspace is an optimised, blurred crop of “Cafe in Paris - 001” by Nicolas Vigier, released under CC0 (public domain dedication) via Wikimedia Commons. It is used as a placeholder scene until the licensed video and photography library is connected through Cloudflare R2. The ambient sounds are generated in the browser with the Web Audio API.

Changes

This page will change before a production launch. Material changes will be shown in the app and, for account holders, sent by email. The effective date at the top of this page will move with them.

Questions: hello@foconotes.com

Open the workspace