1. Data we process
We process account data (name, email), organization and membership data, site configuration, scan results, and integration metadata needed to run the service.
We also record product events such as completed scans, monitoring confirmations and account creation. When you submit a free scan, we include a category for the page and referring site, and a label for recognized campaign links. These fields do not contain the full referring URL, search terms or the URLs you submit for scanning. Events use internal identifiers and hashed account or request identifiers to connect related actions.
When you scan through an AI assistant using our MCP integration, ShareScan receives the public URL you provide, fetches the page and its referenced preview assets, and stores the URL and scan results in a report. The findings and report link are returned to your assistant provider. Report links are accessible to anyone who has them and normally expire after 180 days; link expiry does not itself delete stored scan data. Do not submit credentials, private pages or URLs containing secrets. A scan does not enable monitoring; email monitoring requires separate consent and email confirmation.
On public pages, we also count page views and visits using a random identifier held only in the open page's memory. It resets on reload, in a new tab, or after a period without page navigation. We record public page paths, the landing page, a referring-site category and recognized campaign labels. We do not send query strings, URL fragments, full referrer URLs, IP addresses or user-agent strings with these page-view events, or create account profiles from them. When you start a scan in the same visit, we attach this temporary identifier and public landing-page context to the scan events. This lets us measure which resources lead to completed reports and voluntary follow-ups using the report's internal identifier. If you create a site in a workspace from a report, we can also relate that step to the workspace's first subscription payment when calculating aggregate conversion counts. We skip this measurement when the browser sends Do Not Track or Global Privacy Control.
2. Why we process data
Data is used to authenticate users, monitor configured URLs, deliver alerts, support billing, secure integrations, and troubleshoot service issues.
Product analytics helps us understand which resources lead to useful scans and voluntary follow-ups. This measurement does not add analytics cookies or browser storage.
4. Retention and deletion
Data is retained while your account is active and for a limited period after deactivation for security, accounting, and legal compliance. You can request deletion through support.
5. Security
We apply technical and organizational safeguards to protect data, including access controls, encrypted transport, and audit logging.