Privacy Policy
Last updated: 2026-08-27
Sprinty is currently in pre-release. This policy explains how we handle beta-access requests, onboarding communications, optional lifecycle consent, and the limited security and operational data required to run a trust-first beta.
What we collect
- Work email, company name, and company size for beta qualification and onboarding
- Optional consent for lifecycle and announcement emails
- Optional marketing attribution parameters (UTMs) and referrer
- Operational anti-abuse and delivery-state data needed to protect the beta and reconcile access emails
How we use it
- Instantly grant clearly qualified beta access, review exceptions, and send access-granted emails
- Understand demand and prioritize roadmap feedback
- Operate beta security controls such as work-email qualification, rate limiting, and access-email reconciliation
- Send optional waitlist nurture, announcements, and onboarding drips when you opt in
Service providers
- Upstash / Vercel KV stores waitlist and access-state records used by the beta workflow.
- Postmark handles product-critical transactional beta emails and feedback intake.
- Brevo may be used for optional waitlist nurture, announcements, and onboarding lifecycle emails.
- Cloudflare Turnstile provides bot and abuse protection on the beta-access form.
- Stytch provides sign-in authentication and session management for approved beta users.
Analytics and video disclosures
Video delivery and measurement. Sprinty uses Mux to host and deliver the product walkthrough and to measure aggregate playback engagement, quality and reliability. Sprinty configures the player not to use Mux analytics cookies and does not send Mux customer tenant, mailbox, permission or waitlist-form data.
Product and acquisition analytics. Sprinty uses PostHog Cloud EU to measure a limited set of acquisition, beta-access and product milestones. Events are sent through Sprinty’s servers using pseudonymous identifiers and strict data allowlists. Sprinty does not use session replay, form capture, DOM recording or analytics advertising profiles.
Performance measurement. Sprinty uses Vercel Speed Insights on selected public landing-page routes to measure aggregate real-world performance such as Core Web Vitals.
Retention and deletion
We retain beta-access and waitlist records only for as long as they are needed to run the pre-release program, support approved onboarding, prevent abuse, and maintain a reliable operational history for that beta workflow. If you want your waitlist data removed, contact us.
Support and privacy contact
For beta-access questions, data requests, or privacy issues, contact feedback@sprinty.io.
What we don’t do
- We don’t sell your information.
- We don’t send unrelated marketing spam.
- We don’t use your waitlist submission to claim mailbox-content access or tenant-wide send capability.
This policy may evolve as the product matures. For now, the waitlist is the primary data collection flow.
Join the beta waitlist.
Use your work email to join the queue. Clearly qualified teams can get access immediately, and exceptions are reviewed in waves.