Processing...
Processing...

Privacy Policy

This Privacy Policy explains what information TopicalDrift.com ("Topical Drift", "we", "us") collects, how we use it, and the choices you have.

Effective date: January 10, 2026 • Last updated: April 19, 2026
Quick summary
  • Passwordless login via MagicLinks (email-based).
  • We collect only what we need to run crawls and support the product.
  • Embeddings & UMAP data stored for analysis.
  • GSC access used only for requested analysis.
  • Topical Map Generator — AI pipeline data handled as described below.
  • Topical Map Editor — no data sent to our servers unless you save.
  • We don't sell your personal information.
  • You can request deletion of your data.

TopicalDrift.com

TopicalDrift.com provides three tools for SEO content architecture:

  • Topical Drift Analyzer — sitemap crawling, main-content extraction, 768-dimensional embeddings, UMAP semantic projection, k-means clustering, internal link context analysis, and GSC data integration (optional).
  • Topical Map Generator — seven-stage AI pipeline that produces a structured content map from a macro topic and seed keyword. Includes SERP analysis, entity extraction, topic classification, URL architecture generation, and internal linking plan.
  • Topical Map Editor — a free browser-based visual editor for loading, editing, and exporting topical and concept maps. No account required. Most functions run entirely in the browser.

"You" refers to the person or organization using our website and services.

Information we collect

A) Information you provide
  • Account/contact info: email address (for MagicLinks passwordless authentication), name (optional), and any message content you submit via contact forms.
  • Drift Analyzer inputs: sitemap URL(s), site URL(s), and configuration you provide for crawls.
  • Topical Map Generator inputs: macro topic, seed keyword, and optional site URL you provide when generating a map. These are sent to our AI pipeline to generate your map.
  • Topical Map Editor inputs: JSON files you load into the editor are processed entirely in your browser. They are not sent to our servers unless you use the Save function to save to your account.
  • Uploads (if offered): files you upload for analysis (e.g., internal link exports, GSC CSV exports).
  • Payment information (when paid plans launch): processed by third-party payment processors (we don't store full credit card numbers).
B) Information we collect automatically
  • Usage data: pages viewed, crawls initiated, maps generated, actions taken in the app, timestamps, and basic diagnostic events.
  • Device/log data: IP address, browser type, operating system, referring/exit pages, and approximate location derived from IP.
  • Cookies/local storage: used for essential site features (authentication session, theme preference) and optional analytics (see "Cookies & tracking" section).
  • Performance metrics: crawl duration, map generation time, error logs, API response times for service improvement.
C) Crawled website data (Drift Analyzer)
  • Page content: HTML fetched from your sitemap URLs (we extract main content, not full raw HTML)
  • Internal links: anchor text, surrounding text, container/heading context
  • Metadata: page titles, meta descriptions, canonical tags, status codes
  • Processed data: high-dimensional embeddings, UMAP 2D projections, cluster assignments, semantic distances
D) Topical Map Generator data
  • Pipeline inputs: macro topic and seed keyword you provide are sent through the seven-stage AI pipeline including SERP analysis and entity extraction.
  • SERP data: we fetch and analyze public search results as part of topic discovery. We do not store raw SERP HTML — only extracted topic candidates, entities, and PAA questions used to build your map.
  • Generated map data: the resulting nodes, edges, URLs, entities, aliases, and confidence scores are stored in your account so you can access, edit, and export them.
  • AI model calls: pipeline stages that use AI models (OpenAI or similar) send cleaned topic text — not your personal data or full site content — to those services. See "Third-party services" for details.
E) Google Search Console data (optional)

If you connect Google Search Console via OAuth 2.0, we may access GSC performance data such as:

  • Queries, clicks, impressions, CTR, and average position for your property
  • Page-level performance metrics
  • Date ranges you specify for analysis

We use GSC data only to produce the analyzes and reports you request. We do not access unrelated properties or use your GSC data for purposes beyond your requested crawls. You can revoke access at any time through your Google account settings.

Passwordless authentication via MagicLinks

We use MagicLinks for passwordless authentication:

  • When you sign in, we send a time-limited login link to your email address
  • Clicking the link authenticates your session
  • We do not store passwords — only your email address and authentication tokens
  • Authentication tokens expire after a set period (typically 30 days)
  • We use secure, encrypted cookies to maintain your logged-in session
Security benefit: Passwordless authentication eliminates password-related risks (weak passwords, reuse, breaches). You authenticate via your email provider's security.

Privacy considerations for Topical Map tools

