Privacy Policy

1. Local-First Storage

Scraps Cache is built from the ground up as an offline-first application. Your notes, checklists, canvas drawings, labels, and uploaded attachments are saved directly on your device using your browser's IndexedDB storage.

You can use Scraps Cache completely offline without creating an account, without connecting to any server, and without sending a single byte of note data over the internet.

2. End-to-End Encrypted Cloud Sync

Multi-device sync is completely optional. When you choose to sync across devices, all note titles, bodies, checklists, attachments, and canvases are encrypted on your device using XChaCha20-Poly1305 before transmission.

The sync keys are generated on your hardware and never sent to any server in plaintext. The sync relay stores your content only as opaque encrypted ciphertext, next to blinded hashes and the few records listed in section 4 that it needs to run sync. We cannot read, scan, index, monetize, or decrypt your content.

3. Zero Tracking & No Analytics

We do not track you. Scraps Cache contains:

• No third-party advertising scripts or tracking pixels
• No behavioral tracking or analytics frameworks
• No personal profiling or data brokers
• No third-party tracking cookies

4. Relay Server Logs & Verification

When interacting with the optional cloud sync relay or push wake service:

• Transient Network Logs: Standard network logs (such as IP addresses and request timestamps) may be processed temporarily by infrastructure providers (e.g., Cloudflare) strictly for DDoS mitigation and operational stability.
• Bot Verification: When creating a sync workspace on public relays, Cloudflare Turnstile may be used to verify human visitors without setting tracking cookies.
• Push Notifications: Web Push notification endpoints and encrypted wake payloads are stored only to deliver background sync wake signals to your devices.
• iPhone App Push: With notifications allowed, the iPhone app registers the push token iOS gives it with the relay, under each workspace it syncs. iOS issues one token per app, so the relay can tell that those workspaces are on the same phone. A reminder push travels through Apple's push service and says only that a reminder is due; it never carries a note or its title.
• Workspace Records: For each synced workspace the relay keeps a random workspace ID, its public signing key, how many encrypted records and bytes it holds, and when it was last used. It uses them to run sync, enforce storage limits and remove unused workspaces. None of them is your name, email or phone number.
• Reminder Times: For the reminders in a synced workspace, the relay stores the time each upcoming one is due, without its note or title, so that it can wake your devices. Each time is deleted a day after it has passed.
• Abuse Limits: To slow down abuse, the relay counts requests per IP address (per /64 network for IPv6) and per workspace. A counter is deleted within about an hour once it has been idle for 10 minutes, except a workspace's count of sync writes (uploads and deletions), which is kept for 5 days after its last use.

5. Data Ownership & Right to Deletion

You own all of your data. You can export a full password-encrypted backup at any time from the Settings menu. If you use cloud sync, you can unlink your workspace or execute a permanent deletion, immediately wiping the cloud ciphertext record.

A synced workspace that has not been used for 365 days is deleted from the hosted relay. When you remove a workspace from the cloud, the relay deletes its data at once and keeps its random ID and the date, so that a lost device that still holds the workspace's key cannot create it again. Its count of sync writes goes after 5 days, as above.

6. Self-Hosting & Source Code

Scraps Cache is open source. You are welcome to inspect the cryptographic implementations, audit our code, or host your own sync relay and web server so that you have 100% control over your infrastructure.

7. AI Assistants (Optional)

Scraps Cache has no AI features and runs no AI service. You can choose to connect an AI assistant by deploying your own MCP server and approving it on a consent screen that names its address. Approving gives that server the key to one synced workspace: whoever runs it, and any AI assistant you connect to it, can read and change the notes in that workspace. Nothing is shared unless you approve it. To end its access, remove the workspace from the cloud.

8. Contact

Questions about privacy or your data: write to support@scrapscache.com. More help is on the Support page.