CallSafeMe Privacy Policy
This Privacy Policy explains how CallSafeMe (“we”, “us”, “our”) collects, uses, shares, and stores information when you use the CallSafeMe mobile applications (Android and iOS) and the website https://www.callsafeme.com/.
We do not sell personal information. We do not read or upload contacts from your device address book.
Application purpose
CallSafeMe is a contact-number and safe-calling app for everyday deals. Its purpose is to let you share a CallSafeMe number and a public contact card so that a buyer, renter, or customer can call or message you inside the app when you sell an item, offer a local service, or reply to a listing—without publishing your real phone number. Core features include Identity Numbers, public contact cards, in-app voice calling, messaging, and Discover browsing of public cards.
Google APIs Terms of Service — AI NCII statement
CallSafeMe uses Google Sign-In / Google APIs only to create and authenticate user accounts (receiving Google account identifier, name, email address, and avatar URL for that purpose). CallSafeMe does not use Google APIs, Google user data, or any Google service to create, generate, edit, distribute, or host AI-generated non-consensual intimate imagery (AI NCII). CallSafeMe does not provide image-generation features powered by Google APIs, and Google user data is never used to train or operate AI systems that generate intimate or sexual imagery. CallSafeMe’s use of Google APIs complies with the Google API Services User Data Policy (including the Limited Use requirements) and the Google APIs Terms of Service.
Sign in with Apple — data use statement
CallSafeMe uses Sign in with Apple only to create and authenticate user accounts. We may receive an Apple user identifier (subject) and, if you choose to share them, your name and email address (including an Apple private-relay email when you hide your real email). CallSafeMe does not use Apple user data, Sign in with Apple, or any Apple identity service to create, generate, edit, distribute, or host AI-generated non-consensual intimate imagery (AI NCII). Apple user data is used solely to create, sign in to, and maintain your CallSafeMe account, and to display name information you choose to provide inside the product. We do not use Apple user data for advertising, we do not sell it, we do not share it with data brokers, we do not use it to train generalized artificial-intelligence or machine-learning models, and we do not provide image-generation features powered by Sign in with Apple data. CallSafeMe’s use of Sign in with Apple complies with the Apple Developer Program License Agreement, App Store Review Guidelines, and Apple’s requirements and guidelines for Sign in with Apple.
1. Information we collect
1.1 Google Sign-In data
If you choose Google Sign-In, Google provides CallSafeMe with the following user data (depending on what Google returns for your account): Google account identifier (subject), name, email address, and avatar/profile image URL. We request only the access needed to sign you in (commonly OpenID / email / profile style identity information).
We use Google Sign-In data solely to create, authenticate, and maintain your CallSafeMe account and to display your name/avatar inside the product. We do not use Google user data for advertising, we do not sell it, we do not share it with data brokers, we do not use it to train generalized artificial-intelligence or machine-learning models, and we do not use Google user data or Google APIs to create images. CallSafeMe is not used for AI-generated non-consensual intimate imagery (AI NCII). CallSafeMe’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.
1.2 Apple Sign-In data
If you use Sign in with Apple, Apple provides CallSafeMe with an Apple user identifier (subject) and, if you choose to share them, your name and email address (which may be an Apple private-relay address). We request only the identity information needed to sign you in.
We use Sign in with Apple data solely to create, authenticate, and maintain your CallSafeMe account and to display name information you choose to provide inside the product. We do not use Apple user data for advertising, we do not sell it, we do not share it with data brokers, we do not use it to train generalized artificial-intelligence or machine-learning models, and we do not use Apple user data to create images. CallSafeMe is not used for AI-generated non-consensual intimate imagery (AI NCII). CallSafeMe’s use of Sign in with Apple complies with the Apple Developer Program License Agreement, App Store Review Guidelines, and Apple’s Sign in with Apple requirements.
1.3 Account and product data
- CallSafeMe Identity Numbers we assign (for example #218 758 3921).
- Session authentication tokens so you can stay signed in.
- Contact cards you create: title, description, price, category, visibility settings, optional country/region labels you enter, links, and photos you upload.
- In-app messages, reports you submit, and block lists.
- Discover browsing preferences you set (such as a region filter).
1.4 Call and messaging metadata
- Call invites, room identifiers, call status, and participant user/number identifiers needed to connect in-app voice calls.
- Signaling and TURN relay configuration needed to establish encrypted WebRTC sessions.
- Microphone audio is transmitted between devices for the live call. We do not record, transcribe, or permanently store call audio content.
1.5 Device, push, and diagnostics
- Device platform (Android / iOS) and push notification tokens (for example FCM) for incoming-call and message alerts.
- IP address, approximate request time, user-agent / device type.
- Security and reliability events such as rate-limit hits, lookup events, and basic operational metrics.
- Local on-device caches such as login tokens and dial history used by the app.
1.6 Purchases
If you buy CallSafeMe Pro or another subscription, Apple App Store or Google Play processes the payment. We receive product identifiers, platform, subscription status, and expiry so we can unlock features. We do not store full payment card numbers.
2. Summary table
| Data | Source | Purpose |
|---|---|---|
| Google account id, name, email, avatar URL | Google Sign-In | Create and sign in to CallSafeMe account |
| Apple account id, optional name/email | Sign in with Apple | Create and sign in to CallSafeMe account |
| Identity Number, session token | CallSafeMe | Account identity and authenticated use |
| Cards, photos, messages, reports | You | Core product features and safety |
| Call metadata (not audio recordings) | App use | Connect and secure in-app calls |
| Push token, IP, diagnostics | Device / network | Notifications, abuse prevention, reliability |
| Subscription status | App stores | Unlock paid features |
3. How we use information
- Provide accounts, Identity Numbers, public/private cards, lookup, Discover, messaging, and in-app calling.
- Send transactional notifications for incoming calls and messages.
- Prevent fraud and abuse (rate limits, report handling, bans, audit logs).
- Manage subscriptions and respond to support requests.
- Improve reliability using operational metrics.
- Comply with law and protect users and the platform.
4. How we share information
We do not sell personal information. We share information only as follows:
- Public cards: Content you set to public can be viewed by anyone with the link.
- Other users: People you call or message can see the information needed for that interaction.
- Service providers: Infrastructure used to run CallSafeMe, including Cloudflare (Workers / D1 / R2), Firebase Cloud Messaging for push delivery, and our server host for reverse proxy / TURN. They process data on our instructions to operate the service.
- Google and Apple: When you use their sign-in or app-store billing, under their own policies.
- Legal: When required by law or necessary to investigate abuse or prevent harm.
5. Device permissions
- Microphone: in-app voice calls.
- Camera / photos: card images.
- Notifications: incoming calls and messages, including lock-screen alerts.
- Network / call-related system capabilities: connectivity and reliable call wake-up (platform-dependent).
You can revoke permissions in system settings. Related features may stop working.
6. Retention and deletion
- Account, number, and card data are kept while you use CallSafeMe.
- Call audio is not retained as a recording library.
- Logs and diagnostic events are kept only as long as needed for security and operations, then deleted or anonymized.
- Account deletion: use Settings → Delete account in the app for immediate deletion, or follow CallSafeMe account deletion / email support@callsafeme.com if you cannot sign in. We process email requests within a reasonable period unless the law requires us to keep a record.
7. Your choices and rights
- Edit or archive cards, control public/private visibility, and manage blocks in the app.
- Manage microphone, camera, and notification permissions in system settings.
- Cancel subscriptions through Apple App Store or Google Play.
- Where applicable law provides, request access, correction, export, or deletion by contacting support@callsafeme.com.
8. Children
CallSafeMe is intended for a general adult audience and is not directed to children under 13 (or a higher age required where you live). We do not knowingly collect personal data from children. If you believe we collected a child’s information in error, contact us and we will delete it promptly.
9. International transfers and security
Our infrastructure may be located outside your country (for example via Cloudflare and related cloud services). We use reasonable technical and organizational measures such as encryption in transit, access controls, and least-privilege practices. No internet transmission can be guaranteed 100% secure.
10. Changes
We may update this Privacy Policy. The revised version will be posted on this page with an updated “Last updated” date. Continued use after an update means you acknowledge the revised Policy.
11. Contact
CallSafeMe
Privacy and data requests:
support@callsafeme.com
Home page:
https://www.callsafeme.com/