FAC (Paid) Privacy Policy

Effective date: November 9, 2026

Who we are

Excelltech Inc., based in the United States (“Excelltech,” “we,” “us,” or “our”), provides the paid FAC app, also known as Fake-A-Call, and its associated scheduling service. We are responsible for the personal information we process as described in this policy.

Contact us at excelltechmobile@gmail.com.

This policy applies to the paid app. The separate FAC Free app has its own Privacy Policy. The paid app contains no advertising. Buying the app or subscribing does not disable the analytics and crash reporting described below.

Caller content and permissions

FAC simulates calls on your device. It does not place telephone calls to other people or provide emergency calling.

Your saved caller profiles, selected photos, recorded or imported audio, local call settings, and FAC Recents history are stored in the app on your device. FAC does not upload your caller photos or audio recordings to our servers, analytics services, or advertisers. Selected caller names and scheduling details are sent to our service when you use Call Later, as explained below.

Microphone and photos. Microphone permission is used when you choose to record caller audio. FAC does not record your conversations or transmit microphone audio during simulated calls. You can revoke microphone permission in your device's Settings. You select individual photos through Apple's photo picker; FAC does not request access to your entire photo library. FAC does not request GPS or device location permission.

Choosing a contact. If you use the contact picker, Apple's system interface shares the contact you select. FAC copies its display name and available photo into your caller setup. FAC does not request general address-book access, copy the selected contact's phone numbers, email addresses, or postal addresses, or keep the saved caller synchronized with Contacts. Changes in FAC do not edit your original contact. The copied name can be sent to our scheduling service if you use that caller for Call Later; its photo stays in the app.

Importing audio. If you choose an audio file through Files, FAC reads that selected file and converts it into a local audio copy for playback. It can retain the original filename as the clip's display name on your device. The file's audio and filename are not sent to our scheduling, analytics, or advertising services. The Files provider, including iCloud Drive or another provider you use, may download the source file and process that access under its own terms. Removing the imported copy from FAC does not delete the original file from Files or its provider.

When Show calls in Phone Recents is enabled, iOS can place simulated-call entries in the system call history. This setting is enabled by default. Switching it off affects future entries; existing entries must be managed in the Phone app. Caller names and images may also appear on incoming-call screens or the Lock Screen, depending on your device settings.

Apple or your computer may include app data in device backups, and Apple may manage or synchronize system call history according to your settings. These system services are separate from FAC's servers. FAC does not provide its own cloud backup or synchronization of your photos or recordings.

Information processed by our online services

Scheduling and authentication. When FAC connects to check scheduling access or to use Call Later, we process a randomly generated installation identifier, a Firebase anonymous authentication identifier, and Apple-signed proof that you acquired this app. Registering for scheduled calls also sends a device push token. Creating a schedule sends the chosen caller's name and identifier, a recording selection identifier, the scheduled time, and identifiers used to manage that request. We store status, delivery acknowledgments, cancellation information, and related timestamps. The app also reports whether it could present a scheduled call, an applicable failure category, the report time, and app version and release-channel information to help diagnose delivery problems. The recording identifier selects local audio; it does not contain the audio or its local filename.

You do not need to supply a name, email address, or password to create a FAC login. An anonymous sign-in protects service requests, but its identifiers still distinguish your installation and can be personal information. They are not fully anonymous data.

Purchases and free-call allowance. Apple processes payments. We receive and verify signed app and subscription information, including transaction identifiers, the purchased product, subscription expiration and renewal status, and refund or revocation information. We associate authorized installations with that access. We use a hashed version of Apple's identifier for your acquisition of this app to maintain the lifetime free-call allowance across devices and reinstalls. Subscription records also retain the Apple-issued app-acquisition identifier itself to verify that the subscription belongs to the same app account. These identifiers do not give us your Apple Account email address or password. We do not receive your payment-card details.

Usage analytics and diagnostics. FAC uses Google Firebase Analytics and Crashlytics. Reports include a random app-user identifier, app and operating-system information, device characteristics, app openings, feature use, call counts, call durations and outcomes, scheduled times, cancellations, free-call or subscription usage, purchase product identifiers, and crash or error diagnostics. Diagnostic events may include random call identifiers and how late a scheduled call appeared to be when the app opened.

