Privacy Policy — Recall

Effective Date: April 15, 2026

Last Updated: August 10, 2026

Recall: Recall, operated by Joseph Cornaggia ("we," "us," or "our")

1. What Recall Is

Recall is a customer-memory application for independent sellers and sales professionals. It helps users capture, structure, and find details from customer conversations using voice notes and AI-assisted extraction.

Recall is a productivity and customer-memory tool. It is not a CRM, medical-record system, loan-origination system, insurance policy system, legal matter-management system, password manager, document vault, compliance archive, or employer system of record.

2. What Data You Enter

You may choose to enter customer names, contact details, notes, product interest, follow-up reminders, objections, deal context, and other sales-relevant information.

Customer profiles and saved notes are stored locally on your device by default. Sign in with Apple links subscription identity and purchase restoration. Customer Book Backup is separately controlled in Settings. If enabled, Recall stores the current encrypted backup and, for reliability, up to one immediately preceding encrypted revision so you can restore an empty install. Recall does not provide staff with a routine browsing dashboard, although limited authorized operational access or legally required disclosure may occur.

Backups may include customer names and contact details, profiles, sanitized notes and transcripts, product/service and follow-up context, selected workspace and business-card settings, supported order records, Loose End state, prompt history, and deletion tombstones. Raw audio, usage counters, AI telemetry, subscription records, tokens, and device secrets are excluded.

3. Audio, Transcription, and AI Processing

When you submit a recording or note for AI processing, Recall sends the relevant content through Recall’s AI proxy for transcription and structured extraction. Before a user’s first voice capture, the app discloses this provider processing and links to this policy.

In the production privacy mode, raw recordings are sent through Recall's secure AI proxy to OpenAI for transcription. Recall does not copy raw audio to a second provider as a fallback. Recall removes detected phone numbers, email addresses, credentials, account identifiers, patient identities, and other blocked sensitive values from the transcript before sending it to OpenAI for structured extraction. A server-side check rejects extraction input that still contains obvious unsanitized contacts or blocked values. Automated detection is a risk-reduction measure and cannot guarantee that every sensitive phrase will be recognized.

For AI processing requests, Recall’s AI proxy processes requests in transit and does not retain customer profiles, audio, transcripts, prompts, or extracted notes as a persistent cloud customer database. Its operational logs contain timing, selected provider/model, response status, cache-token counts, request/quota identifiers, and similar technical data designed not to contain customer content. Hosting infrastructure retains those operational logs according to its configured service plan. Optional Customer Book Backup is separate and described below.

Recall does not opt submitted OpenAI API content into model training. Structured-extraction requests include store: false; OpenAI's standard API data controls may still retain limited transcription content, extraction inputs and outputs, and metadata for abuse monitoring for the provider's stated period (currently up to approximately 30 days) unless Recall's account receives an approved stricter data-control arrangement.

Submitted content may be processed by Recall’s AI proxy and AI providers in jurisdictions outside your country as needed to provide the service.

Audio is uploaded only when you submit a recording for transcription. By default, the local recording file is deleted from your device after processing unless you enable an available on-device retention setting.

4. Sensitive and Regulated Data

Recall is designed to preserve sales-relevant context while avoiding extraction or storage of sensitive personal, health, financial, credential, and regulated document contents.

Do not record, enter, upload, or store information in Recall that is unnecessary for sales follow-up, including:

• Social Security numbers, driver-license numbers, passport numbers, full dates of birth, or similar identity-theft-sensitive data
• Credit-card numbers, bank-account numbers, routing numbers, payment credentials, full credit reports, full loan applications, tax returns, exact income/assets/debts, or account statements
• Passwords, API keys, access tokens, portal credentials, gate/alarm/garage/lockbox/security-camera codes, or other access credentials
• Protected health information, patient names, patient identifiers, medical-record numbers, diagnosis or treatment details, lab results, medical images, insurance member IDs, or patient billing details
• Legal strategy, privileged legal advice, court filing text, signed engagement or retainer agreements, confidential settlement terms, or trust-account details
• Confidential security materials, security questionnaire answers, SOC 2 report contents, penetration-test reports, or vulnerability details

