Privacy
Simple, useful, and respectful.
Runners Gateway only asks for information that helps your account and the app experience work. We do not use ad cookies or hidden profiling. Product events may be logged in a simple way so we can understand whether the v1 core loop is helping people check in, return, and use the community bridge.
What We Store
We store the email address you use to sign in, your Supabase auth session, and the profile or content you choose to add, such as your display name, username, bio, avatar, links, posts, comments, follows, encouragement, reports, and reset or Journey-related activity.
We may also store whether email nudges are turned on for your account, plus simple delivery records for one-off onboarding nudges, such as the nudge type, status, and when it was sent.
If you sign up through a campaign link, we may store simple source details from that link, such as UTM source, medium, campaign, content, term, source, or ref values. These help us understand which invitations lead to real app use.
Legacy blog, club, and programme records may still be stored if you used those routes while they were available. They are kept so we do not break old content or remove data unexpectedly.
Cookies
We use essential cookies for sign-in and security. If you choose the Keep me signed in on this device option, your auth session can stay on this device for up to 30 days. If you leave it unchecked, the auth session is kept for the browser session only.
The cookie notice is remembered in your browser storage so it does not keep appearing. That preference is not used for tracking. Contextual Community prompts can also be remembered in browser storage so a dismissed prompt does not keep appearing.
Why We Use It
We use this information to keep your account signed in, protect access to your account, show your profile, create the Home and Journey experience, support follows and encouragement, handle reports, and make the Skool/community bridge work clearly.
Current product measurement is intentionally small. Where analytics events exist, they are used to understand broad v1 behaviour such as profile completion, check-ins, resets, encouragement, follows, comments, mentions, and whether Community prompts were shown, dismissed, or clicked. We do not add a new external analytics provider unless it is configured for the app. Campaign source details may be reviewed alongside this internal activation data so we can see which public links lead to first and second check-ins.
If sign-up is nearly finished but your profile is still waiting, we may use your email address to send one gentle profile setup nudge. These emails are sent through our configured SMTP provider and are not used for broad marketing automation.
Your Choices
You can sign out at any time to clear your active auth session. You can also ask to access, correct, export, or delete your account data. Account settings include a data export and account pause/delete controls.
You can turn email nudges off from Account settings, and profile setup nudge emails include a direct link to turn them off.
Deleting your account marks it as deleted, removes your avatar, and hides your active profile from normal app surfaces. Some records may remain for security, moderation, backups, legal reasons, or to preserve conversations where other people also took part.
External Community
The Community page links to Skool for deeper discussion, resources, and accountability. Skool is separate from this app and has its own privacy practices, moderation, and account controls.