These reports do not include caller names, photos, recording contents, authentication credentials, or push tokens. FAC configures Analytics without advertising-identifier or vendor-identifier collection and disables advertising personalization. Google may process network information and derive approximate geography for analytics and service operation. The random app-user identifier is separate from the Apple app-account identifier used for the free-call allowance.

Analytics and crash reporting are enabled automatically in the current app. There is currently no in-app analytics or crash-reporting opt-out. Local Call Now keeps caller content off our scheduling server, but can still generate usage and diagnostic events.

Service diagnostics. Separate from app analytics, our backend records operational events containing call or purchase reference identifiers, the app edition, scheduled and delivery times, retry counts, status and failure categories, free-call or subscription funding, and push-service response identifiers. Delivery reports can also include app version and release-channel information. These application logs exclude caller names, photos, audio, payment credentials, and authentication or device push tokens. They help us investigate delayed or failed calls and purchase-verification problems.

Connection and support information. Our hosting and authentication providers process connection details such as IP addresses, request times, and technical metadata to operate and secure the services. If you contact us, we receive your email address and the information you choose to send. Please do not send passwords, payment details, or unnecessary private caller content.

Why we use information and who receives it

We use information to deliver and manage scheduled calls, verify purchases, restore access, administer free-call allowances and usage limits, secure the service, prevent misuse, understand feature use, diagnose failures, and answer support or privacy requests.

Google provides our cloud hosting, database, authentication, analytics, and crash-reporting services. Apple provides App Store purchases and push delivery, and manages the system calling interface. Scheduled-call push messages pass through Apple and can include the selected caller name, caller and recording identifiers, and timing information. Audio and photo files are not included.

We may disclose information when legally required, to establish or defend legal claims, or when reasonably necessary to investigate fraud or protect people or the service. If the business or app changes ownership, relevant information may transfer to the successor subject to applicable law and appropriate notice.

The paid app does not supply data to an advertising network. We do not sell its users' personal information for money or use it for advertising based on activity across other companies' apps or websites.

For additional information about our providers, see Google’s Privacy Policy, Firebase privacy information, and Apple’s Privacy Policy.

How long information is kept

• On-device content: stays until you remove it or delete the app and its local data. FAC Recents retains up to 200 entries. A recording or caller snapshot may remain while another saved caller, pending call, or active call still uses it. Device backups and Phone Recents must be managed separately. Some authentication identifiers stored in the device Keychain can survive reinstalling.

• Server call records: become eligible for automatic deletion seven days after the scheduled call time. Canceling a call changes its status; it does not immediately erase the record.

• Device registrations: become eligible for deletion after 90 days without registration activity.

• Operational counters: scheduling-limit records become eligible for deletion after two days. Other request, registration, and purchase-verification counters become eligible after one or two days, depending on their purpose. Cancellation markers and processed purchase-notification identifiers become eligible after 35 days.

• Purchase, access, and free-call records: have no automatic expiry in the current service. We retain subscription and access records to support restoration, renewals, refunds, and abuse prevention. We retain the limited hashed account identifier and free-call usage count to administer the lifetime offer. Reinstalling or clearing local history does not reset it. These records remain subject to applicable deletion rights and lawful retention exceptions.

• Authentication records: remain until deleted through the authentication service, subject to that provider's deletion and backup processing.

• Analytics: Google Analytics is configured for two months of event-data retention and 14 months of user-data retention. The user-data period restarts with new user activity, so a regularly active user's identifier can remain for longer than 14 months in total. Google's user-data period also applies to key-event data. Expired data is removed through Google's monthly deletion process. These settings do not expire standard aggregated reports and do not control separate diagnostic exports. See Google’s retention explanation.

• Crash and session diagnostics: Google states that Crashlytics starts removing crash traces and associated identifiers after 90 days. We also use a separate Google BigQuery export for crash and session diagnostics. The export has no automatic expiry configured, so exported copies can remain longer than the Crashlytics retention period, until separately deleted. We use these records to investigate faults and compare reliability across app versions; they remain subject to applicable deletion rights. See Firebase’s retention information.

