Data and Retention

Spyvero combines user-submitted research inputs with public advertising data and background processing records.

Customer inputs

Spyvero may store audit queries, competitor names, domains, filters, monitor schedules, uploaded images, organization settings, team membership, billing status, and support messages.

Public ad data

Audit results can include public ad text, creative media, advertiser/page names, ad identifiers, activity dates, landing page URLs, platform labels, media hashes, embeddings, cluster relationships, and score signals.

Spyvero does not claim ownership of third-party ads or advertiser content shown through the product.

Processing providers

Spyvero's production stack is designed around:

• Supabase/Postgres for application data.
• Apify for public ad scraping workflows.
• Inngest for background jobs and worker orchestration.
• Backblaze B2 or S3-compatible storage for uploaded files and persisted ad media.
• Sentry for error and performance monitoring when configured.
• Resend or another email provider for transactional email.
• Crisp for support chat when configured.
• Paddle for supported billing and checkout flows.

Media retention

Public ad media is persisted so research does not break when public CDN links expire. The intended MVP retention window for downloaded ad media is 30 days, after which media may be archived, deleted, or otherwise limited according to storage policy, plan limits, and technical constraints.

Audit records, monitor history, billing records, logs, and account data may be retained for different periods so Spyvero can provide history, support users, prevent abuse, resolve disputes, and meet legal or accounting obligations.