Privacy · version 2026-09-25-rewarded-ads

Privacy Notice

What we use

We use account details, an encrypted verified mobile number, purchase and Ring records, call metadata, safety events, and the call content needed to operate the service. We do not store the date of birth entered at the age gate; we store the resulting adult attestation or account closure.

Why we use it

We use this data to authenticate accounts, deliver calls, bill accurately, prevent repeated or abusive calling, honour recipient blocks and reports, investigate safety issues, and meet legal obligations.

Phone numbers and suppression

Phone numbers are encrypted for recovery and separately indexed with a one-way value for matching. A recipient suppression record is retained so that their instruction not to be called continues to work.

Account allowances and contacts

Introductory calls belong to your active account rather than to a browser, device or shared network. Each account receives 1 lifetime introductory call for pre-recorded scripted characters; AI characters require Rings. A reserved call is returned only when the call cannot proceed; a completed eligible call is settled once. These records are used for call accounting, not advertising tracking.

Site activity metrics

We use a purpose-specific, server-issued pc_site_activity cookie to estimate browsers and page visits across tabs. It expires after 48 hours, is HttpOnly and SameSite=Lax, and is Secure on HTTPS. Our server stores a one-way identifier, the broad site section, timestamped page entries, and first and last activity times. While signed in, we link activity to your internal account identifier, never an email address, phone number or contact record. We also record successful quote and checkout issuance references to measure their subsequent call completion or purchase credit using existing server records. No destination, scenario, transcript or payment details are copied into analytics. Repeated page entries and checkout retries are deduplicated. We do not track activity across sites. The displayed visitor count is an estimate of active browser sessions, not a count of unique people. Records older than 48 hours are excluded from metrics and removed during routine activity cleanup. Purpose-specific keyed network hashes limit rapid activity messages in server memory; these expire after one minute and are never stored with activity records.

You can turn off these site activity metrics here at any time. This stops future activity messages from this browser, clears the activity cookie, and requests removal of this browser session's activity, page entries and funnel observations. Financial and call records are retained separately for their operational purposes. Your choice is saved in this browser until you turn metrics back on or clear site storage. A separate pc_site_activity_disabled cookie stores only this on/off preference, for up to one year, so our APIs honor an opt-out even if activity deletion is temporarily unavailable. It is SameSite=Lax and Secure on HTTPS; turning measurement on removes it.

Recordings and transcripts

Whether a call is recorded is decided by the applicable call policy. Access is limited to the account owner and authorised operators, subject to recipient controls and retention rules.

Reaction likes and listens

Character and reaction likes are separate, account-linked choices. A reaction listen is counted after three seconds of visible, forward playback in our player. Signed-in listens are deduplicated by account. When you play a reaction while signed out, we set the encrypted pc_reaction_engagement cookie for 30 days, restricted to reaction API requests. It is HttpOnly, Secure and SameSite=Lax. We store a purpose-specific one-way identifier with the clip listen, not the cookie itself. It is not used for advertising, calling allowances, recipient identification or tracking across other sites.

We use short-lived keyed account and network hashes to limit rapid engagement requests; these in-memory rate-limit records expire after one minute. You can remove the engagement cookie by clearing this site's cookies. Blocking or clearing cookies, changing browser or signing in can affect deduplication. These counts are not proof of a unique person or protection against every manipulated playback request. Recipient withdrawal, retention and publication controls still determine whether a clip is public.

Reporting public reactions

You can report a public reaction without an account or phone number. We store the reaction release identifier, your selected reason and any details you choose to send for authorised moderation. Please do not include names, phone numbers or other private details. Reports are separate from recipient call-blocking requests.

On a successful report we set the encrypted pc_reaction_report security cookie for 30 days, restricted to reaction API requests, with HttpOnly, Secure and SameSite=Lax protections. A separate purpose-specific one-way identifier is stored with your report to prevent duplicate reports for the same release. It is not linked to your likes, listens, account or calling allowance. Short-lived keyed network and reporter values limit rapid requests in memory and expire after one minute. Clearing site cookies can affect duplicate detection; this is not proof of a unique reporter. Report evidence and operator review notes remain available for safety investigations when media is withdrawn or expires, subject to the final approved retention policy.

Service providers

We use contracted providers for authentication, email, telephony, payments, hosting, and voice or language processing. They receive only the data needed to provide their service.

Your choices

You may request access, correction, deletion, or restriction where applicable, and object to or withdraw optional processing. Recipients can block calls and report a call without creating an account.

Contact

Data controller: Syed Shah

Email: privacy@prankcall.app