Keepfor Cloud Third-Party Subprocessors
Last updated: October 11, 2026
1. Overview
Keepfor Cloud utilizes third-party subprocessors to provide infrastructure, payment processing, and transactional messaging capabilities. Each subprocessor is vetted for security, confidentiality, and data protection compliance.
2. List of Subprocessors
| Subprocessor | Entity & Location | Service Provided | Data Processed | Compliance / Security |
|---|---|---|---|---|
| Cloudflare, Inc. | 101 Townsend St, San Francisco, CA 94107, USA | Edge compute (Workers), Workers Logs (may include IP address and request URL, retained up to 7 days), relational database (D1), object storage (R2), vector index (Vectorize), AI inference (Workers AI), CDN, DDoS protection | Saved URLs, clean extracted HTML/text, vector embeddings, account IDs, session identifiers | SOC 2 Type II, ISO 27001, PCI-DSS Level 1, Standard Contractual Clauses (SCCs) |
| Stripe, Inc. | 354 Oyster Point Blvd, South San Francisco, CA 94080, USA | Payment processing, subscription lifecycle management, customer billing portal, invoicing | Customer email, billing address, payment instrument details, subscription status | PCI-DSS Level 1 Service Provider, SOC 1 & 2, SCCs |
| Resend, Inc. | 2261 Market St #5039, San Francisco, CA 94114, USA | Transactional email delivery (email verification, password reset tokens, weekly reading digests) | Recipient email address, email subject line, notification body (article titles, links) | SOC 2 Type II, GDPR compliant DPA, SCCs |
| PostHog, Inc. | United States (US region) | Product analytics (US region), server-side events only | Pseudonymous internal account ID, plan, and product event names. No email addresses, names, saved URLs, page content, search queries, prompts, or AI outputs. Client IP discarded; geolocation disabled | SOC 2 Type II, GDPR compliant DPA, SCCs |
3. Subprocessor Architecture and Data Scoping
- Cloudflare:
- All tenant databases (D1 shards) and object storage buckets (R2) are hosted within Cloudflare global network infrastructure.
- Vector embeddings are indexed in Cloudflare Vectorize with tenant namespace separation.
- Text summarization and tagging queries run ephemeral inference via Cloudflare Workers AI with no data retention for model training.
- Stripe:
- Payment credentials (credit card numbers, CVCs) are transmitted directly from the user's browser to Stripe Elements and never touch Keepfor Cloud servers.
- Keepfor Cloud retains only the opaque
stripe_customer_idandstripe_subscription_idreferences.
- Resend:
- Resend is invoked solely for programmatic email dispatch via HTTPS API calls.
- No email bodies sent to Resend contain full article texts or confidential document bodies.
- Emails contain verification links, password reset links, and article title digests.
- PostHog:
- Events are sent server-side only. There is no autocapture, no session recording, and no PostHog script in the browser.
- Events are keyed to a pseudonymous internal account ID. Deletion of the matching PostHog person is available on request to support@keepfor.me.
4. Updates and Notifications
Keepfor Cloud will maintain this list with current information. When new subprocessors are engaged or replaced, active customers will be provided with advance notification in accordance with the Data Processing Addendum.