1. Who is responsible and how to contact us
Dial Backup, LLC operates dialbackup.com and determines how account and service data are used. Our mailing address and contact email appear above. Send privacy questions to info@dialbackup.com or use the privacy request form. You do not need to create an account or accept our terms to submit a privacy request. This notice covers visitors, account holders, and people whose contact details are supplied by a user.
2. Information we collect and its sources
- Account and eligibility: email, name and profile information you or Google provide; phone number and verification status; language; password and hotline PIN credentials where used; and the version and time of your terms acceptance and 18+ confirmation. We do not ask for a date of birth or identity document in the ordinary signup flow.
- Contacts: when you choose sync, Google supplies contact names, phone numbers, and available email addresses. We store those fields, source, favorites, and sync timestamps. Read-only permission does not mean session-only storage. Contact details may concern people without a DialBackup account.
- Calling and verification: telephone numbers needed to connect a call, provider call identifiers, selected contacts, timestamps, duration, status, and billing calculations; phone verification requests and results. Twilio processes call audio to connect calls and limited speech input for menu navigation. Our application does not enable conversation recording. Providers may maintain their own operational records.
- Payments: PayPal order and capture IDs, amount, currency, purchased minutes, payment status, and account linkage. We do not receive or store your full payment-card number or PayPal password. PayPal separately processes payment, identity, and fraud information under its own notice.
- Technical, security, and requests: hosting and telephone providers may receive IP addresses, browser and device information, request logs, error and abuse information. We record essential account, sync, call, and payment events, and the contact details, content, status, and response records of support or privacy requests.
Do not send passwords, PINs, card details, government IDs, health information, or other unnecessary sensitive information in support or privacy-request text.
3. Why we use information
We use account, contact, calling, and payment data to deliver requested contact backup and calling, manage prepaid minutes, authenticate users, verify phone control, respond to requests, and provide payment recovery. We also use limited records to prevent abuse, secure the service, investigate errors and disputes, and meet applicable legal obligations. We do not use Google Contacts for advertising, sell address books, or use contact information to train generalized AI models.
DialBackup's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Contacts data only to provide the contact backup and calling features you request, and people at DialBackup do not read it except with your permission, for security purposes, or where required by law.
Where European or UK data-protection law applies, the bases are performance of our contract for account and paid-service operations; legitimate interests in protecting the service, resolving disputes, and enabling the personal communications users request, balanced against affected people's rights; and compliance with applicable legal obligations. Where we rely on consent for an optional use, we will seek a separate, specific choice and provide a way to withdraw it. Google's authorization screen is a permission to access Google data, not blanket consent for unrelated processing.
Account and payment information needed to provide a requested service cannot simply be omitted while that service is supplied. Google Contacts sync is optional. We do not use solely automated decisions that produce legal or similarly significant effects as a business feature; contact us to request human review of a security or account restriction.
4. Who receives information
Google handles Google sign-in and authorized Contacts access. Google Cloud hosts the application and database. Twilio processes telephone, verification, and call-routing data, including the number called and audio necessary to connect calls. PayPal processes checkout and payment data. We use these services only for the purposes described here; some providers, particularly payment and account providers, also act independently for their own legal, security, or account obligations. Their own privacy notices apply to those activities.
People you call and their telephone networks receive information needed to complete the communication, which may include caller information. We may disclose information where reasonably necessary to comply with a lawful request, protect rights or safety, investigate misuse, or carry out a corporate transaction with appropriate safeguards and notice where required. Access by people administering DialBackup is limited to service, support, security, and compliance work.
5. Cookies, browser preferences, and advertising
We use session and security cookies for sign-in and a short-lived, signed cookie to carry your age and terms confirmation through Google sign-in. These cookies support functions you request. We do not enable advertising pixels, cross-site behavioral advertising, optional analytics cookies, or public page-view event collection in this application. Essential operational events, such as a completed payment, remain necessary to run the service.
We do not sell personal information or share it for cross-context behavioral advertising, and we do not use sensitive information to infer personal characteristics for advertising. Global Privacy Control and Do Not Track do not enable any such activity: optional page-view collection stays off for everyone. If we introduce optional tracking, we will update this notice and provide any required prior consent and opt-out controls before enabling it. Your browser can block cookies, although sign-in may then stop working. Google and PayPal manage cookies on their own sites when you choose to visit them.
6. Retention, deletion, and security
Account information and synced contacts are kept to support your active account and requested service. Disconnecting Google removes stored Google authorization tokens and synced Google contacts from our active database and attempts to revoke provider access. You can also revoke access in your Google Account.
Call and purchase history support account history, billing reconciliation, disputes, and applicable legal obligations. Deleting an account removes its active account, linked credentials, contacts, calls, and in-app purchase receipts and deletes analytics records linked by account ID or email. Save receipts and raise billing or refund questions before deleting; deletion does not waive legal claims. Privacy-request correspondence may be retained separately to verify and demonstrate how the request was handled. Retention is assessed against the service purpose, an unresolved request or dispute, applicable recordkeeping duties, and legal holds.
Deletion from our active database does not immediately remove copies in provider logs, backups, or records PayPal, Google, or telephone providers keep for their own obligations. Those copies follow their retention and recovery processes. We do not promise that every log or backup is removed within 30 days. Contact us for details relevant to your request or about remaining records.
We use encrypted connections, access controls, hashed passwords, and other technical protections. New and updated hotline PINs are hashed; legacy PINs are upgraded on successful use. No system is perfectly secure. We investigate suspected incidents and make notifications required by applicable law.
7. Your choices and privacy rights
In Settings, you can correct profile details, download account data in JSON, disconnect Google and remove synced Google contacts, or delete an account. The export excludes authentication secrets. Use the request form or email info@dialbackup.com for additional access, correction, deletion, portability, restriction, objection, limits on use, complaints, or an appeal. Contacts without accounts can use the same methods.
Where applicable, California and other U.S. state laws provide rights to know and access categories and specific information, correct inaccuracies, delete information, and opt out of sale, targeted advertising, sharing, or certain profiling. California law may also provide a right to limit certain sensitive-information uses. We do not conduct those sale or advertising activities. We do not discriminate or retaliate for exercising a privacy right. Authorized agents can submit requests, subject to reasonable verification of authority and identity.
Where GDPR or UK GDPR applies, rights may include access, rectification, erasure, restriction, portability, objection, and withdrawing consent for processing based on consent. You may complain to your local supervisory authority, including an EU data-protection authority or the UK Information Commissioner. A request can be subject to legal exceptions; we will explain any refusal or required verification and how to challenge it.
Our initial response target is within one calendar month, and we will follow any shorter applicable deadline. If a lawful extension or exception is needed, we will explain it as required. A request receipt is not confirmation that we have verified identity or completed deletion. Send an appeal using the form's appeal option or by replying to our decision. We will explain the applicable appeal process and regulator complaint route.
8. Children and age information
Accounts are restricted to people 18 and older. We request an affirmative adult confirmation and terms acceptance before account creation, including before Google sign-in, and before existing accounts resume covered service activity. We do not offer a parental-consent signup program for minors. If we learn a child's account or information has been collected improperly, we will restrict use, assess the report, and remove or otherwise handle it as required. Parents and guardians can select "Report a child's data" on the request form.
An adult user may have contact details concerning a minor in an address book. That is different from offering an account to a child, but the information remains subject to this notice and applicable rights. We do not use child contact details for advertising or unrelated profiling. The ordinary age check is self-attestation; it is not a claim that all device age-signal or identity-verification laws have been implemented.
9. International processing and changes
Dial Backup, LLC is in California and the application's current hosting is in the United States. Providers may process information in other countries. Where applicable law requires a transfer safeguard, the relevant processing arrangement must include an appropriate mechanism, such as approved contractual safeguards or an applicable adequacy framework. Contact us for information about the mechanism and safeguards for a particular transfer. This notice is not a claim that Dial Backup, LLC is certified under the EU-U.S. Data Privacy Framework.
We will update this page when practices change and identify the effective version. Material account-related changes will be presented in the service before renewed covered activity. We will obtain a separate choice where a new use requires consent. Earlier transactions and existing statutory rights are not retroactively waived by an update.
