Privacy Policy
This Privacy Policy describes how Stint Labs LLC, a Virginia limited liability company (“Stint”, “we”, “us”, or “our”), collects, uses, discloses, and protects information when you visit this website (stinthq.com) or join the waitlist for our private beta.
Scope. This policy covers this website, the beta waitlist, and the Google Calendar connection described in section 7, and the health and fitness data described in section 8. Everything else handled inside the Stint application is covered by the application's own privacy policy, which you can read at that link; it contains the same Google Calendar section.
1. Information we collect
Information you provide directly. When you request access to the beta, we collect:
- Your name and email address.
- A consent record: the exact consent language you agreed to, the timestamp of your agreement, and the IP address the submission came from. We keep this as proof of consent.
- Optional follow-up answers, if you complete the second step after signing up: for example, what you want from Stint, where you heard about us, and any notes you add.
- Anything you send us through the contact form or by email.
Information collected automatically. When you visit the site, we and our service providers automatically collect:
- Device and browser information: browser type and version (user-agent), device type, screen size, operating system, and preferred language.
- Usage information: the pages you view, the elements you interact with, approximate time on page, and the sequence of your visit.
- Attribution information: the page you first landed on, the site that referred you, and any campaign (UTM) parameters in the link that brought you here. We capture these on your first visit so we can tell which of our posts or campaigns are working.
- Approximate location: a coarse, city-level location derived from your IP address by our analytics provider. We do not collect precise geolocation.
- Experiment assignment: which version of the page you were shown, when we are testing more than one design (see “Analytics and A/B testing” below).
2. Cookies and similar technologies
We use a small number of cookies and browser-storage entries, all functional or analytical. We do not use advertising cookies, and we do not permit third-party ad networks on this site.
st_ab: a functional cookie that remembers which design of the page you were assigned during an A/B test, so your experience stays consistent between visits. Expires after 90 days.- Sign-up continuity cookie: set after you join, holding a random record identifier that links your sign-up to the optional follow-up step. It contains no personal details and expires after 7 days.
- Theme preference: a local-storage entry remembering your light/dark choice.
- Attribution snapshot: a local-storage entry recording the first link that brought you to the site (referrer and campaign parameters), so attribution survives if you browse to another page before signing up.
- PostHog analytics cookies: set by our analytics provider to distinguish visitors and sessions (see the next section).
You can clear or block cookies in your browser settings. Blocking them will not prevent you from browsing the site or joining the waitlist.
3. Analytics and A/B testing
We use PostHog, a product-analytics service, to understand how visitors use the site and to run controlled experiments (for example, showing two page designs to different visitors and measuring which one people prefer). PostHog collects the usage, device, attribution, and approximate-location information described above, tied to a random visitor identifier.
Session replay. Our analytics may reconstruct anonymized replays of visits (mouse movement, scrolling, and page interactions) so we can find and fix usability problems. All form inputs are masked: anything you type, whether your name, email, or anything else, is redacted before it ever reaches the replay and appears only as placeholder characters.
We do not send your name, email address, or phone number to our analytics. Analytics events describe behavior (“a visitor joined the waitlist”), not identity.
4. How we use information
We use the information described above to:
- Reserve your place in the beta (or on the waitlist) and contact you about your access;
- Send you a confirmation email when you join, and occasional updates about the beta and the product;
- Operate, secure, and troubleshoot the website;
- Detect and prevent spam, fraud, and abuse (for example, our sign-up form uses timing checks and hidden-field traps to reject automated submissions);
- Understand how visitors find and use the page, measure which campaigns and designs work, and improve the site;
- Maintain records we need for legal and compliance purposes, such as proof of consent; and
- Honor the commitments we make to founding members, such as the founding rate associated with your sign-up.
We do not use your information for automated decisions that produce legal or similarly significant effects, and we do not use it for cross-context behavioral advertising.
5. Email
When you join, we send a confirmation email and may email you about your beta access and meaningful product updates. We aim for signal, not noise. Every email includes an unsubscribe link, and unsubscribing never affects your place in line.
6. How we share information
We do not sell your personal information, and we do not share it for targeted advertising. We disclose personal information only in the following circumstances:
- Service providers. Companies that process information on our
behalf so the site can function, under contracts that limit their use of it to
providing the service to us:
- Vercel: website hosting and content delivery;
- Neon: the database that stores waitlist sign-ups;
- Resend: delivery of transactional email (your confirmation and access emails);
- PostHog: product analytics and session replay, as described above.
- Legal requirements. If we believe disclosure is required by law, regulation, legal process, or a governmental request, or is necessary to protect the rights, safety, or property of Stint, our users, or the public.
- Business transfers. If Stint is involved in a merger, acquisition, financing, or sale of assets, personal information may be transferred as part of that transaction, subject to this policy's commitments.
7. Google Calendar
Only if you connect it. From the Connect page you can connect your Google Calendar. When you do, Google asks you to allow Stint to view the events on your calendars (read-only), and tells us the email address of the Google account you connected, which we show you as "Connected as" so you know which account it is.
What we read and keep. Stint reads the events on your primary Google Calendar for the day before today through fourteen days ahead: each event's title, start and end, and, if present, its description, location and link. We keep only the title, date, start and end of each event, so it can appear in your own day list on Today, on your Plan calendar (marked "Google Calendar"), in your morning brief and in your coach's view of your day. We refresh this copy about every 15 minutes while you use Stint, and once a day. We never read your calendar list, settings or sharing rules, and we never create, change or delete anything on Google Calendar.
What we do with it, and what we don't. Your calendar events are used only to show you your day and to plan around it. The titles and times may be sent to Anthropic, our AI provider, only to write your own brief and your coach's replies; Anthropic does not train on that data. We do not sell calendar data, do not use it for advertising, do not share it with anyone else, and do not use it to develop, improve or train any AI or machine learning model. No person at Stint reads your calendar data except to fix a problem you ask us about, to investigate abuse or a security issue, or when the law requires it.
How it is protected. The sign-in tokens Google gives us are encrypted (AES-256-GCM) with a key kept outside the database, and only the code that talks to Google can decrypt them. The database that holds the copied events is encrypted at rest by our host, and all traffic is encrypted in transit.
How to stop. Tap Disconnect on the Connect page. Stint revokes its access at Google (so Stint disappears from the third-party access list in your Google account) and deletes the stored tokens the same moment. The events copied from Google are deleted with them. You can also remove Stint from your Google account at myaccount.google.com/permissions, which stops the next sync. Deleting your Stint account deletes the copied events with everything else.
Stint's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy
8. Health and fitness data
Only if you connect it. From the Connect page you can connect Apple Health (in the iPhone app), Oura or WHOOP. Each one asks your permission before Stint reads anything, and Stint only reads: we never write to Apple Health or to your wearable.
What we read. From Apple Health: sleep, steps, workouts, resting heart rate, heart-rate variability, active minutes and weight. From Oura: readiness, sleep, heart-rate variability and resting heart rate. From WHOOP: recovery, sleep, strain, heart-rate variability, resting heart rate, workouts and weight. We keep one record per day of these numbers.
What we do with it, and what we do not. Your health and fitness numbers are used only to show them to you on Track and Today, and so your coach and your morning brief can plan your day around them. The numbers may be sent to Anthropic, our AI provider, only to write your own brief and your coach replies; Anthropic does not train on that data. We never use health data for advertising or marketing, never sell it, never share it with anyone else, and never use it to develop, improve or train any AI or machine learning model. No person at Stint looks at your health data except to fix a problem you ask us about, to investigate abuse or a security issue, or when the law requires it.
How it is protected. The sign-in tokens Oura and WHOOP give us are encrypted (AES-256-GCM) with a key kept outside the database. The database that holds your numbers is encrypted at rest by our host, and all traffic is encrypted in transit.
How to stop. Tap Disconnect on the Connect page. Stint stops reading, deletes the stored sign-in, and for Oura and WHOOP revokes its access at the provider. For Apple Health you can also turn off access in the iPhone Settings app, under Health. The numbers already synced stay on your Track until you ask us to delete them (write to privacy@stinthq.com) or delete your account, which deletes them with everything else.
9. How long we keep information
- Waitlist records (name, email, answers, attribution): kept while the beta and waitlist are active and for a reasonable period afterward, so we can honor founding-member commitments and re-open access fairly. Deleted on request at any time.
- Consent records: kept as long as we may need to demonstrate consent under applicable law.
- Analytics data: retained under PostHog's standard retention schedule and deleted or aggregated over time.
- Contact-form messages: kept as long as needed to resolve your inquiry and for our records.
10. Your choices and rights
- Email: unsubscribe via the link in any email.
- Access, correction, deletion, portability: ask us to access, correct, delete, or export the information we hold about you at any time through the contact form or at privacy@stinthq.com. Deleting your record removes you from the waitlist.
- Cookies: control or clear them in your browser settings.
We will verify requests using the email address on file and respond within the time required by applicable law. We will never discriminate against you for exercising a privacy right.
11. U.S. state privacy rights
Depending on your state of residence (including California, Virginia, Colorado, Connecticut, and other states with comprehensive privacy laws), you may have statutory rights to access, correct, delete, or obtain a copy of your personal data, and to opt out of its sale, targeted advertising, or certain profiling.
We do not sell personal information and do not engage in targeted advertising or profiling of the kind those laws regulate, so there is nothing to opt out of, but the access, correction, and deletion rights above are available to everyone, not just where the law requires them. Where required, we honor browser opt-out preference signals such as Global Privacy Control (GPC).
To exercise a right, use the contact form. If we decline a request, you may appeal by replying to our decision, and you may also contact your state attorney general.
12. Visitors outside the United States
This site is operated from the United States, and the information we collect is stored and processed in the United States by us and the service providers listed above. Data-protection laws in the U.S. may differ from those in your country. By using the site or joining the waitlist, you understand that your information will be transferred to and processed in the United States.
If you are in the European Economic Area, the United Kingdom, or Switzerland: we process the information you provide on the basis of consent (which you may withdraw at any time) and our legitimate interests in operating, securing, and improving the site. You additionally have the rights to object to or restrict processing and to lodge a complaint with your local supervisory authority.
13. Security
We take reasonable technical and organizational measures to protect your information: all traffic to the site is encrypted in transit (TLS), sign-up data is stored in an access-controlled database encrypted at rest, and access to personal information is limited to those who need it to operate the service. No method of transmission or storage is completely secure, and we cannot guarantee absolute security, but if we learn of a breach affecting your personal information, we will notify you as required by law.
14. Children
This site is not directed to children, and we do not knowingly collect personal information from anyone under 16. If you believe a child has provided us personal information, contact us and we will delete it.
15. Changes to this policy
We may update this policy from time to time. The “last updated” date above will change when we do, and if a change meaningfully reduces your rights or expands what we collect, we will take reasonable steps to bring it to your attention, for example, by emailing the waitlist.
16. Contact us
Stint Labs LLC
Attn: Privacy
privacy@stinthq.com
or via the contact form on this site.