Open menu
Your account and community
Privacy Policy
Understand what you share, who can see it, and what happens when you leave Intervals.
Who operates Intervals
Intervals is operated by Intervals For Men LLC, a limited liability company organized in New York, United States.
Intervals is initially launching in the United States only.
Information you provide
Intervals is a discussion community for adult men, ages 18 and older. Creating an account involves an email address, password and account identifier. Your profile includes a display name, last initial, age interval, adult confirmation, selected topics, participation preferences and an anonymous-posting preference.
Private check-ins record the date, your capacity, the main load you select, how you are carrying it and an optional private note. Earlier check-ins may also contain a selected need for that day.
Community activity includes posts, replies, reactions, followed discussions, blocks, notifications and reports. What you choose to write may reveal personal experiences, health information or other sensitive details. Share only what you are comfortable providing, and do not expose another person's private information.
Privacy and anonymity
Your check-ins are not published to other members. Discussions and replies are shared with members according to the community's access and moderation rules.
When you post anonymously, other members see an identity-redacted author label. Anonymous contributions remain associated with your account internally so authorized moderation can review reports, abuse and safety concerns. Anonymous posting does not make activity untraceable to Intervals.
These access controls do not mean the service is end-to-end encrypted. Information is processed by the services used to operate Intervals. Other members may also copy or quote content they can see; Intervals cannot promise to retrieve every such copy.
How information is used
- Provide account access, email confirmation, account recovery and profile settings.
- Show your private check-in history and help you find conversations relevant to your interval and selected topics.
- Operate discussions, replies, reactions, following, blocking and notifications.
- Review reports, moderate content, apply suspensions and prevent duplicate activity and abuse.
- Understand community participation through founder tools, including activity summaries, returning-member counts and contributor information. Some of these tools use account-linked information; the founder dashboard does not display private check-ins.
Private check-in choices
The following choices describe the intended consent release. Production rollout and database enforcement have not been verified.
Private check-ins require a separate choice agreeing to storage of your responses, including health information you choose to provide, for private history and summaries. Check-ins are not shared with other members.
A second, optional choice lets today's explicitly selected topic or load, such as Health or Loneliness, influence discussion suggestions. Private notes, capacity scores, carrying state, historical check-in profiles, derived summaries, safety signals, moderation information and support correspondence are not inputs to these suggestions. We do not analyze private notes to infer interests or health conditions.
You can turn off topic suggestions in check-in privacy choices and keep using check-ins, history and summaries. Future suggestions then use ordinary discussion inputs independently of your check-ins. Refreshing or returning to an open page rechecks your choices; already displayed information cannot be recalled from a device.
Withdrawing private check-in consent stops new saves, summaries and topic-based suggestions. Withdrawal does not itself delete saved records. Retained history remains available for your review and privacy requests; account deletion is separate. We keep minimal, versioned records of these choices with your account and remove them when your Auth account is deleted.
Private notes and identifiable sensitive narratives must not be used for founder growth analytics. Existing narrowly scoped safety and crisis moderation remains separate from recommendations, marketing and engagement scoring. See the Consumer Health Privacy Notice for processing and provider details.
Service providers and email
Intervals uses Supabase for authentication and hosted data, Vercel for application hosting, and Resend for founder welcome emails. These services process information needed to provide their functions. Earlier owner confirmation identified Resend as the transport for Supabase Auth emails; current provider configuration still requires release verification.
For support and privacy correspondence, ImprovMX forwards messages sent to hello@intervalsmen.com to the founder's Gmail inbox. The founder handles correspondence in Gmail and sends replies through Resend from hello@intervalsmen.com.
The current Vercel plan, analytics, telemetry and log-drain settings have not been verified for this draft. Resend open and click tracking settings are also unverified. No claim that tracking or analytics is disabled is made here. Hosting, authentication and email services may maintain operational records separately from the community activity tools described above.
Earlier provider records identified primary application data and hosting regions in the United States. Current regions still require confirmation; those records do not establish that all provider processing, support, logs or backups remain in the United States.
Welcome-email delivery records include delivery identifiers and attempt or delivery times. Server and provider records can also include diagnostic information and account identifiers used to operate and troubleshoot the service. An email delivered to you or a message you send to a contact mailbox has a lifecycle separate from your Intervals profile.
Retention and deletion
Account information, check-ins and community records remain available for their app functions unless changed or removed through the service. There is no general automatic expiry for an inactive account or its check-ins.
The deletion behavior below describes the implemented design. Production rollout and remaining browser and designated-account checks are unconfirmed.
You can request permanent account deletion using Delete my account, including before completing onboarding. The form verifies your current password. Successful deletion removes the sign-in account, profile and associated private check-ins, and removes the departing account's relevant interaction and abuse-prevention records.
Your authored post and reply text and identity references are erased. Rows that are no longer needed are pruned. Empty discussion structures, timestamps and relationships may remain where needed to preserve other members' replies or reports. Other members' content is not deleted merely because it mentions or quotes you.
If files owned by your account remain in Storage, deletion is refused. The account flow does not automatically remove files. See deletion help if you cannot complete the process.
Abuse-prevention cleanup runs during later activity for the relevant account and action. It is not a guarantee that every abuse record expires after 24 hours.
The approved correspondence retention policy is to keep routine support correspondence for 12 months after resolution. We keep privacy and legal request correspondence for 24 months after closure, then delete it unless a longer period is required for an active dispute, a security or fraud investigation, or a legal obligation. Real-case execution of this policy remains to be verified before publication.
Deleting active app records does not itself erase provider backups, diagnostic logs, delivered emails, messages held in a contact mailbox or copies retained on devices. Those records have separate retention and deletion processes. Provider-published retention periods apply to particular record categories, not every copy. Some internal backup and purge details are controlled by the provider and are not publicly specified; we do not promise a single provider-wide erasure deadline.
Cookies and your device
Authentication uses browser session storage and cookies. Intervals also stores a guided-onboarding completion flag and a short history of discussion-prompt choices in your browser. Those preferences do not have an automatic expiry in the app.
You can clear site data using your browser settings; doing so may sign you out or reset local preferences. Account deletion does not promise to clear every browser-local preference or cached copy on every device.
Your choices and questions
You choose whether to contribute to discussions, use anonymous posting or add an optional check-in note. Profile settings let you change available profile and posting preferences. You can block members, report concerning content or use the account-deletion form.
See privacy help or contact hello@intervalsmen.com for support or privacy questions. Do not include passwords, verification codes, session tokens or private check-in notes in a message.
We do not fulfill emailed requests for access to or changes to personal information based on email alone. We require verification appropriate to the information requested before disclosing, modifying or deleting it. We will never ask for your password by email.
The planned request-verification workflow, whose production operation remains unconfirmed, uses in-app confirmation tied to the specific request and its scope for existing accounts that can sign in. This includes inactive accounts. Suspended members can use the same confirmation route without regaining community access. Signing in alone does not confirm a request, and confirmation does not automatically fulfill it.
We do not restore deleted accounts or data, recover backups, or reconstruct deleted identifiers to verify a request. Creating a new account with the same email address does not establish ownership of earlier records or transfer requests or authorizations from a deleted account.
For former-account claims and separately retained correspondence, we assess only evidence already lawfully retained. Possession of an email address alone is not sufficient for sensitive historical disclosure or changes. If we cannot reliably verify ownership, we will not disclose, modify or delete the claimed information on that basis.
Information that is no longer held cannot be supplied. That is different from being unable to verify ownership of information that may remain. We explain verification limitations without confirming account history or revealing another member's information.
Read the Terms and Community Guidelines for the expectations that apply when participating.
Policy changes
We may update this policy to reflect changes to Intervals or how information is handled. Published versions will identify their effective date. We will explain material changes and provide any notice or obtain any consent required before those changes apply.