Vrsnify

Privacy Policy

Last updated 2 November 2026

This policy covers the personal data Vrsnify handles when you use our website, app, install pages, API and SDK.

1. Who we are

Vrsnify (“we”, “us”) runs this website: the Vrsnify app, its public install and share pages, and the APIs and SDK that apps distributed through Vrsnify call. This policy explains what personal data we handle, why, who we share it with, and the choices you have.

Teams use Vrsnify to share test builds with their testers. When a team (an organization or project owner) collects data about its testers through Vrsnify, such as device registrations, bug reports or crash reports from their app, that team decides what is collected and we process it on their behalf. If you’re a tester with a question about that data, you can ask the team that shared the build with you, or use our contact formand we’ll work with them to answer it.

2. Information we collect

Your account. Name, email address, password (stored only as a one-way hash by our sign-in provider), profile photo if you add one, when you accepted these terms, and two-factor authentication settings.

What you add to Vrsnify. Organizations, projects, tasks, comments and mentions, time entries, test cases, feature flags, release notes, screenshots and other files. App builds you upload (.ipa, .apk, .aab) and the details we read from them: app name, icon, version, bundle or package ID, minimum OS and provisioning profile details.

Uploads without an account. If you upload a build from our home page, the build and the email address you give us, so we can send you the link and connect the upload to your account if you sign up later.

Tester and device information, sent by a team’s testers or by apps that use our SDK:

  • Registered devices: device identifier (UDID), device name, and the name and email of whoever registered it.
  • Bug reports: what the tester writes, device model, operating system, app version, an optional screenshot, and their name and email if they provide them.
  • Crash reports: the error and stack trace, app version, device model and name, operating system, network type and Wi-Fi signal strength.
  • Install confirmations and install-page visits: device model, operating system and app version, plus counts of install clicks.
  • Push notification tokens for devices that opted in to update notifications.

Technical and security information. The IP address and browser of each signed-in session, which you can review and sign out in Settings → Active sessions. Short records of requests to our public endpoints, keyed by IP address or email address, which we use to limit abuse. Browser push subscription details if you turn on browser notifications. Messages you send to support and the page you sent them from.

We read your time zone from your IP address on each request so we can show times in your local time. We don’t store it.

Records of your privacy choices and requests. When you make a cookie choice, accept these policies, export your data, delete your account or send us a privacy request, we keep a short record of what happened and when, and which version of this policy was in force. These records hold your user ID or a one-way hash of your email address, never the address itself, so they can show we respected your choices even after your account is deleted.

Credentials you give us for integrations. API tokens (we store only a hash of each token), webhook URLs, Firebase service-account keys and App Store Connect API keys. We use them only to do what you set them up to do.

We don’t use advertising or analytics trackers, and we don’t buy data about you from anyone.

3. How we use information

  • To provide Vrsnify: hosting and distributing builds, running projects and boards, and showing your team’s activity.
  • To send the emails and notifications you or your team have set up (invites, mentions, release and crash alerts, reminders, daily digests). You can turn these off per project in Settings → Notification preferences.
  • To keep Vrsnify secure: sign-in protection, two-factor authentication, password-change alerts, rate limiting and abuse prevention.
  • To answer support requests.
  • To run AI features, described below.
  • To meet legal obligations and enforce our Terms of Service.

4. AI features

When a bug report comes in, we send its text (title, description, steps, expected and actual result) to Anthropic to suggest a category and severity. When you click to tidy up release notes, we send the notes text. We never send builds, screenshots or credentials.

Under Anthropic’s commercial terms, what we send isn’t used to train their models. The suggestions are only hints: your team decides what to do with every report.

5. Who we share information with

We don’t sell personal data or share it for advertising. We share it only with the following people and services, and only as far as each needs.

Service providers that run parts of Vrsnify for us:

  • SupabaseDatabase, sign-in and file storage (your account, projects, builds, screenshots). Data is stored in the United States.
  • VercelHosting the website and APIs, and connecting an organization's custom domain.
  • ResendDelivering the emails we send (invites, notifications, digests, alerts).
  • AnthropicAI features: suggesting a bug report's category and severity, and tidying release notes when you ask it to.
  • ipinfo.ioTurning the IP address of a signed-in session into an approximate location in Settings → Active sessions (sent over an encrypted connection).
  • Google Firebase Cloud Messaging, Apple Push Notification service, and browser push servicesDelivering push notifications, using credentials a project owner adds or the browser you allowed notifications in.
  • Apple App Store ConnectOnly if a project owner connects TestFlight, using the API key they provide.
  • Your team. People in your projects and organizations see what you add there, according to their role. Organization admins can see every project in their organization.
  • Anyone with a share link. A build’s share page shows its app name, icon, version and release notes, and lets anyone who has the link install it, unless the owner turns the link off or adds an expiry or PIN.
  • Integrations your team sets up. Webhooks send release, task and approval events to the URLs a project owner adds, such as Slack or Microsoft Teams.
  • Vrsnify operators. A small number of people who run Vrsnify can access accounts and content to provide support, keep the service secure and deal with abuse. Every page they open and every action they take is logged.
  • When the law requires it, or to protect the rights, safety or property of our users, the public or Vrsnify.
  • If Vrsnify is reorganized, merged or sold, with the new operator, who must keep this policy’s protections in place.

