What this page covers

This page explains, in plain language, what IndieDevTest stores and shares when you use the site. It describes how the product works today — not legal advice, and not a guarantee beyond these product facts.

Accounts (Clerk, email, and optional GitHub)

You sign in through Clerk using email or, if you choose, GitHub. Clerk holds your authentication session and any linked provider details needed to sign you in.

After you sign in, we keep a local profile in our database with information such as your Clerk user id, display name, profile image URL, and an optional linked GitHub id and username. You can also add a testing contact email, optional bio, and X/Twitter handle during onboarding.

Public profiles and listings

Developer profiles and app listings you publish are meant to be public. That typically includes your display name, profile handle, photo, bio, social handle if you added one, and the app details you post (name, description, logo, store or TestFlight link, platform, and status).

Anyone can browse open listings. Do not put private secrets in profile text or listing copy.

Tester emails

Your saved testing contact email is stored on your private profile. When you request to test someone’s app, we snapshot and share it with that listing’s owner. When you accept a tester for your own app, we share your saved contact email with that tester. It is never shown on public browse pages or public profiles.

Private tester feedback and devices

When a tester has joined a testing track, they can submit private feedback about that app. We store the issue title, severity, details, optional reproduction steps, and an optional free-text device name. This feedback is visible to the tester who submitted it and the owner of the relevant listing, not to the public.

Listing owners can mark feedback as unresolved, fixed, or skipped. That status is visible to the tester and the listing owner and helps them track the outcome of a report.

Listing reports and moderation

Signed-in members can privately report a listing for spam or scams, inappropriate content, misleading links, impersonation, or another concern. We store the report, its optional explanation, and the reporting account so the site admin can investigate and prevent duplicate reports. The listing owner is not shown the reporter’s identity.

Transactional email (SendGrid)

We use SendGrid to send product emails. Those include contact-form messages and emails about tester requests (for example when someone asks to test your app, or when a request is accepted or declined). Reminder emails about listing milestones may also go out when that feature is enabled.

Admin alerts (Pushover)

If configured, the site can send optional Pushover notifications to the site admin for operational events such as a first-time signup, a contact-form submission, a tester request, or a listing report. Email addresses in those alerts are masked where applicable.

Analytics (Umami)

Analytics are optional. If Umami is configured for the deployment, a self-hosted Umami script may load to collect basic page-view style usage data. If those settings are empty, the script is not loaded.

Database hosting (Neon / Postgres)

App data — profiles, listings, tester requests, assignments, reviews, and related records — lives in a Postgres database hosted on Neon.

How long we keep data

We keep account and listing data while your account and related records are active on the service. You can permanently delete your account from Profile settings; this permanently takes your profile, listings, tester activity, and feedback offline immediately and cannot be undone.

Your requests

If you want to ask about your data or correct something, contact us through the contact form. We will respond as best we can for a small indie product.

Changes

If how the product handles data changes in a meaningful way, we will update this page and the “Last updated” date above.