Privacy Policy

1. Information we process

We process account names, email addresses, optional profile/contact details, password hashes, account/security settings, subscription and invoice records. We also process searched phone numbers, normalized courier metrics and timestamps, search/usage logs, IP addresses, browser information and sign-in events. Google sign-in, when enabled, supplies a verified email, name and identity identifier.

2. Why we use it

Information is used to provide courier checks, authenticate users, enforce quotas and access restrictions, maintain billing records, prevent abuse, investigate security events and send account/service notifications where mail delivery is configured. We do not sell personal lookup records. You must have an appropriate lawful basis for submitting a customer's number.

3. Couriers and service providers

A queried phone number is sent to configured courier services using the operator's authorized connection. Courier responses are normalized into the history metrics used by this application; courier address books are not stored as lookup results. Hosting, database/cache infrastructure, email providers and optional Google authentication process information needed for their respective functions. Those providers operate under their own policies.

4. Saved results and access

Successful results are saved in server-side cache/database snapshots and may be reused or refreshed, including during courier outages. Workspace data is scoped to that tenant. Authorized platform administrators can manage tenants, investigate abuse and access operational records needed to administer the service. API keys provide authorized integration access and should be kept on your server.

5. Cookies and browser storage

Session cookies keep you signed in; Remember me extends the sign-in period when selected. A temporary cookie protects Google OAuth state. Browser storage remembers your language choice. These are used for the application's operation and preferences. Clearing them may sign you out or reset preferences.

6. Security and retention

Passwords are hashed, session/API tokens are stored as hashes, and configured secrets and queued email content are encrypted server-side. Access controls, HTTPS and backups reduce risk but do not guarantee absolute security. Records are retained for service, billing, audit and security needs; no universal automatic deletion period is currently configured. Protected backups may retain earlier records until their retention is reviewed by the operator.

7. Your requests and policy changes

Contact the operator to request access, correction or deletion of account-related information, report misuse, or ask about retained records. Identity and authority may need verification; billing, security and legal obligations may affect what can be deleted. Do not send passwords, API secrets or unnecessary customer information in a support request. This policy may be updated; check its effective date.

Contact

CourierGuard

Contact the platform administrator who manages your subscription.