• Service logs: ordinary cloud logs, including separate delivery and purchase-verification diagnostics, are configured for 30 days; certain cloud administration and audit logs are retained for 400 days. Exported service-log records in BigQuery are configured to expire after 30 days. The seven-day call-record deletion period does not delete these separate diagnostic logs.

• Backup and recovery copies: the scheduling database keeps up to seven days of version history, and its daily backups are configured for seven-day retention. Provider recovery systems can retain copies after an active record expires; those copies are separate from the app's ordinary live records.

• Support correspondence: is retained as needed to handle your request, keep a record of its resolution, and meet applicable legal obligations or resolve disputes.

Automatic deletion and removal from backup systems are not instantaneous. We may keep information longer where a specific legal obligation or valid legal hold requires it.

Your choices and privacy rights

You can edit or remove caller content, clear FAC Recents, cancel pending schedules, change Phone Recents behavior, and revoke microphone permission. A scheduled call is canceled only when the service confirms cancellation before delivery begins. Removing a caller or changing a recording does not automatically change an existing scheduled-call snapshot.

Deleting the app removes its ordinary local data, but does not automatically erase server records, provider records, Keychain items, backups, or system call history. It also does not cancel an Apple subscription. Manage subscriptions in your Apple Account settings.

To request access, correction, deletion, or other assistance with information we hold, email excelltechmobile@gmail.com and identify whether you use FAC Paid or FAC Free. We may need limited additional information to locate the relevant installation or purchase and verify an access or deletion request. We will not ask for your Apple Account password or full payment details. Because our operational records do not contain your email address, emailing us alone may not identify those records. We will explain any inability to identify data or any lawful reason for retaining it.

Depending on your location and the law that applies, you may have rights to obtain a copy of information, correct it, delete it, restrict or object to processing, request portability, withdraw consent, and complain to a data-protection authority. Some US laws also provide rights to opt out of sale, sharing for cross-context behavioral advertising, or certain profiling, and to appeal a denied request. You can contact the same email to submit an appeal. We will handle requests within the applicable legal time limits and will not unlawfully discriminate against you for exercising your rights. Where permitted, an authorized agent can submit a request with appropriate proof of authority. Withdrawal of consent does not affect processing that was lawful before withdrawal.

International processing and regional legal grounds

Excelltech is based in the United States, and our scheduling database is hosted in the United States. Apple and Google may process information in other countries where they operate. Privacy laws in those countries may differ from those where you live.

Where EEA or UK data-protection law applies, our grounds for processing include performing our agreement with you for requested scheduling and purchase services; legitimate interests in securing the service, preventing abuse, and handling support, subject to your rights; and compliance with legal obligations where applicable. Information required to authenticate, verify access, or deliver a scheduled call is necessary for those features; they cannot operate without it.

Usage analytics and crash reporting help us understand feature use and improve reliability. They are enabled automatically as described above. Downloading the app, accepting its terms, or reading this policy is not treated as consent to processing that requires separate consent. You can contact us to raise an objection or make a privacy request; there is no in-app switch that disables these services.

Google's applicable Cloud Data Processing Addendum and Firebase Data Processing and Security Terms describe the contractual protections for the cloud and Firebase services we use. Their transfer provisions provide for recognized data-transfer frameworks and, where applicable, standard contractual clauses. For information about the safeguards relevant to your data, contact us at excelltechmobile@gmail.com. Apple's and Google's own privacy notices explain their separate processing and international-transfer arrangements.

Children and teenagers

FAC is intended for people aged 13 and older and is not directed to children under 13. If you are under the age of legal adulthood, your parent or guardian should review this policy and the Terms of Use with you. Higher local age requirements and parental-consent requirements still apply.

If you believe a child under 13 has provided personal information to our services, contact us. We will investigate and remove information where required by applicable law. Apple's content age rating is separate from these eligibility requirements.

Security and changes

We use measures designed to protect information, including encrypted network connections, authenticated service requests, and access restrictions. No storage or transmission system can be guaranteed completely secure.

We may update this policy as the app, providers, or legal requirements change. We will update the effective date and provide additional notice or request consent when required. This policy explains our practices; it does not replace any separate consent required by law.