Privacy policy

This draft explains how Pilo handles local workspaces, optional accounts and Sync, and embedded content. It needs owner review before public launch.

Draft for review · 17 November 2026

The short version

  • Local workspaces are saved in your browser. Pilo does not upload them automatically; you choose when to use a cloud workspace.
  • Email sign-in and optional Sync use Pilo’s account and cloud services. Stripe processes subscription payments.
  • Google Fonts and video/social providers receive requests when their fonts or embedded content load. Their own privacy policies apply.
  • X and Pinterest previews load automatically by default for new workspaces. You can turn automatic loading off in Settings.
  • This is a draft. Contact details, vendor locations, retention periods and account-deletion steps must be confirmed before launch.

01Who we are

Pilo is the website at pilonotes.com and the notes app at pilonotes.com/app. It is operated by OSIO Ltd, a company registered in England and Wales (company number 17463838).

OSIO Ltd is responsible for the personal information described in this draft (“we”, “us”, “our”). A Pilo privacy contact address must be supplied before launch.

This policy is written for the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations 2003 (PECR), as amended.

02Local workspaces and Sync

Pilo starts with a local workspace saved in your browser’s IndexedDB on the device you’re using. Signing in does not by itself upload that workspace. If you choose to create or open a cloud workspace, its synced content and arrangement data are sent to Pilo’s cloud service and associated with your signed-in account.

Local workspaces and cloud workspaces are separate. Copying local content to a cloud workspace is a deliberate action; review the destination before confirming it. Cloud data is not covered by the “local only” protections described for browser storage.

That means:

  • Local content stays on your device unless you choose a cloud-workspace action. Clearing site data or losing the device can remove the local copy; use Export backup in Settings to keep a separate copy.
  • Cloud workspaces are stored online. Workspace content and geometry are processed by the cloud service so Sync can keep that workspace available to your account.
  • Backups are files you create. Where you keep them (and who can see them) is up to you. Backup files are not encrypted by Pilo, so store them somewhere you trust.
  • Pasting or dragging content is handled in the browser. Loading an embedded provider preview or opening a link can make a separate request to that provider or website.
  • Several open tabs use browser-local messages to keep the same local workspace up to date.

You can export, edit or delete local data in the app or browser settings. Cloud-workspace retention and deletion periods, including account closure and backups, must be confirmed before this draft is approved.

03What we do receive

Technical information when you load the site

When your browser requests the website and app, the hosting service may receive standard technical details such as your IP address, request time and path, browser and operating-system information, and referring page. The hosting provider processes request information to deliver and secure the service. Its exact log-retention settings must be confirmed before this draft is approved.

The app can cache its own files for offline use. This reduces later requests but does not prevent hosting or provider services from receiving information when a new request is made.

When you contact us

If you email the support address, we receive your email address, your name if you include it, and what you choose to tell us. The address itself needs owner confirmation before launch.

Accounts, Sync and payments

If you sign in, Supabase Auth processes your email address and account/session information. If you choose a cloud workspace, workspace content and arrangement records are stored by the Supabase service for that account. Stripe processes subscription checkout and billing; Pilo receives subscription status and entitlement information to provide the selected service. Confirm the current vendor settings, retention periods and support process before publication.

Analytics and advertising

No analytics or advertising scripts were found in the current landing-page source. Hosting logs and requests to external fonts or content providers are separate from analytics and are described below.

04Embedded content from other services

Pilo can display content from YouTube, Vimeo, X and Pinterest. When a preview or player loads, your browser connects directly to that provider. The provider may receive your IP address, browser and device details, the provider URL or content identifier, and the page where the embed appears. It may store or read its own cookies or similar data and may associate activity with an account where you are signed in. Each provider’s own privacy policy applies to its handling of that request.

The relevant provider URL or content identifier is sent to render that card; other note text is not intentionally passed to the provider. Embeds run in provider frames and cannot read the app’s local workspace. Provider activity requires an internet connection.

YouTube (Google)

Thumbnails: when a YouTube card is on screen, the app shows the video’s thumbnail image, which your browser fetches from Google (img.youtube.com). This shares your IP address and browser details with Google, but does not load the player.

