Privacy Policy

• Account: your email address and name.
• Builders: your project details, what you want to learn, who you want to hear from, your weekly availability, and your meeting link if you add one.
• Testers: age range, what you do, country, devices, interests, the apps you use, when you’re free, and whether you write code.
• Sessions: booking times, the takeaways testers write, the notes and ratings builders leave, a written transcript of sessions held in Google Meet or Zoom when the tester agreed to transcription, and, for self-paced sessions, the screen and voice recording the tester chose to make and send.
• Payments: handled by Stripe. We store Stripe’s IDs for payments and payout accounts, never full card or bank numbers.
• Technical: the IP address of sign-in requests (to stop abuse) and standard server logs.

• To match builders and testers, and to book and run sessions.
• To take payments and pay testers.
• To send emails you need: sign-in links, booking confirmations, reminders and payout notices. We don’t send marketing email without asking.
• To keep usertank secure and fix problems.

• Builders see a tester’s first name and profile summary (age range, what they do, country, devices and interests). Never their email address.
• Testers see the builder’s project name and description and the request details.
• During a call, both people see whatever they choose to show on camera or by sharing their screen.

We don’t sell personal information. We use these services to run usertank, and they only process data to provide their service to us:

• Stripe: payments, payouts and identity checks for testers who get paid
• Daily: video calls in usertank’s built-in room (not recorded)
• Recall.ai: the notetaker that transcribes Google Meet and Zoom sessions when the tester agrees. It holds the recording for at most 24 hours, and we delete it as soon as the transcript is saved.
• Resend: sending email
• Railway: hosting, our database, and storage for self-paced session recordings
• Google: only if a builder connects Google Calendar, to check busy times and add booked sessions
• LinkedIn: only if a tester chooses to verify their profile with LinkedIn

These providers may store data in the United States or other countries. We may also share information if the law requires it.

If you connect Google Calendar, usertank reads only your free/busy times (not event details) to hide times you’re busy, and creates an event on your calendar for each session booked through usertank. You can disconnect at any time from your Availability page.

usertank’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We don’t use Google data for advertising and don’t sell it.

If you verify with LinkedIn, usertank receives your LinkedIn name, photo, email and account ID. We store your name, photo and account ID to show builders a “LinkedIn verified” badge with your LinkedIn name, and to stop one LinkedIn account verifying several testers. We never post to LinkedIn. You can remove the verification at any time from your Profile page.

We use one cookie to keep you signed in, and one to remember who referred you if you arrive through someone’s link. No ads, no tracking cookies, no third-party analytics.

We keep your information, including session transcripts and self-paced recordings, while your account is open. Only the tester who made a recording, the builder it was made for and our team can watch it. You can ask us to delete a transcript or recording at any time. If you ask us to delete your account, we delete your profile and session details within 30 days, except records we must keep for payments, tax or legal reasons.

You can ask to see, correct or delete your information, or ask a question about how we handle it, by emailing hello@usertank.co. Depending on where you live (for example, under Canada’s PIPEDA, or in some U.S. states), you may have additional rights, and we’ll honour them.

usertank is for people aged 18 and over. We don’t knowingly collect information from anyone younger.

If we change this policy in a meaningful way, we’ll let you know by email or on the site.