Privacy Policy

    Effective Date: November 17, 2025

    Last Updated: October 15, 2026

    Disclaimer: This policy is comprehensive and based on standard requirements (GDPR, CCPA, PIPEDA). However, you should have a legal professional review this before going live to ensure it matches your specific liability insurance and local laws.

    Welcome to cite-met ("Company," "we," "our," or "us"). We are committed to protecting your personal information and your right to privacy. This Privacy Policy explains what information we collect, how we use it, and what rights you have in relation to it.

    This policy applies to all information collected through our website (https://cite-met.com), our hosting services, our analytics dashboard, Cite-Met Pulse, and any related services, sales, marketing, or events (collectively, the "Services").

    By using our Services, you agree to the collection and use of information in accordance with this policy.


    1. Information We Collect

    We collect personal information that you voluntarily provide to us, information automatically collected when you use the Services, and information accessed via third-party integrations (such as GitHub).

    A. Personal Information You Provide

    • Account Data: When you register, we collect your name, email address, and authentication credentials.
    • Billing Data: If you purchase a paid plan (Local, Growth, Authority, or Add-on Services), our third-party payment processor (Stripe) collects your payment method details and billing address. We do not store your full credit card information on our servers.
    • Communication Data: Information you provide when you contact support or request an audit.
    • Scan Data: When you scan a website, we store the URL you scanned and the results of the scan. If you give us your email address to get a report, we store it with the scan it came from.

    B. Information from Third Parties (GitHub)

    Our Service relies on integration with GitHub to access your source code for deployment. When you link your GitHub account, we collect:

    • Profile Information: Your GitHub username, avatar, and email address.
    • Repository Access: We access only the repositories you explicitly grant us permission to see. We use this access to clone your code, run your build, and deploy your website.
    • Commit Data: We log commit messages and timestamps to record each deployment and update your dashboard status.

    C. Information Automatically Collected (Usage Data)

    When you visit cite-met.com or use our dashboard:

    • Log Data: IP address, browser type, operating system, referring URLs, device information, and timestamps.
    • Cookies: We use cookies to maintain your session and user preferences.

    D. Data We Process on Your Behalf (Analytics)

    This is distinct from your account data. When you host a website on cite-met, we act as a Data Processor for the traffic visiting your website. We collect the following on your behalf to generate your AEO & SEO Analytics Dashboard:

    • Visitor IP Addresses: Used for geographic breakdown (Country/Region) and abuse prevention.
    • User Agents: Used to identify device types (Mobile/Desktop) and specific AI Bots (e.g., ChatGPT-User, Googlebot).
    • Request Paths: Which pages on your site were visited.
    • Referrers: Where your traffic came from (e.g., Direct, Realtor.ca, Google).

    E. Cookieless Engagement & Navigation Analytics

    For sites we host, and for external sites that add our monitoring snippet, we also measure engagement (time on page) and navigation journeys (the ordered paths visitors take through a site) without using cookies or any browser storage. Because nothing is written to the visitor's device, no consent banner is required for this measurement. The following notice applies to visitors of those sites:

    Our cookieless site analytics measure page views, time on page, and navigation paths. To tell visits apart within a single day, we derive a temporary, non-reversible identifier from your IP address and browser, combined with a secret that rotates every 24 hours. We do not store your IP address, and because the secret changes every day, this identifier cannot link your visits across days. This processing is carried out on the basis of legitimate interest and involves no cross-site tracking.

    This notice covers only the cookieless analytics. It does not describe Cite-Met Pulse, which works differently and can recognise a returning visitor across days. Pulse is described in Section 1.F.

    F. Cite-Met Pulse (Visitor Intelligence and Lead Capture)

    Cite-Met Pulse is separate from the cookieless analytics in Section 1.E, and it works differently. Pulse is a script, loaded from platform.cite-met.com/pulse, that runs on the websites of customers whose plan includes it. We also run it on cite-met.com, so it applies to you when you visit this site. Pulse can recognise a returning browser across days, and it can link a visit to a company or, once you give us your details, to you.

    On a customer's website, we handle this data on the customer's behalf (see Section 1.D). The customer decides how to use it. This section describes what Pulse itself does.

    What Pulse collects when it is switched on

    • Pages and clicks: The pages you view (the address path, including anything after a "?", and the page title), where you came from (the referring page and any campaign tags in the link, such as utm_source), how long you are actively on a page, and what you click (the kind of element, the first 60 characters of its label or text, and the link address if it is a link). Pulse does not collect what you type into form fields while you browse.
    • Visit history: When you first and last visited, how many times you have come back, and the order of pages in each visit.
    • Approximate location: Your country, region, and city, worked out from your IP address by Cloudflare.
    • Your company, when you appear to be on a business network: Pulse takes the name of the organization that owns your network connection, as reported by Cloudflare, and skips names that look like internet providers, mobile carriers, and hosting, cloud, or VPN services. We do not use a separate IP lookup service for this. The result is a best guess about a network, not a fact about you. It can be wrong or missing, and visitors on home or mobile connections usually can't be matched.
    • Your IP address and browser details: Pulse does not save your IP address or browser details with your page views, visits, or company match. They are used while your request is handled, to work out location and network, to limit abuse, and to check bot-protection challenges, and the browser details are used only to flag likely bots. If you submit a form, we do save your IP address and browser details with that submission (see below).
    • Activity in the Pulse panel: What you open or click in the Pulse panel, such as an offer, and the privacy choices you make there.
    • Offers: A site owner can set up prompts that appear based on the pages you have viewed and whether you have visited before. To find a matching prompt, Pulse sends the pages you have viewed in this visit and a Pulse ID to our servers.

    Forms and meeting bookings

    If you fill in a form or book a meeting through Pulse, we collect what you enter (such as your name, email address, message, and any other fields the form asks for) and the pages you viewed before you sent it. For a form, we also save your IP address, browser details, and country with the submission. For a booking, we also save the time and time zone you chose.

    When you give us your email address this way, Pulse links the earlier and later visits from that browser to your name and email, so the site owner sees them together. The site owner is notified by email. For a form, that email includes your country and IP address. A booking is added to the site owner's calendar if they have connected one, and you receive a confirmation email.

    What Pulse stores in your browser

    Pulse does not use cookies. It uses your browser's local storage for three things:

    • A random ID that lets Pulse recognise your browser on later visits. It is created only if Personalization is on, it is not built from your device or browser characteristics, and it stays until you clear your site data.
    • Your privacy choice, kept for up to 12 months, after which Pulse asks again.
    • Small settings, such as whether you minimized the Pulse panel or dismissed an offer.

    Your choices

    • In the EU, EEA, and UK, Pulse records nothing about your visit until you make a choice. If you decline Analytics, Pulse does not record your page views, clicks, or time on the page, but it can still show you offers and record whether one was shown, clicked, or dismissed, using a temporary ID that is not saved in your browser. Elsewhere, Pulse starts on and shows a notice. In both cases you can change your mind at any time through "Manage preferences" in the Pulse panel or the "Privacy & data" link at the bottom of it.
    • How we decide which applies: We use the country that Cloudflare detects for your connection. If no country is detected, the EU, EEA, and UK behavior does not apply to you, and Pulse starts on with a notice.
    • Analytics: If you turn this off, Pulse stops recording your page views, clicks, and time on the site.
    • Personalization: If you turn this off, Pulse stops using its saved random ID, so it can't recognise you on later visits. The ID stays in your browser until you clear your site data.
    • Site owners choose whether the privacy panel appears. We switch it on by default, and it is on for cite-met.com. If a site owner turns it off, Pulse runs without asking you, and your options on that site are to block the script or to contact us or the site owner.
    • Blocking Pulse: You can block scripts from platform.cite-met.com/pulse in your browser or with a content blocker. Until you block it, each page that embeds Pulse asks our servers for the script.
    • Do Not Track and Global Privacy Control: Pulse does not currently act on these browser signals. Use the choices above instead.

    Where Pulse data is stored and who else handles it

    Pulse data is stored in a database that we run on Cloudflare. Each customer can see only the Pulse data collected on their own sites. Cloudflare also provides the bot-protection challenge (Cloudflare Turnstile, which receives your IP address) on Pulse forms and bookings, and sends the notification and confirmation emails. If a site owner has connected Google Calendar, your name and email address go to that calendar when you book a meeting.

    How long we keep Pulse data

    Pulse does not yet delete visit records automatically after a set time. We keep them until they are deleted, which we do when you ask us to (see below) or when the customer asks.

    Seeing or deleting your Pulse data

    Email privacy@cite-met.com and tell us which website you visited. Because we do not keep IP addresses with visit records, we can't look you up by IP address. To find your records we need something that links them to you: the email address you used on a form or booking, or the Pulse ID in your browser's local storage (the item named __sc_anchor). If Pulse runs on a customer's site, we may pass your request to that customer, because we hold the data on their behalf.


    2. How We Use Your Information

    We use the information we collect for the following business purposes:

    1. To Provide the Service:
      • To authenticate your identity via GitHub.
      • To clone, build, and host your website.
      • To add our measurement scripts to the HTML your build outputs, and to serve a default robots.txt and any robots.txt or llms.txt set for your site in our dashboard.
      • To manage custom domains and SSL certificates.
    2. To Provide Analytics:
      • To process your website's traffic logs and visualize human vs. AI bot traffic in your dashboard.
    3. To Provide Cite-Met Pulse:
      • To show a customer which pages visitors view and how they move through the site, to match visits to companies and, where someone gives their details, to people, to show offers, and to deliver forms and meeting bookings (see Section 1.F).
    4. To Improve Our Technology:
      • We analyze how AI crawlers interact with the sites we host to refine our AEO (Answer Engine Optimization) algorithms.
    5. To Communicate with You:
      • To send deployment status emails (Success/Failure).
      • To send billing receipts and feature updates.
    6. To Enforce Security:
      • To detect and prevent fraud, abuse, or security incidents (e.g., DDoS attacks).

    3. How We Share Your Information

    We do not sell your personal information. We only share information with the following third parties for specific business purposes:

    • Cloudflare (hosting and database): Cloudflare hosts the site and delivers it through its network (CDN, DDoS protection, and edge computing). It also runs the database where we store scan results and any email address you give us, applies rate limiting to the scanner, and controls access to our staff-only admin pages (Cloudflare Zero Trust). Your website content and traffic logs pass through Cloudflare's network.
    • Cite-Met Pulse: Pulse also relies on Cloudflare for bot-protection challenges (Cloudflare Turnstile) on forms and bookings and for sending notification and confirmation emails. If a site owner has connected Google Calendar for bookings, Google receives the booker's name and email address for the calendar event. The customer whose site Pulse runs on can see the Pulse data collected there. See Section 1.F.
    • Resend (email): When you ask for a scan report by email, Resend sends it. It receives your email address and the report for that purpose only.
    • Payment Processors: We use Stripe to handle all billing and payments.
    • Analytics Services: We may use internal or third-party tools to monitor the performance of the cite-met.com platform itself.
    • Legal Requirements: We may disclose your information where we are legally required to do so in order to comply with applicable law, governmental requests, a judicial proceeding, court order, or legal process.

    4. International Data Transfers

    Headquarters: cite-met is headquartered in Canada.
    Infrastructure: Our infrastructure is distributed globally via Cloudflare.

    If you are accessing our Services from outside Canada, please be aware that your information may be transferred to, stored, and processed by us in our facilities and by those third parties with whom we share your personal information, in Canada, the United States, and other countries.

    For users in the European Economic Area (EEA) or United Kingdom (UK): We ensure that any international transfers of data comply with the GDPR, utilizing Standard Contractual Clauses (SCCs) or ensuring adequacy decisions are in place.


    5. Data Retention

    • Account Data: We retain your account information as long as your account is active.
    • Source Code: We do not permanently store your source code. We pull it from GitHub to build it, cache the build artifacts (the output of your build) for hosting, and retain the artifacts until the next deployment replaces them or you delete the project.
    • Cite-Met Pulse Records: Pulse does not yet delete visit records automatically after a set time. We keep them until they are deleted at your request or the customer's. See Section 1.F.
    • Analytics Logs: Detailed raw traffic logs for your hosted websites are retained for a limited period (e.g., 30-90 days) to generate reports, after which they are aggregated or deleted.

    6. Security of Your Information

    We use administrative, technical, and physical security measures to help protect your personal information.

    • Encryption: All data in transit is encrypted via TLS/SSL.
    • Access Control: Access to source code and build environments is strictly limited to automated processes and authorized engineering staff for debugging purposes only.
    • GitHub Tokens: We do not store your GitHub password. We use OAuth tokens which can be revoked by you at any time via your GitHub settings.

    However, please remember that no electronic transmission over the internet or information storage technology is 100% secure, so we cannot promise or guarantee that hackers, cybercriminals, or other unauthorized third parties will not be able to defeat our security and improperly collect, access, steal, or modify your information.


    7. Your Privacy Rights

    Depending on your location, you may have the following rights:

    • Access: Request a copy of the personal data we hold about you.
    • Rectification: Request that we correct inaccurate data.
    • Deletion: Request that we delete your account and all associated data (including hosted projects and analytics history).
    • Revocation of Consent: You can revoke our access to your GitHub repositories at any time by uninstalling the cite-met App in your GitHub settings.

    To exercise these rights, please contact us at privacy@cite-met.com. For data collected by Cite-Met Pulse, include the details described in Section 1.F so we can find your records.


    8. A Note for Builders & Developers

    Since cite-met builds your site from your repository and serves the result, adding its measurement scripts and the robots.txt and llms.txt files described above, please note:

    • Intellectual Property: You retain full ownership of your code and content. cite-met claims no intellectual property rights over the material you provide to the Service.
    • Injected Files: The llms.txt and robots.txt files we generate are owned by you upon generation.

    9. Cookies and Tracking Technologies

    We use cookies to authenticate your session.

    • Essential Cookies: Necessary for the website to function (e.g., logging in).
    • Analytics Cookies: Used to understand how you interact with our dashboard.

    You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use the login features of our Service.

    Visitor analytics on the sites we host is cookieless. The engagement and navigation-journey measurement described in Section 1.E uses no cookies and writes nothing to a visitor's device. See Section 1.E for details.

    Cite-Met Pulse does not use cookies, but it does store a few items in your browser's local storage. These include a random ID that lets it recognise your browser on later visits, and your privacy choice. See Section 1.F for what they are and how to turn them off.


    10. Updates to This Policy

    We may update this privacy policy from time to time. The updated version will be indicated by an updated "Revised" date and the updated version will be effective as soon as it is accessible. We encourage you to review this privacy policy frequently to be informed of how we are protecting your information.


    11. Contact Us

    If you have questions or comments about this policy, you may email us at privacy@cite-met.com.

    Ranking isn't enough. Get cited.

    Scan your site now. Talk to us when you want it fixed for you.

    Talk to us

    Free scan. No signup.