6. Where your data is stored

Our database and file storage are in the United States, and our providers may process data in other countries. By using Vrsnify you understand your data will be transferred outside India (or wherever you are) for these purposes. We rely on our providers’ safeguards to protect it.

7. How long we keep it

  • Account information: until you delete your account.
  • Project content, including builds, tasks, comments and tester data: until the project’s owners delete it.
  • When you delete your account: data that’s only about you is deleted, including your notifications and favorites, push subscriptions, support messages, install records and builds you uploaded without an account. What you added to other people’s projects (comments, time entries, approvals, activity) stays with that team’s work but is no longer linked to your name or email; it’s shown as coming from a deleted user. Your name and email are also removed from bug reports and device registrations you submitted.
  • Archived builds: permanently deleted in the first nightly clean-up (at 00:00 IST) that runs at least 12 hours after the build was archived, or straight away if an owner chooses “Delete now”.
  • Legal hold: a project owner can place a project on legal hold, which stops its data being deleted until they lift it.
  • Push notification tokens: removed as soon as the push service tells us they no longer work.
  • Rate-limiting records (which contain IP or email addresses): deleted automatically after 7 days.
  • Records of privacy choices, requests and operator access (described above): kept for 3 years so we can answer questions or complaints about them, then deleted automatically.
  • Backups made by our database provider can keep deleted data for a limited time before it’s overwritten.

8. Your rights and choices

Depending on where you live, including under India’s Digital Personal Data Protection Act, 2023, you can:

  • Access and take a copy of your data: Settings → Export my data. The export includes everything linked to your account or email, including bug reports and devices you submitted, support messages, uploads, and the records we keep of your privacy choices and requests.
  • Correct your name or photo in your profile, or ask us to correct anything else.
  • Delete your account: Settings → Delete account. If you’re the only owner of a project or the only admin of an organization, you’ll need to hand it over first.
  • Withdraw consent or object: turn off email or push notifications, or change your cookie choice. This doesn’t affect anything we did before.
  • Nominate someone to exercise these rights for you if you die or become unable to.
  • Raise a grievance with us through our contact form and, if you’re not satisfied, with the Data Protection Board of India.

If you’re in the European Union or United Kingdom, you have the equivalent rights under the GDPR, including the right to complain to your local data protection authority.

9. Cookies

Vrsnify uses no advertising, analytics or third-party tracking cookies. Only the items below are stored in your browser. Essential ones are always on. Functional ones are only set if you allow them: choose “Accept all”, or “Customize” to decide category by category. Optional categories start switched off. You can change your choice at any time, and we record each choice so we can show what you agreed to.

  • Sign-in session (sb-…-auth-token)Essential Keeps you signed in.
  • Share PIN attemptsEssential Limits wrong PIN guesses on a protected install page. Expires after the lockout window.
  • cookie_consentEssential Remembers the choice you made in the cookie banner. 1 year.
  • cookie_consent_idEssential A random ID that links your cookie choices to our record of them, so we can show what you agreed to. 1 year.
  • Theme and sidebar (browser storage)Essential Only saved when you pick a theme or collapse the sidebar yourself.
  • qa_bucketFunctional Keeps you in the same staged-rollout group on install pages across visits. Only set if you allow Functional cookies ("Accept all", or switched on under "Customize"). 1 year.

10. Security

We use encrypted connections (HTTPS), database access rules that limit each person to their own projects, hashed API tokens, optional or organization-required two-factor authentication, alerts when your password changes, and a list of active sessions you can sign out of. No service is perfectly secure. If a breach affects your personal data, we’ll notify you and the relevant authorities as the law requires.

11. Children

Vrsnify is for professional teams and isn’t meant for anyone under 18; you confirm you’re 18 or older when you sign up. We don’t knowingly collect children’s personal data. If you think a child has given us their data, contact us and we’ll delete it.

12. Changes to this policy

When we change this policy, we’ll update the date at the top. If a change is significant, we’ll also tell you by email or in the app before it takes effect.

13. Contact and grievances

For privacy questions, requests or grievances, use our contact form. You don’t need an account, so it works for testers and for people who have deleted their account. If you’re signed in, you can also use Help (?) → Contact support. Our support team handles grievances and we aim to reply within 30 days.

Before acting on a privacy request, we may ask you to confirm that you own the email address or account it’s about. If your request is about tester data a team collected, we’ll involve that team, because they decide how that data is used.