# Rhypple Privacy Policy

Privacy

Privacy

The basic things to know about storage, sync, Rhypple Cloud, billing, and beta analytics.

Last updated: June 20, 2026 Core policy and cloud notes

Google user data

How Rhypple uses Google Drive data

Rhypple uses Google Drive as a sync layer for user-controlled workspaces. For Drive-synced workspaces, sync happens between your device and Google Drive for core notes, attachments, team shared folders, channels, and messages. Rhypple does not receive, host, or keep a copy of your Rhypple database or Google Drive files.

Local database

Only on your device

Workspace content is stored in local browser or app storage. Google Drive is not used unless you choose a Drive sync mode.

Personal Drive database

Private sync in your Drive

Rhypple stores sync files in the hidden Google Drive app data area so the same workspace can move between your own devices.

Team workspace database

Shared Drive folders

Rhypple stores shared workspace data in a visible Google Drive folder, including team channels, messages, manifests, point batches, snapshots, and attachments.

Rhypple Cloud Team Workspace

Firebase-backed paid workspace

Rhypple Plus workspaces use Firebase Auth, Firestore, Firebase Storage, and billing state so teams can sign in, sync, use channels, invite members, and manage Plus access.

Data accessed

  • Your Google Account email, display name, and profile image, when available, to show the signed-in account and identify team members.
  • Drive access needed to find Rhypple folders that you own, choose, or join, including folders shared by another Google account.
  • Google Drive file and folder metadata needed to find, create, open, update, and delete Rhypple workspace files and folders.
  • Rhypple workspace file contents stored in Drive, including sync files, manifests, note attachments, channel messages, and message attachments.
  • Drive permissions for team workspaces, so owners can invite members and Rhypple can respect folder access.

Data usage

  • Sync your Rhypple database across your devices or a team workspace.
  • Create, read, update, and delete Rhypple folders and files in Google Drive.
  • Download updates, upload local edits, resolve sync state, and recover workspace state after reopening the app.
  • Show account, workspace, channel, attachment, and sharing status inside Rhypple.

Data sharing

  • We do not sell Google user data, use it for advertising, or transfer it to data brokers.
  • Workspace content is written to Google Drive from your device only so Google Drive can store and sync the files you chose to sync.
  • In team workspaces, content in shared folders is available to the Google accounts that have Drive permission for those folders.
  • Rhypple does not share Google Drive file contents with PostHog or other analytics services.

Storage and protection

  • Local databases stay in browser or app storage on your device.
  • Personal Drive databases stay in your Google Drive app data storage.
  • Team workspace databases stay in the Google Drive folders controlled by the workspace owner and Drive permissions.
  • Drive communication uses Google's OAuth flow and HTTPS. OAuth tokens are stored on your device for sign-in and sync; desktop builds use OS-provided encryption where available.
  • Rhypple does not keep OAuth tokens outside your device.

Retention and deletion

  • Rhypple keeps Google Drive data only in your device storage or in your Google Drive, depending on the database mode you choose.
  • You can delete local data from the app or your browser storage, and you can delete Drive-synced workspace files from Google Drive.
  • You can revoke Rhypple's Google access from your Google Account permissions at any time.
  • For deletion help, email rhypple.app@gmail.com. Because we do not keep a server copy, deletion usually means removing the local or Drive files you control.

Limited use statement

Rhypple's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Apps on one database

How Rhypple apps use Google Drive

Rhypple is a shared database layer with multiple apps on top. The app you open changes the interface and the kind of records you create, but Drive sync applies to the active Rhypple database unless a feature says it stays local.

Atlas

Research and renderer files

Atlas uses the Rhypple database for project notes, citations, trails, and the project graph. When Drive sync is enabled, that database syncs through Drive. Atlas may also use Drive for renderer target files such as LaTeX, HTML, Markdown, slide files, template assets, overlays, anchors, and target sync metadata. Private editing session state stays on your device.

Workspace

Team folders and channels

Workspace uses a visible shared Google Drive folder for team workspaces. That folder can contain the shared core database, workspace manifests, channel folders, message files, message indexes, and attachments. Google Drive permissions decide which Google accounts can access the shared workspace and its channels.

Other apps

Records in the shared database

Apps such as Action Space, Research Notes, Simple Notes, Time Trackers, Desk, Classroom, and Observatory use the shared Rhypple database for the records they create, such as notes, tags, tasks, timers, saved research entries, observations, and attachments. In Drive sync mode, those records sync as Rhypple database data. In local mode, they stay on your device.

Rhypple Cloud

How Rhypple Plus uses Firebase and Stripe

Rhypple Cloud Team Workspace is the paid team database option. It is separate from local databases and from Google Drive databases.

Firebase Auth

Sign-in identity

Cloud workspaces use Firebase Auth, currently Google sign-in, to identify the signed-in user, workspace owner, and team members. Rhypple may use your account email, display name, profile image, Firebase user id, and subscription claim to show account and access status.

Firestore and Storage

Team workspace content

Cloud workspace data can include workspace metadata, point revisions, sync batches, snapshots, channels, messages, invites, roles, audit records, and attachments. Access is controlled by Firebase security rules and privileged Firebase Functions for actions such as invites, role changes, billing state, and protected workspace operations.

Stripe

Rhypple Plus billing

Rhypple uses Stripe to create checkout sessions, manage subscriptions, and receive subscription status updates. Internal codes can also grant zero-cost Plus access. Payment details are handled by Stripe, not stored in the Rhypple database. Rhypple stores only the billing identifiers and subscription state needed to unlock or revoke Rhypple Plus access.