Privacy Policy
Innotesce provides public website-readiness audits. This policy explains the limited information processed when you use the service.
Information we process
When you run an audit, we process the public website address you submit and public content that the website makes available. We retain a limited audit history for that exact URL, including score and check summaries. When you unlock a detailed report, we store the first name, email address, audited website, score, and audit reference you provide, and email a copy of that report to the address you provided. To avoid duplicate sends, we retain a short-lived, one-way hashed entitlement for that website and email; the browser also stores a first-party record that the report was unlocked for that website, which you can clear in the report. Report delivery is transactional and does not subscribe you to marketing. If you separately select the optional follow-up checkbox, we record the consent time and disclosure version and schedule two messages: the report’s highest-priority fixes and one invitation to the $199 AI Visibility Fix. Every follow-up includes an unsubscribe link. Unsubscribing, a provider suppression, a hard bounce, or a spam complaint stops the sequence; we may retain a one-way hash of the address so that suppression remains effective. Delivery attempts and provider events may be retained with the lead for up to 12 months. When you request an implementation plan, we store the name, business name, work email, website, and score you provide. When you submit a partner application, we store your name, work email, business or agency, public website, the kinds of clients you serve, and your preferred way to collaborate. A partner application is used to review and respond to that request and does not subscribe you to marketing. If you purchase a service, our payment provider processes your payment information and we retain the order reference, purchased service, checkout email, project-intake details, and subscription status needed to deliver it. Monitoring plans also retain scheduled score reports, technical-change summaries, scan errors, the next scheduled scan date, the business profile details supplied during intake, and the exact AI-answer prompts selected by the customer. If provider/API collection is activated, the selected prompts and supplied business profile are sent to the disclosed provider; the current adapter is designed for the Perplexity Agent API using the named Sonar model and web-search tool. Each observation may retain the named provider and model, run time, mention outcome, inferable position or prominence, competitor mentions, a limited answer snapshot, citations or sources, and collection errors. These observations measure only the disclosed provider API and saved prompt set; they do not reproduce personalized consumer AI-product sessions.
Product analytics
We collect limited first-party product events—page views, audit starts and completions, detailed-report unlocks, checkout starts, and confirmed purchases—to understand the service funnel. Analytics events may contain the page path, a random session identifier stored only for the browser tab, limited campaign tags, the submitted website hostname and audit score for completed scans, or the purchased plan. They do not contain an email address, name, raw IP address, user-agent string, full referrer, advertising identifier, or cross-site tracking cookie. Anonymous analytics events expire after 90 days. Collection respects Global Privacy Control and Do Not Track.
How we use it
We use this information to run requested and scheduled audits, show repeat-audit trends, send monitoring reports and service alerts, enforce subscription entitlements, respond to implementation-plan and partner requests, deliver purchased services, maintain security, and improve the service. We do not sell personal information.
Connected business accounts
If you choose to connect Google Business Profile, Google asks you to authorize access to the profiles you own or manage. We securely store an encrypted OAuth refresh token so scheduled comparisons can run while you are offline. We temporarily cache a limited profile snapshot—including business name, address, phone, website, category, hours, service area, status, and Google identifiers—for no more than 29 days. You can revoke access from your Google Account or ask us to disconnect and delete the connection.
Customer accounts and CMS connections
Customer access uses a one-time email link and a secure browser session. We store the normalized email address, session metadata, account-security version, and timestamps needed to authenticate and recover the account; we do not store an Innotesce password. If you connect a content-management system, we store the site address, provider, encrypted connection credential, draft content, approval state, remote content identifier, publication status, and version history needed to perform actions you explicitly approve. CMS credentials are not displayed after connection.
The Innotesce Connector for WordPress exchanges a single-use account key for a revocable site credential. We store the account association, public site address, plugin and WordPress versions, declared capabilities, connection activity, requested audit summary, and limited change-event metadata. Change events may identify the event type, post type and numeric post identifier, changed plugin or theme name, detected SEO provider, and aggregate WooCommerce product and in-stock counts. The connector does not send WooCommerce customer or order records. Business facts and unpublished draft contents remain in WordPress unless you separately use an authorized Innotesce publishing workflow.
Publishing is not automatic. A draft must be previewed and its current version explicitly approved before Innotesce can publish it. Where rollback is offered, it republishes an earlier version stored by Innotesce and may not include changes made directly in the CMS or by another tool.
Public website content
The scanner is designed for publicly accessible pages. Do not submit private, internal, or password-protected URLs.
Retention and security
Detailed-report, implementation-request, and partner-application records are retained for up to 12 months. Detailed report snapshots expire after 30 days, browser-email access records and anonymous product analytics events expire after 90 days, and audit-history records are limited to the latest 12 runs per exact URL and retained for up to 12 months. Order, subscription-status, monitoring, customer-account, CMS connection, draft, publishing-history, and administrator-audit records are retained only as needed to operate the service, deliver purchased work, preserve the customer’s history, maintain security, and follow up on requests. Private monitoring-dashboard and one-time login links should not be shared. We use reasonable technical measures to protect stored data, but no online system is completely secure.
Your choices
Transactional email recovery temporarily stores the recipient and original message while retrying delivery for up to 20 hours. Message content and recipient details are removed from the recovery job when it is accepted, canceled, or stopped for review; delayed processing during an outage may delay cleanup. Queued messages are checked against account deletion before sending. Recent job indexes expire after 30 days; minimal pseudonymous deduplication markers remain to prevent repeat sends. Provider acceptance is not a guarantee of inbox delivery, and messages already handed to a provider cannot be recalled.
Customers can start permanent account deletion from the Privacy section of their account, using a fresh sign-in link and typing DELETE. Subscriptions must first be canceled and cancellation must take effect; account deletion does not cancel billing or issue refunds. Administrator accounts require assisted deletion after administrative access has been transferred.
Access is revoked when deletion starts. Resumable background cleanup removes the account profile, account-linked report requests, private monitoring history, CMS drafts and publishing history, and stored integration credentials. Minimal purchase records remain for accounting, alongside pseudonymous security/deletion markers and email-suppression hashes that prevent stale credentials or delayed events from restoring access. Public anonymous website audits are not account-owned and follow their normal expiration. Content already published to your website, delivered emails, payment-provider records, and provider backups are outside this account-cleanup process. Revoke connected apps at the provider separately. Contact support to check completion or before registering again.
You can disable anonymous analytics in this browser using the control above, and you may revoke all browser sessions from your account. You can also ask us to access, correct, disconnect, or delete information associated with an account, CMS connection, implementation-plan request, partner application, or purchase by contacting us at hello@innotesce.com. Deleting a CMS connection does not delete content already published to that CMS.
Changes
We may update this policy as the service evolves. The date at the top indicates the latest revision.