BlueCaller Inc. Privacy Policy
Effective date:
Who we are and what this policy covers
BlueCaller Inc. is responsible for the personal information handled through this coming-soon website and preregistration service. Contact us about privacy at [email protected]. Our business mailing address is 85 Knoxdale Road, Ottawa, Ontario K2G 1A4, Canada. This policy covers visiting the website, joining the launch-update waitlist and contacting us about those activities. It does not describe a future BlueCaller application or services that are not available here.
Information we collect and why
- Waitlist details: email address, country (Canada or United States), postal or ZIP code, and primary trade if you choose to provide it. We use these details to administer preregistration, understand geographic and trade interest, and provide the launch updates you request. Email, country and postal or ZIP code are required; trade is optional. You can browse without registering.
- Consent records: the time of registration, the launch-email consent wording and version, and a withdrawal date if consent is withdrawn. These records help us respect your choices and document the basis for sending updates. The launch-update checkbox is unchecked initially. We do not verify email ownership or send automated emails through the preregistration form.
- Campaign attribution: approved campaign codes in the landing-page URL and the referring website’s hostname. These are stored with a new registration to understand how visitors find BlueCaller, even if optional analytics is declined. We do not store full referring URLs, advertising click identifiers or browsing history in the registration record. Unapproved campaign values are discarded.
- Security and connection information: hosting and bot-protection services receive request information such as IP address, browser/device and connection metadata. The waitlist Function uses the request IP address and normalized email to generate keyed hashes for rate-limit counters; it does not store raw IP addresses in the waitlist database. The challenge token is sent to Cloudflare for verification. These measures help prevent automated abuse and protect the service.
- Requests you send us: your email address, message and information reasonably needed to answer a privacy request or verify that you are entitled to make it. Please do not send sensitive documents unless needed and requested.
Launch updates and your choices
Registering requires your affirmative consent to email updates about BlueCaller’s launch. This is separate from optional analytics. A duplicate submission does not replace the existing registration, change recorded details or restore consent that was withdrawn. To withdraw launch-email consent, correct your details or request deletion, email [email protected]. Withdrawal stops the future launch updates covered by that consent; it does not make earlier lawful processing unlawful. Deleting a registration also removes its associated consent record, subject to any legally required retention.
Launch communications and future launch announcements use [email protected]. No launch emails are sent by the present preregistration service. Before email delivery begins, messages must identify BlueCaller Inc., provide the required contact information and a working unsubscribe method, and honor unsubscribe requests within the applicable legal deadline. The waitlist is not permission for unrelated marketing or disclosure to other organizations for their own marketing.
Optional analytics and browser storage
Google Analytics 4 is optional. It loads only after you allow it or return in the same browser with a saved Allow choice. It measures page views, waitlist-button interactions and confirmed new registrations. A duplicate or failed request does not generate a new-registration conversion. Our event code does not send form details, email addresses, postal codes, trade, registration identifiers or campaign values to Google. It supplies query-free page URLs and an empty referrer. Google can nevertheless receive connection metadata, including an IP address, and uses analytics cookies and identifiers when enabled. Advertising signals and personalization are disabled in the configured integration.
The website stores your analytics choice in this browser’s local storage. If browser storage is blocked, your choice may last only for the visit. Rejecting analytics does not prevent registration. Withdrawing permission stops future measurement by this implementation and attempts to clear applicable Google Analytics cookies; it does not retract data already sent. Choices apply to the current browser. Reload other open BlueCaller tabs after changing your choice, and set your preference separately on other browsers or devices.
Analytics preferences
You can allow optional analytics or reject it, including withdrawing a previous Allow choice. Registration works without analytics.
Optional analytics: off.
Service providers, disclosures and storage
We use Cloudflare Pages and Functions to deliver the website and process submissions, Cloudflare Turnstile to check for bots, Supabase to store registrations and consent records, and Google Analytics when you permit optional analytics. Cloudflare may use security-related browser storage as part of its services. These providers process information to perform their services and may handle operational metadata under their own terms and privacy practices.
The configured waitlist database is in Supabase’s Canada Central region and is separate from BlueCaller’s application databases. A Canadian database location does not mean all processing stays in Canada: Cloudflare, Google and provider support or subprocessors may process information in other countries, including the United States, where local authorities may have lawful access. We remain responsible for information processed on our behalf under applicable law.
This implementation does not sell the waitlist, provide it to advertisers, or enable cross-context advertising integrations. Information may also be disclosed where required by law or reasonably necessary to protect legal rights or investigate misuse, subject to applicable law. We do not give public access to registration records.
Retention and deletion
We retain information only while needed for the purposes described here, consent administration, security and applicable legal obligations, and then delete it or make it no longer identifiable. Retention depends on the type of information, the purpose for keeping it and applicable legal requirements. This applies to waitlist records, consent and suppression evidence, correspondence, security logs, analytics and backups.
The current rate-limit window is ten minutes. Counter expiry stops an old attempt affecting that limit but does not itself erase the database row; operational cleanup is required. Removing a registration from the live database does not necessarily remove it immediately from provider backups. Backup deletion follows the provider’s retention cycle; deletion requests also need to be reflected if information is restored from a backup. Withdrawal may require keeping limited suppression evidence so a later duplicate does not restart unwanted updates.
Security
The service uses HTTPS, server-side validation, Turnstile verification, rate limits, database access restrictions and server-side credentials. Database rules prevent duplicate registrations from overwriting existing details or withdrawn consent. Application responses and analytics do not include submitted personal details, and application code does not log request bodies. Providers may maintain their own operational logs. No internet transmission or storage system is guaranteed secure; we do not promise absolute protection.
Access, correction, deletion and complaints
Email [email protected] to ask about the personal information we hold about you, request access or correction, withdraw consent, request deletion, or raise a complaint. We may need proportionate information to verify your identity and protect other people’s information. We will explain applicable limitations, such as legal retention requirements, and respond within the time required by applicable law.
Depending on your location and the law that applies, including Canada’s PIPEDA or applicable provincial privacy law, you may have rights of access, correction and challenge to our privacy practices. You may complain to the Office of the Privacy Commissioner of Canada or an applicable provincial authority. U.S. state privacy rights depend on residence and whether the law covers our activities; where applicable, they may include access, correction, deletion, portability, appeal and protections against discriminatory treatment for exercising rights. Contact us to exercise applicable rights or seek an explanation of a decision. We do not represent that every state privacy statute applies to this service.
Changes to this policy
Material changes to purposes or consent requirements will be explained before information is used in a way that requires fresh consent. Questions about this policy can be sent to [email protected].