Skip to content

Keepfor Cloud Privacy Policy

Last updated: October 11, 2026

1. Overview

This Privacy Policy explains how Keepfor ("Keepfor Cloud", "we", "us", or "our") collects, uses, stores, and protects personal data when you use the Keepfor Cloud hosted service ("Service") available at https://app.keepfor.me.

2. Information We Collect

A. Account and Authentication Data

  • Email address (used as unique login credential and for service notifications).
  • Password hash (cryptographically hashed using argon2 or pbkdf2-sha256; plain-text passwords are never stored).
  • Session tokens and personal access token hashes.
  • Account creation timestamp and last login timestamp.

B. User Content and Library Data

  • URLs submitted for reading and extraction.
  • Clean extracted HTML and text content extracted from saved articles.
  • User-created notes, tags, and reading progress metadata.
  • Vector embeddings derived from article text chunks for semantic search and question answering.

C. Billing and Subscription Data

  • Stripe customer identifier and subscription identifier.
  • Subscription plan type, billing period dates, and status.
  • Payment card data is processed directly by Stripe, Inc. and is never received, handled, or stored by Keepfor Cloud servers.

D. System Telemetry and Audit Logs

  • HTTP request logs capturing request ID, tenant ID, route path, status code, and latency.
  • Operator audit logs recording administrative actions (such as account suspensions or trial extensions).
  • Cloudflare Workers Logs, which may include the visitor IP address and request URL, retained for up to 7 days.
  • Log Hygiene Guarantee: Request logs and operator logs never contain saved article content, extracted clean text, or user email addresses.

E. Product Analytics and Marketing Attribution Data

  • Product usage events sent to PostHog, tagged with an internal account identifier and plan. See Section 6 for the full list and what is never sent.
  • Marketing attribution values (UTM source, medium and campaign, and the referring site hostname) captured from your first landing-page visit and stored on your account at sign-up. See Section 7.

3. Purposes of Data Processing

We process your data exclusively to provide and maintain the Service:

  1. Content Ingestion and Reader View: Fetching web pages you submit, parsing clean text, and rendering the distraction-free reader interface.
  2. Search and Organization: Indexing text for full-text search (SQLite FTS5) and semantic vector search (Cloudflare Vectorize).
  3. AI Features: Generating concise article summaries, suggesting tags, and answering questions about your saved library using Cloudflare Workers AI.
  4. Digest Emails: Delivering scheduled weekly reading digests if enabled in your settings.
  5. Billing Administration: Managing subscription status, upgrades, and renewals via Stripe webhooks.
  6. Product Analytics and Attribution: Understanding which features are used, which plan limits are reached, and which marketing channels lead to sign-ups, so we can improve and operate the Service.
  7. No AI Model Training: We do not sell your personal data or saved library content, nor do we use your private articles, notes, or embeddings to train artificial intelligence models.

4. Data Retention and Deletion

  1. Active Retention: Data is retained for as long as your account remains active.
  2. Data Export: You can export your full library, metadata, tags, and notes at any time via the export interface.
  3. Account Deletion: Upon initiating account deletion (or tenant termination):
  • All relational database rows (items, tags, chunks, credentials) are deleted from the data shard.
  • All cached HTML blobs and export archives are deleted from Cloudflare R2 object storage.
  • All vector embeddings are deleted from Cloudflare Vectorize.
  • All control-plane records and active sessions are permanently deleted.
  • Associated Stripe recurring subscriptions are immediately cancelled.
  1. Analytics Data and Deletion: Analytics events are keyed to a pseudonymous internal account identifier, not to your email address. On request to support@keepfor.me, we will also delete the matching PostHog person and its events.

5. Third-Party Subprocessors

To operate the hosted infrastructure, Keepfor Cloud engages third-party subprocessors under strict data protection agreements:

  • Cloudflare, Inc.: Compute (Workers), relational databases (D1), object storage (R2), vector index (Vectorize), AI inference (Workers AI).
  • Stripe, Inc.: Payment processing and customer billing portal.
  • Resend, Inc.: Transactional email delivery for verification, password resets, and weekly digests.
  • PostHog, Inc.: Product analytics (US region). Server-side events only: no autocapture, no session recording, and no scripts loaded in your browser. See Section 6.

Cloudflare also provides Workers Logs for operational debugging. These logs may include the visitor IP address and request URL and are retained for up to 7 days.

See Third-Party Subprocessors for full subprocessor disclosures.

6. Product Analytics

We use PostHog, hosted in the United States region, to understand how the Service is used. Events are sent from our servers only. We do not use autocapture or session recording, and we load no PostHog scripts in your browser.

Events collected. Each event is tagged with an internal account identifier and your plan:

  • Sign-up and login
  • Trial and subscription events
  • Item saved
  • Summary generated
  • Ask query
  • Search performed
  • Plan limit reached
  • Export requested
  • MCP token created

Never sent to PostHog. Email addresses, names, saved URLs, saved page content, search queries, prompts, and AI outputs.

IP address. The client IP address is discarded and not stored by PostHog, and geolocation is disabled.

Retention. Analytics events are retained according to PostHog's default retention settings.

Legal basis. Where the GDPR applies, we process this data under our legitimate interests in operating, securing, and improving the Service.

Deletion. To have your analytics data deleted, email support@keepfor.me. Events are keyed to a pseudonymous account identifier, and we will remove the matching PostHog person on request.

7. Cookies

Keepfor Cloud sets only first-party cookies:

  • kfc_session (session cookie): keeps you logged in. It is HttpOnly, Secure, and SameSite=Lax. Session cookies are strictly necessary to provide the Service.
  • kfc_attr (attribution cookie): set on your first landing-page visit when you are not logged in. It lasts 30 days and is HttpOnly, Secure, and SameSite=Lax. It holds a random anonymous identifier, any UTM campaign values from the link you followed, and the hostname of the referring site. We use it to attribute sign-ups to marketing channels. If you sign up, these values are stored on your account (as utm_source, utm_medium, utm_campaign, and referrer).

You can refuse kfc_attr by blocking cookies in your browser without affecting the Service. Blocking session cookies will prevent you from logging in.

8. Your Rights (GDPR, CCPA, and Global Privacy)

Depending on your location, you have the right to:

  • Access: Request confirmation and details of personal data held about you.
  • Portability: Download an export of your content in machine-readable JSON format.
  • Correction: Update inaccurate or outdated profile information.
  • Erasure: Permanently delete your account and all associated library content.
  • Withdraw Consent: Unsubscribe from digest emails or promotional communications at any time.

9. Contact Information

For privacy questions, data protection requests, or GDPR inquiries:

  • Email: privacy@keepfor.me
  • Data Controller: Keepfor
Return to Keepfor Cloud