Privacy policy
Effective 23 October 2026.
Surfacd is operated by ImpactEngine Digital LLP, India. For support, billing questions or privacy requests, contact hi@surfacd.co.
Information we use
We process account and authentication information, workspace membership, projects, saved research, notes, comments, plans and reports you choose to import. We use this information to provide the service, maintain access controls, support customers and prevent abuse. Upload reports only when authorized. Do not upload payment-card details, passwords or unnecessary merchant or customer personal information.
Research also contains dated observations of public Shopify App Store listings, search results and selected reviews. These observations are separate from private workspace data. Source links, observation dates and coverage limitations accompany retained evidence where available. Surfacd is independent of Shopify and the apps it describes.
Private workspaces and sharing
Imported performance reports, projects, notes and plans are scoped to your workspace. Owners control membership and roles; authorized members can access or export data according to their role. Anyone you give a downloaded file to can retain that copy. Support and operational access is restricted to authorized purposes. Private customer reports do not become part of the shared research corpus.
Collection and automated analysis
Reading saved research uses retained observations. Authorized collection and monitoring jobs request public search or listing pages using browser and proxy infrastructure. Semantic competition assessments send the research keyword and public listing evidence through OpenRouter to the selected model provider. Saved private notes and uploaded performance reports are not inputs to this corpus-scoring workflow. Provider processing and retention depend on the configured service and provider; we do not promise universal zero retention or model accuracy.
Service providers
Infrastructure includes OVHcloud hosting, Clerk authentication, Decodo proxy routing, and OpenRouter with the selected inference provider, currently Liquid for corpus scoring. When paid billing is enabled, Paddle handles checkout and subscription payments as merchant of record. Providers may process information outside India. Their privacy terms describe their processing: OVHcloud, Clerk, Decodo, OpenRouter and Paddle.
Retention and deletion
- Raw private performance uploads and staged rows expire seven days after upload. Scheduled cleanup removes expired staging, including staging for committed reports. Polling and retrying do not extend this deadline.
- Committed normalized report facts, saved research and workspace work remain until deleted under the account or workspace lifecycle. Removing upload staging does not erase committed facts.
- Generated selected-plan and comparison export jobs expire after 24 hours. Downloads require current authorization. Copies you download are controlled by you.
- Demo profiles and their private work are removed after 30 days. Product-event records and the billing-event replay ledger expire after 90 days. Expired rate-limit windows are removed after they are more than one day old.
Owners can request workspace deletion through the service. The deletion workflow removes private workspace data and applicable stored artifacts. Shared public research is retained separately; deleting a private project does not erase an independent public source. Limited billing, security and audit records can remain for operational or legal obligations. Provider records follow the applicable provider policies.
Contact us to request access, correction, export or deletion, or to raise a concern about retained public-source information. We may verify your identity and authority before acting.
Cookies, measurement and security
Essential cookies support authentication, the demo and security. The demo cookie lasts up to 30 days. Optional acquisition measurement is controlled through Privacy preferences and uses a separate 30-day identifier when enabled and accepted. Product measurement excludes research keywords and private notes. Optional preferences do not disable essential authentication or security processing.
Abuse prevention derives a keyed HMAC from the client IP address supplied by the HTTPS ingress. IPv6 addresses are grouped by their /64 prefix. The application rate-limit table stores that HMAC and counters, rather than the raw address. Hosting, ingress and authentication providers can process IP addresses and security logs separately.