Recall’s templates and AI prompts are designed to ignore blocked sensitive values and retain only non-sensitive business context when possible. For example, Recall may preserve “clinic asked for HIPAA review before trial” while avoiding patient names or medical-record details.

You are responsible for reviewing AI-generated extractions before saving or exporting them.

5. Medical Sales and Health Information

Recall is not designed to store PHI, patient records, or clinical chart content. Unless a separate written agreement says otherwise, Recall is not acting as a HIPAA Business Associate and should not receive, store, or manage protected health information.

Medical sales users should capture only sales-relevant account context, such as clinical champion, value-analysis status, reimbursement question, trial/evaluation stage, training need, or evidence request. Do not store patient-identifying information or patient-specific clinical details in Recall.

6. Usage, Subscription, and Operational Data

Recall may store limited product events locally on your device to support app operation, subscription/trial flows, and troubleshooting. To authenticate optional Customer Book Backup, verify subscription access, enforce usage limits, prevent abuse, and operate the service, Recall's servers and service providers may also process pseudonymous app-user or recovery identifiers, subscription and entitlement status, request counts, timestamps, feature or operation type, technical status/error information, and limited security logs.

These operational records are designed not to include customer names, customer contact details, notes, transcripts, search queries, or audio. Customer content submitted for AI processing is handled separately as described in Section 3, and an optional recovery backup is handled separately as described in Sections 2 and 8.

Recall does not sell customer records, use customer notes for targeted advertising, license individual customer data, or share personal information for cross-context behavioral advertising. Because Recall does not sell or share personal information in that sense, California “sale” and “sharing” opt-out rights should not apply to Recall’s current practices.

7. Your Responsibilities

You are responsible for using Recall consistently with applicable laws, customer notices, consent requirements, employer policies, industry rules, record-retention obligations, and professional duties.

If your employer requires customer data to be stored in an approved system of record, use that system. Do not use Recall to bypass employer systems, duplicate restricted records, evade retention rules, or export customer information without authorization.

8. Data Export, Deletion, and Retention

• Local device data: Retained until you delete it, delete the app, wipe the device, or use available deletion controls.
• Customer Book Backup: If enabled, the current encrypted backup and up to one preceding encrypted revision are retained until replaced or deleted. Deletion removes encrypted customer-book content; minimal pseudonymous revocation/security records may remain. Deleting backup content does not cancel an Apple subscription or erase Apple/RevenueCat purchase records.
• Audio recordings: Deleted after processing by default unless you enable on-device retention.
• Transient AI-provider content: OpenAI transcription and extraction requests are not stored by Recall as application objects, but provider abuse-monitoring records expire under OpenAI's retention process and are not presently exposed to Recall for per-request deletion. Deleting local data or Customer Book Backup therefore propagates to Recall-controlled persistent copies, but cannot accelerate a provider's limited security-log expiration.
• Exports: If you export data, you are responsible for protecting and deleting exported files.
• Device backups: iOS or employer-managed device backups may include local app data depending on your settings and device-management policies.

9. Third-Party Services

We use AI providers whose API terms state that submitted content is not used for advertising or model training unless Recall, as the API account holder, separately opts in. Recall does not opt in. Recall transmits content only to provide the requested app feature and applies the data controls described in Section 3.

Recall may disclose information when required by law, valid legal process, or necessary to protect the security, rights, and safety of Recall, users, or others.

10. Data Security

Recall uses HTTPS/TLS for AI, account, and backup requests, encrypts backup snapshots at rest, and relies on iOS device-level protections for local data. You should protect your device with a strong passcode, Face ID or Touch ID, current OS updates, and any employer-required device-management controls.

No security system is perfect. If we learn of a security incident affecting data for which Recall is responsible, we will provide legally required notices.

11. Children’s Privacy

Recall is intended for adults using it in professional settings. We do not knowingly collect information from children under 13.

12. Changes to This Policy

We may update this policy. When we do, we will update the “Last Updated” date and provide notice where legally required.

13. Contact

Questions or requests:

Email: privacy@recallforsales.com

Mailing: Recall, c/o Joseph Cornaggia, 3031 Stanford Ranch Rd, Ste 2 - 1086, Rocklin, CA 95765-5554, United States