Player: the video player only loads when you press play. It uses YouTube’s privacy-enhanced mode (youtube-nocookie.com). Even in this mode, Google receives information about your device and connection when the player loads, the player can store data on your device, and cookies may be set once playback starts.

Google’s privacy policy: policies.google.com/privacy

Vimeo

The Vimeo player (player.vimeo.com) only loads when you press play. Once loaded, Vimeo receives information about your device and connection and may set cookies or use similar technologies.

Vimeo’s privacy policy: vimeo.com/privacy

X (formerly Twitter)

X posts are shown using X’s official embed (platform.twitter.com), which may load further content from other X domains (such as pbs.twimg.com and abs.twimg.com). The embed only loads when you press Load post on a card, or when you have turned on automatic previews. We request the embed with X’s “do not track” option, which asks X not to use it to personalise your experience — but we can’t control whether X honours it. X may still receive your IP address and device details, and may set cookies or use similar technologies.

X’s privacy policy: x.com/en/privacy

Pinterest

Pins are shown using Pinterest’s official embed (assets.pinterest.com), which may load images and scripts from other Pinterest domains (such as i.pinimg.com and s.pinimg.com) and send usage logs to Pinterest (log.pinterest.com). The embed only loads when you press Load Pin on a card, or when you have turned on automatic previews. Pinterest may set cookies or use similar technologies.

Pinterest’s privacy policy: policy.pinterest.com/en/privacy-policy

Automatic previews for X and Pinterest

Automatic previews are on by default for new workspaces. When enabled, X and Pinterest embeds load when their cards are visible. You can turn automatic loading off at any time in Settings → Advanced → Automatically load rich previews from external sites; you can still load an individual preview manually. This setting is saved with the workspace in this browser.

Website links

For ordinary website links, the app does not fetch the website just because you pasted its address. If you open a link, your browser visits that website and its own privacy policy applies.

Our role

Automatic X and Pinterest previews are enabled by default for new workspaces and can be turned off in Settings. The legal roles and appropriate lawful basis for these provider requests require owner and legal review before this draft is approved. We do not control what providers do with information they receive.

05Fonts

The website uses the Lexend typeface, loaded from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). When a website page loads, your browser requests the font files from Google, which means Google receives your IP address and browser details. Google processes this information under its own privacy policy: policies.google.com/privacy.

The app does not use Google Fonts. Its copy of Lexend is served from our own website along with the rest of the app, so opening the app makes no font requests to third parties.

06Cookies and device storage

The local workspace uses browser storage on your device. Supabase Auth also stores a sign-in session in browser storage. Third-party providers may set or read their own cookies or similar technologies when their content loads. The exact account-session and provider-storage details should be confirmed before this draft is approved:

WhatWhyHow long
IndexedDB (local workspace)Stores local notes, collections, layout, trash and settings on this device.Until you delete them or clear site data.
Browser workspace storage: preview settingStores whether automatic X and Pinterest previews are enabled.Until changed or the workspace data is cleared.
Browser storage: account sessionMaintains your signed-in Supabase Auth session.Until sign-out, expiry or browser data is cleared; exact provider behavior should be confirmed.
Local storage / browser messaging: tab syncTells other open Pilo tabs that a local workspace changed, so they can stay up to date.A few moments; contains a timestamp.
Service worker cacheKeeps a copy of Pilo app files for faster loading and offline access.Until replaced by an update or site data is cleared.

Local browser storage and cloud-workspace storage are different: cloud content is processed by Supabase for the account that owns that workspace. The third-party services in section 4 may use their own storage when their content loads.

07Our lawful bases

This section is a draft, not an approved legal decision. Owner/legal review is required to confirm the appropriate lawful basis for each activity and any consent requirements before publication.

