Privacy Policy

1. What We Collect

• Device permissions data: Contacts, camera, media, microphone, and notifications are used only for features you explicitly enable. The normal simulated-call path does not request camera or microphone access.
• Authentication data: When you sign in with Google, Apple, or email, our self-hosted auth service processes your account identity and session tokens.
• Subscription data: RevenueCat on mobile and LemonSqueezy on web process billing and subscription events.
• Advertising data: Google AdMob on mobile and Google AdSense on consented public web pages may collect device or browser identifiers, approximate location, IP address, and ad interaction data.
• Product usage data: We log first-party events such as completed calls, shares, entitlement state, and app version checks to operate the service and improve quality.
• Web analytics: The website uses Plausible to measure page traffic and navigation patterns.

2. How We Use Data

• To run simulated calls, character galleries, dashboard stats, and community previews.
• To authenticate users and restore sessions across devices.
• To validate purchases, restores, cancellations, and premium entitlements.
• To measure usage, improve quality, and detect abuse or fraud.
• To serve ads in free surfaces where consent and platform policy allow it.
• To respond to support and legal requests.

3. Third Parties

• Google AdMob / AdSense: Advertising and measurement. Google Privacy Policy
• RevenueCat: Mobile subscriptions and restore handling. RevenueCat Privacy Policy
• LemonSqueezy: Web checkout and billing events. LemonSqueezy Privacy Policy
• Plausible: Website traffic analytics on fakecallapp.com. Plausible Privacy

4. Permissions

• Camera and microphone: Used for optional reaction recording only after a per-session disclosure, an explicit Start recording action, and both operating-system permissions. A visible REC timer and Stop control remain on screen.
• Contacts: Optional local caller identities from your address book.
• Media: Optional custom caller assets and user-directed sharing of a temporary reaction copy.
• Internet: Auth, entitlements, ads, blog/community content, analytics, and version checks.

5. Storage and Retention

App settings, call history, and custom local assets are primarily stored on your device. Server-side entitlement, community, analytics, and support-related data are retained only as long as operationally, contractually, or legally necessary.

A completed reaction capture is staged temporarily. It moves into JoltCall's private app storage only when you choose Keep in JoltCall; this is not a system photo-gallery save. Sharing uses a temporary copy. Skip, delete, sheet dismissal, leaving the simulation, and stale-file cleanup remove unretained captures.

6. Your Choices

• You can deny or revoke permissions in device settings at any time.
• You can stop recording at any time from the persistent REC control.
• You can delete an unretained reaction instead of keeping or sharing it.
• You can decline web ad consent on public monetized pages.
• You can uninstall the app or clear app data to remove local-only data.
• For account-related help, email support@fakecallapp.com.

7. Security

• Traffic is sent over HTTPS/TLS.
• Session tokens are stored using platform storage mechanisms.
• We keep data collection scoped to what the product actually needs.

8. Contact