Privacy Policy
RankSpires Privacy Policy
This Privacy Policy explains how RankSpires collects, uses, discloses, retains, transfers, and safeguards information when you visit rankspires.com, sign in with Google, submit a product-page URL, request a Product Conversion Audit, work with Product Truth or Campaign, purchase access, or contact support.
Effective date: August 1, 2026 · Version: 2026-08-01-v2
A requested audit may process the public URL, metadata, visible content, bounded HTML, and a short-lived screenshot.
Derived Product Truth, evidence, audit results, proposed copy, Campaign drafts, and account history may be saved to your workspace.
RankSpires does not continuously monitor the submitted page and does not publish or modify the merchant site.
1. Organization and privacy contact
RankSpires is a software service operated from Québec, Canada. RankSpires is responsible for the personal information it controls under this policy.
RankSpires Privacy Team
Email: support@rankspires.com
Use this contact for access, correction, deletion, portability, consent withdrawal, objection, privacy questions, or complaints.
2. Information we collect
We collect the information reasonably necessary to operate the requested workflow, authenticate users, maintain workspaces, process payments, provide support, secure the platform, and improve reliability.
| Category | Examples | Primary purposes |
|---|---|---|
| Account and identity | Name, email, Google account identifier, login method, account ID, session state, acceptance version | Authentication, account continuity, versioned legal acceptance, security, support |
| Submitted product and URL data | Public product-page URL, product title, description, category, merchant corrections, confirmations, brief content | Start the audit, establish Product Truth, prepare requested outputs |
| Captured page material | Requested and final URL, page metadata, visible page text, bounded HTML snapshot, screenshot, viewport measurements, visual anchors, capture timestamps | Observe the requested page, ground audit evidence, render the review experience, troubleshoot capture failures |
| Derived workspace content | Detected or uncertain facts, Product Truth, evidence references, findings, scores, Current/Proposed drafts, Campaign outputs, saved history | Deliver the audit, preserve review continuity, create grounded marketing drafts |
| Transaction and entitlement data | Order IDs, product or plan, timestamps, payment status, entitlement status, limited metadata supplied by the payment processor | Fulfil purchases, activate access, handle refunds, accounting, fraud checks, disputes |
| Support and contact data | Name, email, subject, message, attachments you choose to send, support history | Respond to inquiries, investigate problems, maintain support continuity |
| Technical and analytics data | Browser and device context, IP-derived security signals, referrer, page views, product events, request IDs, timings, error codes, UTM parameters, cookie or storage identifiers | Security, abuse prevention, attribution, reliability, performance measurement, service improvement |
3. How public product-page capture works
When you request a Product Conversion Audit, RankSpires may retrieve the submitted public URL through bounded server-side requests and browser-capture infrastructure. The active capture design rejects private or internal network targets, limits response size and execution time, and does not use the URL workflow to sign into a merchant account or edit the live page.
The bounded HTML snapshot is processed transiently by the capture component and is not permitted to persist through that component. The visual screenshot is returned as a volatile, authenticated response artifact designed to expire within five minutes. Under the current implementation, that visual artifact is not retained by the server response component, written into telemetry, included in exports, or permitted for browser persistence.
RankSpires may retain the submitted URL and the derived facts, evidence references, audit findings, score state, proposed page content, and Campaign drafts associated with your account. These derived records let you reopen the workspace without pretending that a temporary screenshot is permanent evidence.
Public pages can contain names, reviews, profile images, contact details, or other personal information. Do not intentionally submit pages containing sensitive personal information or pages you are not authorized to have RankSpires inspect. Public accessibility does not remove privacy or third-party rights.
4. Why we use information
We use information to provide the workflow you request, verify authorization and account state, retrieve and analyze the page, separate observed facts from uncertainty, create Product Truth, produce audit and Campaign outputs, save work you ask us to retain, process purchases, answer support requests, investigate failures, prevent misuse, secure the service, and meet legal obligations.
Depending on the context, processing may be based on your consent, performance of the service agreement, legitimate interests in operating and securing RankSpires, or compliance with applicable law. Information required to deliver the requested audit is treated separately from optional analytics or marketing uses where a choice is legally required.
5. Automated analysis and AI providers
RankSpires uses software rules and may send the product facts, instructions, evidence summaries, or draft text needed for a requested feature to an AI model provider. This processing is used to analyze or generate the requested output, evaluate quality, or repair a bounded output. Payment credentials are not part of the content sent for audit or Campaign generation.
RankSpires does not treat an automated result as a final business decision. Outputs remain review-only, may contain errors, and must be checked by the user before publication or reliance.
6. Service providers and disclosures
RankSpires uses service providers to operate the product. These categories may change as infrastructure evolves, but the purpose of each disclosure remains limited to providing, securing, or supporting the service.
| Provider category | Purpose | Typical information involved |
|---|---|---|
| Google authentication | Account sign-in and identity verification | Google credential, account identifier, name, email, verification state |
| Application, database, and hosting infrastructure | Serve the application, store account and workspace records, maintain logs and backups | Account data, saved workspace data, technical logs, request metadata |
| Browser-capture infrastructure | Render the authorized public page and return bounded visual evidence | Submitted URL, rendered page response, screenshot, viewport and anchor measurements |
| AI model provider | Produce or evaluate requested audit and Campaign drafts | Relevant product facts, instructions, evidence summaries, draft outputs |
| Payment processor | Checkout, confirmation, refund and dispute handling | Order IDs, payment status, limited transaction metadata, entitlement reference |
| Analytics and operational support | Measure product use, diagnose failures, provide support | Page and event metadata, request IDs, error information, support context |
We may also disclose information when required by law, to answer a valid legal request, protect users or the service, investigate fraud or abuse, resolve a dispute, or complete a lawful business transfer. We do not sell personal information to advertisers.
8. Retention and deletion
Retention depends on the category and purpose. Short-lived raw capture artifacts follow the transient boundaries described above. Account records, acceptance history, saved Product Truth, audit outputs, Campaign drafts, entitlement records, transaction records, support history, and security logs may be retained while needed to provide the service, reopen saved work, protect the platform, process refunds, resolve disputes, satisfy accounting requirements, or comply with law.
When information is no longer reasonably necessary, we delete or anonymize it where practical. Some transaction, security, fraud, backup, or legal records may remain for a longer period even after account deletion.
9. Processing outside Québec or Canada
Some providers may process or store information outside Québec or Canada. Information processed in another jurisdiction may be subject to its laws. RankSpires uses contractual, technical, and organizational safeguards intended to limit provider use and protect information during cross-border processing.
10. Security and incident handling
We use reasonable administrative, technical, and organizational measures designed to protect information against unauthorized access, use, loss, alteration, or disclosure. Measures may include encryption in transit, access controls, environment separation, bounded URL-fetch rules, private-network rejection, structured logging, abuse controls, session validation, and entitlement checks.
No system is completely secure. If an incident creates a real risk of significant harm and notification is legally required, we will investigate, contain, document, and notify affected individuals and regulators as required by applicable law.
11. Your rights and choices
Depending on where you live, you may have rights to request access, correction, deletion, or portability; withdraw consent where processing is based on consent; object to certain uses; ask about automated processing; and complain to a privacy authority. Rights may be subject to identity verification and lawful exceptions.
To request account or data deletion, contact support@rankspires.com. Deletion may permanently remove access to saved Product Truth, audits, Campaign drafts, history, and active entitlements. We may retain limited records where required for accounting, payment, fraud prevention, security, backup integrity, or legal disputes.
You may restrict optional analytics through available consent controls or browser settings. You may stop submitting URLs at any time. Withdrawing consent does not invalidate processing already completed lawfully and may make some requested features unavailable.
12. Marketing and service messages
We send marketing messages only where permitted by law and provide an unsubscribe method. Necessary service messages about account access, security, purchases, support, entitlement, or material product and policy changes may still be sent.
13. Children
RankSpires is a business workflow and is not directed to children. We do not knowingly collect personal information from minors in violation of applicable law. Contact us if you believe a child supplied information improperly.
14. Changes to this policy
We update this policy when the product, page-capture workflow, data uses, providers, retention practices, or legal obligations materially change. We revise the date and version displayed at the top, publish the updated policy, and may require a new explicit account acceptance when the change affects what you authorize or how your information is processed.