RecallPulse Business — Data Processing Terms

The Customer is the Data Fiduciary (controller) of the call data its reps share. RecallPulse is its Data Processor.

Work-SIM call details, rep identity and device health, as listed in section 8 of our Privacy Policy, only to provide the dashboard, sync, device-health views and CSV export to the Customer.

We process this data only on the Customer's documented instructions — using the dashboard counts as instructions — and tell the Customer if we believe an instruction breaks the law.

HTTPS in transit; passwords stored as one-way hashes; two-factor authentication on every dashboard account; each organisation's data kept separate; a separate access token for each phone; an audit log of important actions; access to production systems limited to the people who run RecallPulse.

Railway (hosting, United States), Resend (email, United States) and Google (sign-in, global). We tell Customers before adding a sub-processor, and they can object.

As set out in section 7 of our Terms: tell employees about the sharing, never require a personal SIM to be shared, have a lawful basis and any required impact assessment, limit dashboard access, choose a retention period and delete what is no longer needed.

We help the Customer answer access, correction and deletion requests from reps and from the people on their calls.

We tell the Customer without undue delay, and within 72 hours of learning of it, about a breach that affects its data.

When the owner asks, we delete the Customer's data within 30 days; otherwise we delete it 12 months after the subscription ends. Invoices are kept for 8 years.

Data is processed in India and the United States. The Customer may send us security questions by email once a year, and we answer in writing.