Topical Map Generator
  • What we collect: macro topic, seed keyword, and optional site URL. We do not collect or store raw SERP HTML — only extracted topic candidates, entities, and structured pipeline outputs.
  • AI pipeline processing: topic text is sent to AI model APIs (e.g., OpenAI) to classify topics, generate entities, and build the map structure. We send cleaned topic strings — not personal data or full site content.
  • SERP data: we fetch publicly available search results as part of topic discovery. This data is used solely to build your map and is not stored in a form that can be attributed to you beyond the generated map output.
  • Map storage: generated maps (nodes, edges, URLs, entities, confidence scores) are stored in your account. You may delete them at any time by contacting us or using in-app controls.
  • Usage limits: we log map generation events (timestamp, account ID, macro/seed keyword) to enforce the 3 maps/month beta limit and prevent abuse.
Topical Map Editor
  • No account required. The Editor runs entirely in your browser. JSON files you load are not transmitted to our servers during editing.
  • No data collected during editing. Node edits, layout changes, and exports all happen locally in your browser session. We do not observe or collect the content of maps you edit unless you Save them to your account.
  • Save function: if you use the Save function, the map JSON is transmitted to and stored on our servers associated with your account. The same deletion rights apply as for generated maps.
  • Exports: PNG, SVG, CSV, and JSON exports are generated in your browser and downloaded directly. We do not receive copies of your exported files.
  • Usage analytics: we may log that the Editor was visited (page view) but do not log the content of maps you load or edit without an account.

How we use information

  • Provide the Drift Analyzer: run unlimited crawls (fair use), generate embeddings, compute UMAP projections, calculate semantic distances, detect drift/mismatch, build clusters, create interactive radial maps, identify linking opportunities, and produce reports/exports.
  • Provide the Topical Map Generator: process macro and seed keyword inputs through the seven-stage AI pipeline, run SERP analysis and entity extraction, generate structured map JSON, store maps in your account, and enforce the 3 maps/month beta limit.
  • Provide the Topical Map Editor: serve the browser-based editor application. Data processing during editing happens in your browser — we only process data you explicitly save to your account.
  • Authentication: send MagicLinks emails, maintain login sessions, manage account access.
  • Support: respond to requests, troubleshoot issues, provide implementation guidance, and improve reliability.
  • Improve the product: analyze aggregate usage patterns (not individual site content or map content) to improve UI, embedding accuracy, UMAP parameters, clustering quality, AI pipeline performance, and workflows.
  • Security: prevent abuse (including fair use policy enforcement), protect accounts, monitor for suspicious activity, and detect automated attacks.
  • Billing (when paid plans launch): process subscriptions, manage plan limits, handle upgrades/downgrades.
  • Communications: send service updates, feature announcements, beta pricing notifications, and (with consent) marketing emails.
What we DON'T do:
  • We do not sell your personal information
  • We do not use your website content or generated maps to train public models for other customers
  • We do not share your embeddings, semantic analysis, or map content with third parties (except service providers who need it to operate the service)
  • We do not use your GSC data for purposes beyond your requested analysis
  • We do not receive or store the content of maps you load in the Editor without an account

Embeddings & UMAP data storage

To provide analysis and track improvements over time (especially with unlimited crawls), we store:

  • Page embeddings: high-dimensional vectors representing semantic meaning (generated via sentence-transformers/all-MiniLM-L6-v2)
  • UMAP projections: 2D coordinates (x, y) for visualization
  • Semantic angles: Angular positions calculated from UMAP projections
  • Cluster assignments: K-means cluster IDs and centroids
  • Distance measurements: Actual (0-2.0) and normalized (0-1) semantic distances
  • Link context embeddings: Vectors for anchor + surrounding text + container context

What we don't store:

  • Full raw HTML of your pages (only extracted main content text)
  • Complete GSC query lists (only aggregate performance data)
  • Passwords (we use passwordless MagicLinks)

Third-party services we use

We share information with service providers who help us operate the service:

Service Purpose Data shared
Hosting provider Infrastructure, servers, databases All service data
MagicLinks Passwordless authentication Email address, authentication tokens
OpenAI API Drift Analyzer embeddings (when applicable) + Topical Map Generator pipeline (topic classification, entity extraction, map assembly) Cleaned page text (Analyzer) or cleaned topic strings (Generator) — not personal data or full HTML
Serp Provider(s) Topical Map Generator — SERP data for topic discovery and PAA question extraction Macro topic and seed keyword search queries — no personal data
Serilog / Log aggregator Error monitoring, logging Error logs, usage metrics, IP addresses
Email service Send MagicLinks, map completion notifications Email address, message content
Payment processor (future) Subscriptions, billing Payment details, billing address
Analytics (optional) Aggregate usage patterns Anonymized page views, events

