Privacy Policy
For certimonitor.com and the CertiMonitor application
Last updated October 5, 2026
This Privacy Policy explains how Jaime Guerrero, doing business as CertiMonitor ("CertiMonitor," "we," "us," or "our"), collects, uses, discloses, and protects personal information when you visit certimonitor.com, use the public /check tool, create or use an account through email or an available Google or GitHub sign-in option, join an organization workspace, request a paid-plan launch notification, subscribe to an available plan, contact us, or otherwise use the Service.
CertiMonitor is designed for users aged 18 and older. We do not sell personal information or use personal information for third-party targeted advertising.
1. Our Role
For account administration, authentication, public checks, requested launch notifications, billing, security, support, service analytics, and our own operational purposes, CertiMonitor generally determines why and how personal information is processed and acts as a controller or business, depending on the applicable law.
For some information that a business customer directs us to process through an organization workspace, member invitation, alert destination, or similar feature, CertiMonitor may act as a processor or service provider on behalf of that business customer. Where required, those processor activities should be governed by separate data-processing terms.
2. Personal Information We Collect
| Category | Examples | Primary Purpose |
|---|---|---|
| Account and authentication | Name, email address, password stored as a hash, optional two-factor authentication secret stored encrypted, passkey public keys. | Create and secure your account; authenticate access; recover accounts. |
| Google or GitHub sign-in | Name, email address, profile image URL, provider account ID, and access tokens together with refresh or ID tokens where issued and retained by the selected integration; expiry information. Stored authentication tokens are encrypted at rest. | Identify, link, and authenticate your account. Tokens are used only for authentication. |
| Organization information | Organization name, members, roles, invitations, and workspace settings. | Operate shared workspaces and permissions. |
| Monitoring and public network data | Domains and ports you add, check results, certificate details served by hosts, DNS records, registration or RDAP information, public certificates you upload, tags, alert rules, and alert history. | Provide TLS, domain, certificate, and DNS monitoring. |
| Public domain checker | Domain submitted to /check. The checker also processes your IP address for rate limiting. Separate hosting and request logs are described below. | Perform the individual check and enforce request limits without requiring an account. |
| Alert destinations | Email addresses and Slack, Discord, Microsoft Teams, or custom webhook URLs. Alert destinations are stored encrypted where stated in the Service. | Deliver alerts to destinations you select. |
| API information | API key prefix and a hash of the API key. | Authenticate API requests. The full API key is not retained in readable form after creation. |
| Billing information | Plan, subscription status and dates, Stripe customer identifier, and related billing metadata. Full payment-card details are submitted directly to Stripe and are not stored on CertiMonitor servers. | Administer subscriptions, payments, and billing support. |
| Technical and security data | IP address, browser user agent, request paths, request logs, error logs, user and organization identifiers, and security events. | Secure the Service, prevent abuse, diagnose problems, and maintain reliability. |
| Usage analytics | Aggregate page views and service usage information from cookieless analytics. | Understand use of the website and improve the Service. |
| Support and communications | Messages you send to support, privacy, or security addresses and related contact information. | Respond to requests, provide support, and maintain records of communications. |
| Optional launch notification | Email address you provide for the request and records of the request, delivery, and any withdrawal or opt-out. | Send the single paid-plan launch announcement you requested and manage that preference. |
We do not ask for private keys. Uploads containing private keys are rejected by the Service. Please do not submit passwords, private keys, or other secrets through fields that are not designed to receive them.
Optional information and access. Provider sign-in and the launch-notification request are optional. A public check does not require an account, and requesting a launch email does not create one. Account-based features need sufficient account information to authenticate you. Declining an optional launch email does not affect your access to the Service.
3. Sources of Information
- You, when you create an account, submit a public check, request a launch notification, subscribe, configure monitoring, invite members, create API keys, select alert destinations, or contact us.
- Google or GitHub, when you choose that provider to sign in, through the permissions you authorize. Our current Google request uses openid, email, and profile; our current GitHub request uses read:user and user:email. We retain the information listed above rather than every field those permissions could make accessible.
- Your organization owner or administrator, when they invite you, assign a role, or manage an organization workspace.
- Public network and registration sources, including TLS connections, DNS, certificate information, and registration or RDAP services for domains and hosts you ask us to check or monitor.
- Service providers, including Stripe for payment and subscription status and infrastructure providers for security, delivery, and operational logs.
- Automatically from your browser or device when you use the Service, such as IP address, user agent, request information, and essential session information.
4. How We Use Personal Information
- provide, operate, maintain, and support the Service;
- authenticate users and secure accounts, organizations, APIs, and infrastructure;
- run public or account-based checks and deliver monitoring alerts to destinations you configure;
- process subscriptions, billing, upgrades, downgrades, cancellations, and payment-related communications;
- send service messages such as verification, password-reset, invitation, billing, security, and operational emails;
- send a single paid-plan launch announcement where you specifically request it, and manage your request or withdrawal separately from service messages;
- diagnose errors, investigate abuse, prevent fraud, and protect users and third parties;
- understand aggregate usage and improve the Service;
- respond to support, privacy, and security requests;
- comply with legal obligations and enforce our agreements; and
- establish, exercise, or defend legal claims where necessary.
For processing subject to the EU GDPR or UK GDPR, we rely on performance of a contract where necessary to provide requested account, authentication, public-check, or subscription services to you; legitimate interests for administering organization-user access, security, rate limiting, diagnostics, and proportionate service improvement; legal obligations for required records and disclosures; and consent for the optional launch-notification request and other activities where consent is required. Our legitimate interests are operating a reliable service, preventing misuse, and protecting users and others, balanced against their rights. Withdrawing consent does not affect processing that was lawful before withdrawal.
Provider sign-in and account linking. Google or GitHub authenticates you and supplies the permitted profile and authentication information. CertiMonitor does not receive your Google or GitHub password. We use provider information to identify and authenticate your account; we do not use authentication tokens to read your email inbox, obtain private repository content, post on your behalf, advertise to you, or add you to a launch list. The integration does not request Gmail, Drive, contacts, or private-repository access.
When the provider email matches an existing CertiMonitor account, the sign-in may be linked automatically to that account. To protect account access, linking can involve additional verification, invalidation of sessions, or removal of an earlier password associated with an unverified account. Contact support@certimonitor.com about an unexpected link or difficulty accessing an account.
Public checks. The /check tool records the domain you submit and uses your IP address for rate limiting within that feature. A check does not add you to an account, continuing monitoring, or an email list. Hosting and operational providers may separately process request and error information, including IP addresses, as described in Sections 2 and 5. An account is not required, but personal information may still be processed when you use the checker. Publicly accessible network or registration information may itself identify individuals.
Optional launch email. Where a launch-notification form is offered, we use the email address you voluntarily submit to send one announcement when paid plans launch. Account registration or Google/GitHub authorization alone is not a request for that announcement or a continuing newsletter. You may withdraw before the announcement by contacting privacy@certimonitor.com, and the message will include an unsubscribe option. Declining or withdrawing does not stop account, security, billing, or other necessary service messages. Any broader marketing subscription would need a separate, clearly explained choice.
5. Service Providers and Recipients
| Provider / Recipient | Function | Information Involved |
|---|---|---|
| Google and GitHub | Optional identity and authentication providers | Provide the selected sign-in profile, provider ID, and authentication tokens; process sign-in requests and related technical information under their own privacy practices. |
| Stripe | Payments and invoices | Account or organization billing identifiers, owner email, subscription information, and payment details submitted directly to Stripe. |
| Vercel | Website and application hosting; cookieless web analytics | Requests to the hosted service, including IP address and user agent, request logs, and aggregate analytics. |
| Neon | Database hosting; current deployment identified as US East, Ohio | Stored account, organization, monitoring, configuration, and related application data. |
| Resend | Transactional email delivery | Recipient email addresses and the content of verification, password-reset, invitation, billing, and alert emails. |
| Email delivery services for requested launch notices | Deliver the optional single launch announcement and manage delivery or opt-out requests | The requested email address, message content, and request, delivery, or suppression information needed for that limited mailing. |
| Better Stack | Logging, uptime, and error monitoring | Application logs such as request paths, IP address, user agent, and user or organization identifiers. Passwords and alert destination URLs are not intentionally included in these logs under the current configuration. |
| Upstash | Scheduling or triggering monitoring jobs | Under the current configuration, the scheduling function receives the trigger rather than customer account or monitoring content. |
| IONOS | DNS and company email services | Technical DNS information and contact, support, privacy, or security communications processed through company email, as applicable. |
| User-selected destinations | Slack, Discord, Microsoft Teams, email providers, and custom webhook endpoints | Alert content and destination information that you instruct CertiMonitor to send to the selected destination. |
Google and GitHub also process information independently for their own identity-service purposes. Their separate policies explain that processing. Our use of the information we receive remains subject to this Policy.
Provider privacy information: Google Privacy Policy and GitHub General Privacy Statement.
We may replace or add service providers as the Service evolves. We will update this Policy when a change materially affects the categories of personal information or purposes described here.
6. Cookies and Similar Technologies
CertiMonitor uses a session cookie or equivalent storage that is necessary to keep you signed in and maintain authenticated use of the Service. Vercel Web Analytics is currently configured to provide aggregate analytics without cookies. Stripe may use its own cookies or similar technologies on payment interfaces for payment processing and fraud prevention.
If you choose Google or GitHub sign-in, your browser connects to that provider. Authentication may use cookies or similar storage to complete the sign-in and protect the session; the provider may also process information under its own policy. Provider authorization is separate from any consent required for optional tracking technologies.
CertiMonitor does not deploy advertising cookies or third-party behavioral advertising trackers for its own advertising. If we introduce non-essential tracking technologies, we will explain them and implement any consent mechanism required by applicable law before using them where consent is required.
7. When We Disclose Personal Information
We disclose personal information only as reasonably necessary for the purposes described in this Policy, including:
- to the service providers and recipient categories described above for the stated functions;
- to sign-in providers, alert destinations, and integrations that you or your organization choose;
- to organization owners and authorized administrators for workspace administration;
- to courts, regulators, law enforcement, or other parties when disclosure is required by law or reasonably necessary to protect legal rights, safety, or the security of the Service;
- to professional advisers where reasonably necessary and subject to appropriate duties of confidentiality; and
- in connection with a merger, financing, reorganization, sale of assets, or transfer of the CertiMonitor business, subject to applicable law, relevant provider restrictions, and appropriate notice and consent where required.
CertiMonitor does not sell personal information for money and does not share personal information for cross-context behavioral advertising as those terms are defined by the California Consumer Privacy Act. We do not use personal information for third-party advertising.
If an LLC or other successor takes over CertiMonitor, we will identify the new operator and effective date, update this Policy, and notify affected account holders as appropriate. A business transfer does not itself authorize new purposes for personal information or enroll anyone in marketing. Existing privacy choices and applicable obligations remain relevant to the transfer.
8. Data Retention and Deletion
Account and monitoring data are generally retained while the relevant account or organization remains active and until you delete the data or account, subject to the exceptions below.
Provider identity and token records. Linked profile information and provider identifiers are retained while needed for the chosen sign-in or account. Tokens are retained only while needed for authentication, taking account of expiry, replacement, known revocation, disconnection, and account deletion. Expiry of a token and deletion of a stored record are different events. Unneeded tokens and provider links are removed from active systems, subject to limited legal or security records and temporary recovery copies described below.
Public-check records. Retention of submitted domains is limited to the period needed for the requested checker function. Rate-limiting information is kept only while needed to apply the relevant request limits. Separate operational logs and any records needed to investigate an identified security incident follow the applicable log or security retention criteria below. Closing your browser does not automatically delete provider logs.
Launch-list records. We retain the active launch-notification entry until the announcement has been sent, you withdraw, or the planned announcement is abandoned, followed by the limited time needed to complete delivery or resolve a request. We may keep a minimal record of your request or opt-out to demonstrate permission, prevent unwanted mail, or comply with law. That record is not a continuing marketing list. An indefinitely delayed launch is not a reason to keep an active list without review.
When a downgrade takes effect, domains, certificates, and related history above the new plan limit are deleted if you affirmatively selected which items to keep and confirmed the downgrade. If a plan ends because payment could not be collected and no selection was made, excess items may be paused instead of immediately deleted so that you can decide how to proceed.
Application logs stored with the current logging provider are retained for approximately 90 days and then deleted under the current configuration. Billing and transaction records may be retained for the period required by tax, accounting, payment, anti-fraud, or other legal obligations.
Agreement and preference records may be retained for the applicable legal recordkeeping or claims period after an account closes. These limited records need not include readable authentication tokens or unnecessary profile information. Where a fixed period is not stated, necessity is assessed by the relevant function, unresolved security or support issues, applicable legal duties, and the availability of less identifying records.
When you delete an account, CertiMonitor deletes associated data from active application systems, subject to limited records we must retain for legal, security, fraud-prevention, dispute, tax, accounting, or payment purposes and any temporary residual copies that may remain in provider backups or technical recovery systems. Backup and provider-specific retention periods may differ from active-system retention.
9. Security
CertiMonitor uses administrative and technical measures designed to protect information appropriate to the nature of the Service. Data is encrypted in transit using HTTPS; stored authentication-provider tokens, alert destinations, and two-factor secrets are encrypted at rest; passwords and API keys are stored as hashes. Accounts may use two-factor authentication and passkeys, and organizations may require them.
No internet service can guarantee absolute security. You are responsible for protecting your credentials, configuring appropriate organization permissions, and promptly reporting suspected compromise to security@certimonitor.com.
10. International Processing and Transfers
CertiMonitor is operated from the United States. Current core service-provider configurations and data regions are described above where known. The specific location of processing may also depend on the provider and on any third-party alert destination you select. If you use the Service from another country, personal information may be processed in the United States or another location involved in providing the selected service or destination, where data-protection laws may differ from those in your location.
Where EU GDPR or UK GDPR transfer restrictions apply to a transfer between organizations, CertiMonitor will use an applicable lawful transfer mechanism where required, which may include the European Commission's Standard Contractual Clauses and, for United Kingdom transfers, the UK International Data Transfer Agreement or UK Addendum, as appropriate. The specific mechanism may be addressed in a Data Processing Agreement with a business customer.
You may contact privacy@certimonitor.com for information about the safeguards applicable to a covered transfer and how to obtain a copy, subject to appropriate protection of confidential information. Selecting an external sign-in provider or alert destination may also involve processing under that provider's own arrangements.
11. Your Privacy Choices and Rights
You can access and update certain account and organization information in the Service and request account deletion through the app. You may also contact privacy@certimonitor.com to request access, correction, deletion, or a copy of personal information we hold about you, including public-check or launch-list information where you have no account. Please provide enough information to locate the relevant record; do not email passwords, private keys, or authentication tokens.
Depending on applicable law and your location, you may also have rights to object to or restrict certain processing, request portability, withdraw consent where processing is based on consent, opt out of certain disclosures, or appeal a privacy-request decision. We may need to verify your identity before completing a request. We will respond within the period required by applicable law and may deny or limit a request where an applicable exception permits us to do so.
Provider choices. You can revoke CertiMonitor's authorization through the controls offered by Google or GitHub. Contact support if you need help disconnecting a provider or arranging another supported sign-in method. Revocation does not by itself cancel a CertiMonitor subscription, delete your account, or erase information already received; those requests are handled separately under this Policy and the Cancellation and Refund Policy.
You may withdraw the optional launch-email request or object to use of your personal information for direct marketing at any time through the unsubscribe option or privacy@certimonitor.com. We will stop that marketing use. Where an applicable law requires recognition of a valid browser opt-out preference signal, we will honor that requirement; our current practice does not involve selling data or sharing it for cross-context behavioral advertising.
12. United States State Privacy Rights
Some U.S. state privacy laws apply only when a business meets statutory revenue, volume, sale, sharing, or other thresholds. If a state privacy law applies to CertiMonitor and gives you specific rights, we will honor those rights as required. We may also choose to honor comparable requests voluntarily even when a particular threshold is not met.
If the California Consumer Privacy Act applies to CertiMonitor, California residents may have rights to know, access, correct, and delete personal information and to opt out of certain sales or sharing. CertiMonitor does not currently sell personal information or share it for cross-context behavioral advertising. We do not discriminate against users for exercising privacy rights protected by applicable law.
13. European Economic Area and United Kingdom
If the EU GDPR or UK GDPR applies to our processing, you may have rights to access, rectify, erase, restrict, or port personal data, object to processing based on legitimate interests, withdraw consent where consent is the legal basis, and lodge a complaint with a competent data-protection authority. These rights are subject to applicable conditions and exceptions.
A business customer that controls personal data processed through CertiMonitor may be responsible for responding to requests relating to data that CertiMonitor processes solely on that customer's behalf. In that situation, we may direct your request to the relevant customer or assist the customer under applicable data-processing terms.
Where applicable law requires CertiMonitor to appoint a representative in the EEA or United Kingdom, representative contact information will be added to this Policy after the representative is appointed and before the arrangement is relied upon for covered processing.
14. Children
CertiMonitor is not intended for anyone under 18, and we do not knowingly offer accounts to children. If you believe a person under 18 has provided personal information through the Service, contact privacy@certimonitor.com.
15. Third-Party Destinations and Links
When you choose Google or GitHub sign-in, direct an alert to a third-party destination, or follow an external link, the third party processes relevant information under its own terms and privacy practices. These providers and destinations operate independently. Their independent processing does not limit CertiMonitor's obligations for the information we receive and process.
16. Changes to This Privacy Policy
We may update this Policy as the Service, vendors, legal requirements, or data practices change. We will post the updated Policy and revise the date above. If a change is material, we will provide additional notice where required by law, such as by email or an in-product notice.
17. Contact
Privacy: privacy@certimonitor.com | Security: security@certimonitor.com | Support: support@certimonitor.com
Jaime Guerrero, doing business as CertiMonitor
59 Cooper St, New York, NY 10034