ActivityLawful basis
Delivering and securing the website and app (server logs, hosting)Legitimate interests — running a working, secure website.
Loading fonts from Google FontsLegitimate interests — displaying the website consistently across devices.
YouTube thumbnailsLegitimate interests — showing which video a card refers to.
Loading a player or embed when you press play, Load post or Load PinLegitimate interests — providing content you have specifically asked to see. The provider’s storage at that point is part of delivering the content you requested.
Automatic X and Pinterest previewsOwner/legal review required: determine and document the appropriate lawful basis for default-enabled previews.
Account sign-in and Sync workspacesProviding the account and cloud service you choose; final lawful-basis wording needs review.
Subscription checkout and billingProcessing a requested subscription and related legal/accounting obligations; final wording needs review.
Replying to your emails and handling rights requestsLegitimate interests in responding to you; and legal obligation where you exercise your data protection rights.

Any legitimate-interests assessment and balancing test remain for owner/legal review; the entries above are not final.

08Who we share information with

We do not sell personal information or share it for advertising. The services involved in delivering Pilo include:

  • Supabase, for email authentication and cloud workspaces you choose to use.
  • Stripe, for subscription checkout and billing.
  • Our hosting provider, which processes technical request information to deliver and secure the site.
  • Our email provider, which stores emails you send to support.
  • The third-party services described in sections 4 and 5, which your browser connects to directly.
  • Authorities or advisers, if we are legally required to disclose information, or need to establish, exercise or defend legal claims.
  • A successor, if Pilo or OSIO Ltd is ever sold or restructured. The final policy must explain how any successor will handle personal information.

09International transfers

Some service providers may process information outside the UK. The locations used by Supabase, Stripe, hosting, email and embedded-content providers, and the applicable transfer safeguards, must be checked against the live service configuration and vendor terms before this policy is approved.

10How long we keep information

  • Local workspaces: kept in your browser until you delete them or clear site data.
  • Cloud workspaces and account records: retained by the relevant service while needed to provide the account and Sync. Exact deletion, backup and account-closure periods must be confirmed before publication.
  • Subscription records: Stripe and Pilo may retain records for billing, reconciliation and legal obligations; exact periods must be confirmed.
  • Server request logs and support emails: handled according to the hosting and email providers’ retention settings, which need confirmation for this release.

11Security

Local workspaces are stored in your browser; cloud workspaces are stored by Supabase and restricted to the account that owns them by server-side authorization. Provider content is loaded in provider frames. No system is risk-free, so protect your account and device, and keep backup files somewhere you trust. The final security and incident-response details require owner review.

12Your rights

Under UK data protection law you have the right to:

  • access the personal information we hold about you;
  • have inaccurate information corrected;
  • have information deleted;
  • restrict how we use it;
  • object to our use of it where we rely on legitimate interests;
  • receive it in a portable format, in some circumstances; and
  • withdraw consent at any time, where we rely on consent. This doesn’t affect anything that happened before you withdrew it. Whether consent is the appropriate basis for default-enabled previews requires owner/legal review.

We don’t make any decisions about you based solely on automated processing.

For local workspace data, use the app’s export, edit and delete controls or your browser settings. For account and cloud-workspace requests, contact the support address below; the account-deletion and support process must be confirmed before launch. We may ask for information to confirm your identity. For information held by YouTube, Vimeo, X, Pinterest, Google or Stripe, use the provider’s own privacy channels.

13Complaints

If you’re unhappy with how we’ve handled your information, contact the Pilo privacy address once it is confirmed. The complaint-handling process must also be approved before launch.

You also have the right to complain to the UK’s data protection regulator, the Information Commissioner’s Office (ICO):

Information Commissioner’s Office
Wycliffe House, Water Lane
Wilmslow, Cheshire
SK9 5AF

Helpline: 0303 123 1113 · Website: ico.org.uk/make-a-complaint

14Children

Pilo’s intended age range and approach to children’s accounts have not yet been confirmed for this draft. Settle and publish the age policy before launch.

15Changes to this policy

We’ll update this policy if Pilo or the law changes. The date at the top shows when it was last reviewed. If a change significantly affects how information is used, we’ll explain it on the website or in the app.

16Contact us

Questions, requests or complaints about privacy: Pilo’s privacy contact address is to be confirmed before launch.