Other sharing scenarios:

  • Legal: to comply with lawful requests, court orders, protect rights/safety, or prevent fraud/abuse.
  • Business changes: in connection with a merger, acquisition, or asset sale (we'll provide notice where required by law).
When we use vendors, we limit access to what they need to perform their services and expect them to protect your data consistent with this policy and applicable law.

Data retention periods

We keep data only as long as necessary for the purposes described above:

Data type Retention period
Account data Until account deletion + 30 days backup retention
Crawl results & reports Free/Starter: current crawl only
Professional: 6 months
Agency: Unlimited
Generated topical maps Stored until you delete them or delete your account. Maps are associated with your account and accessible across sessions.
Editor maps (saved to account) Stored until you delete them or delete your account. Maps edited without an account are not stored on our servers.
Embeddings & UMAP data Same as crawl results (enables historical tracking)
Raw HTML fetches Processed and deleted within 7 days (not permanently stored)
SERP data (Generator) Not stored in raw form — only extracted topic candidates and entities used to assemble the map are retained as part of the generated map.
Map generation logs Timestamp, account ID, and macro/seed keyword retained for 90 days to enforce usage limits and prevent abuse.
Logs (errors, access) 90 days for security/troubleshooting
Authentication tokens 30 days or until logout/revocation
Billing records 7 years (tax/legal requirements)
You can request deletion of your account and associated data (see "Your rights" section). Some data may be retained longer where required by law or legitimate business needs (e.g., fraud prevention).

International data transfers

Your information may be transferred to, stored, and processed in countries other than your own, including the United States.

  • We use service providers that operate globally (hosting, OpenAI API, etc.)
  • Where we transfer data from the EU/UK/EEA to other countries, we use appropriate safeguards such as Standard Contractual Clauses (SCCs) or adequacy decisions
  • By using the service, you consent to these transfers as necessary to provide the service

Cookies & tracking technologies

We use cookies and similar technologies:

Type Purpose Duration Required?
Authentication Maintain logged-in session (MagicLinks) 30 days ✅ Essential
Preferences Theme (light/dark), UI settings 1 year ✅ Essential
Security CSRF protection, abuse prevention Session ✅ Essential
Analytics Understand usage patterns (anonymized) 1 year ❌ Optional
Your choices: You can control cookies through your browser settings. Disabling essential cookies may affect functionality. For optional analytics cookies, we'll ask for consent where required by law.

Security practices

We use reasonable administrative, technical, and organizational measures designed to protect your data:

  • Encryption: HTTPS/TLS for data in transit; encryption at rest for sensitive data
  • Passwordless authentication: MagicLinks eliminate password-related vulnerabilities
  • Access controls: Least-privilege principles, role-based access
  • Monitoring: Automated alerts for abuse, suspicious activity, and anomalies
  • Regular updates: Security patches applied promptly
  • Data minimization: We don't store full HTML, passwords, or unnecessary data
Important: No method of transmission or storage is 100% secure. If you believe your account has been compromised, contact us immediately at our contact page.

Your privacy rights

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

  • Access: Request a copy of the personal information we hold about you
  • Correction: Update or correct inaccurate information
  • Deletion: Request deletion of your account and associated data (subject to legal/operational requirements)
  • Portability: Receive your data in a structured, machine-readable format (CSV/JSON exports)
  • Object: Object to processing based on legitimate interests
  • Restrict: Request restriction of processing in certain circumstances
  • Withdraw consent: Where we rely on consent (e.g., marketing emails, optional cookies), you can withdraw it at any time
  • Lodge a complaint: Contact your data protection authority (if in EU/UK/EEA)

Specific actions:

  • Revoke GSC access: Via your Google account permissions (google.com/permissions)
  • Export data: Use our CSV/JSON export features in the app
  • Delete account: Contact us with your request
  • Unsubscribe from emails: Click unsubscribe link in emails
To exercise your rights:
Use our contact page or email us. We'll respond within 30 days (or as required by law). We may request verification of your identity.

Children's privacy

Our services are not directed to children under 13 (or 16 in the EU, or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe we've inadvertently collected information from a child, please contact us immediately so we can delete it.

Changes to this policy

We may update this Privacy Policy from time to time. We will update the "Last updated" date above, and if changes are material we will provide additional notice (such as a banner, email, or in-app notification, where appropriate). Continued use of the service after changes take effect constitutes acceptance of the updated policy.

Contact us

For privacy questions, data requests, or security concerns, contact us here:

Contact We typically respond within 2-3 business days (privacy requests within 30 days).