Rewind Reels Docscontact@purposeforce.org

Data & Retention Policy

Last updated March 2026

On this page

  1. Overview
  2. Salesforce CRM Data
  3. Generated Videos
  4. Narration Scripts
  5. Billing Data
  6. Logs
  7. API Keys
  8. Summary Table

Overview

Rewind Reels for Salesforce is designed with a data-minimization philosophy. Your Salesforce CRM data is never stored on Rewind servers. Data flows through memory during video generation and is discarded immediately after processing. This page details exactly what data is stored, where, and for how long.

Note: PurposeForce acts as a data processor, not a data controller. Your Salesforce org remains the system of record for all CRM data and video metadata.

Salesforce CRM Data

Salesforce CRM data (Opportunities, Accounts, Cases, Contacts, etc.) is queried at render time via the Salesforce REST API. This data is not stored on Rewind servers.

  • Query: Data is fetched live from the customer's Salesforce org when a video render is initiated
  • Processing: The queried data passes through server memory only during narration generation (Claude API call) and video composition
  • Disposal: All CRM data is discarded from memory after the API response is returned. No database writes, no file system writes, no caching
  • Scope: Only the fields defined in the selected preset configuration are queried. Rewind Reels never performs broad or exploratory queries
Tip: Because data is queried live, each video reflects the exact state of your Salesforce org at the moment of generation. There is no stale data or sync lag.

Generated Videos

Videos are rendered as animated HTML presentations in the viewer's browser. No video files are generated or stored on external servers.

  • Storage location: Narration JSON and theme data are stored on the Rewind_Video__c record in the customer's Salesforce org (fields: Scene_Schema__c, Theme_JSON__c)
  • Access method: The public player fetches narration JSON via the player API and renders scenes client-side with animations and music
  • Retention: Video data persists as long as the Rewind_Video__c record exists in Salesforce. Deleting the record removes all associated data.
  • No external file storage: Unlike traditional video platforms, Rewind Reels does not store MP4 files on S3 or any cloud storage. All rendering happens in the browser.
Note: Legacy videos created before March 2026 may still reference S3-hosted MP4 files. These are served via presigned URLs and will be migrated to the animated HTML format in a future update.

Narration Scripts

AI-generated narration scripts are stored as JSON on the Rewind_Video__c record in the customer's Salesforce org.

  • Storage location: The customer's Salesforce org, on the Rewind_Video__c custom object
  • Rewind servers: Narration scripts are not stored on Rewind servers. The script is generated in memory, sent back to Salesforce via the callback, and discarded from server memory.
  • Retention: Governed by the customer's own Salesforce data retention policies. The narration persists as long as the Rewind_Video__c record exists.

Billing Data (Stripe)

Payment processing is handled entirely by Stripe. PurposeForce stores minimal billing references.

  • Stripe-side: All payment methods, invoices, subscription details, and billing history are stored by Stripe per their data retention policy
  • PurposeForce-side: Only the Stripe Customer ID is stored, on the Rewind_License__c record in the customer's Salesforce org. No credit card numbers, bank details, or payment method information is stored by PurposeForce.
  • Webhook data: Stripe webhook payloads are processed in memory and not persisted. Only the subscription status and tier are written back to the Rewind_License__c record.

Logs

Application logs are managed by the hosting platform (Vercel) and are not retained long-term by PurposeForce.

  • Vercel function logs: Retained for 1 day on the Free plan, or 3 days on the Pro plan. Logs include request metadata, error traces, and function execution details.
  • Long-term retention: No long-term log retention is configured. Logs are automatically purged by Vercel after the retention window.
  • Log contents: Logs may include API key hashes (not plaintext keys), org IDs, video IDs, and error messages. They do not include Salesforce CRM record data.
Note: If you require longer log retention for compliance purposes, contact hello@purposeforce.org to discuss options.

API Keys

API keys are generated during onboarding and stored exclusively in Salesforce.

  • Storage: The API key is stored on the Api_Key__c field of the Rewind_License__c record in the customer's Salesforce org
  • Backend behavior: The Rewind backend validates incoming API keys against the stored value on each request. The backend does not persist API keys — validation is performed per-request.
  • Rotation: API keys can be rotated at any time by updating the Api_Key__c field. The old key is immediately invalidated.

Summary Table

Data TypeStored On Rewind Servers?Storage LocationRetention
Salesforce CRM dataNoMemory only (during generation)Discarded after API response
Video data (narration + theme)NoRewind_Video__c in SalesforceUntil record is deleted
Legacy MP4 videos (pre-March 2026)Yes (S3)AWS S3Until Rewind_Video__c is deleted
Stripe billing dataNoStripe + Stripe Customer ID on Rewind_License__cPer Stripe policy
Application logsTemporarilyVercel1 day (Free) / 3 days (Pro)
API keysNoRewind_License__c in SalesforceUntil rotated or deleted

Data deletion requests

To request deletion of all data associated with your org, email hello@purposeforce.org with your Salesforce Org ID. PurposeForce will remove any server-side data associated with the org (including legacy S3 videos if applicable) and confirm deletion within 5 business days.

Questions about data handling? Email hello@purposeforce.org or visit the PurposeForce website.