ϟ stride.← Back to Stride

STRIDE: ACTIVE DATING

Privacy Policy

Your information. Your choices.
A plain-language guide to privacy at Stride.

Effective and last updated:

Contact: [email protected] ↗

1. Who operates Stride

Stride: Active Dating is operated by Camron Pourhassani. Stride helps adults aged 18 or older meet through shared activities and interests. This policy explains the mobile app’s information practices and, separately, the practices of this website.

For privacy questions, support requests, safety concerns, or data-rights requests, email [email protected].

2. Information we collect

Account and authentication

We collect your name, email address, account identifiers, and authentication information when you create or use an account. Supabase Auth handles email/password authentication. If you choose Apple or Google sign-in, that provider supplies authentication information and authorized account details. Apple may supply a private relay email address. Stride does not receive your Apple or Google password.

Stride’s own signup form does not request a telephone number. However, the Google Sign-In SDK included in the inspected iOS build declares phone-number collection. This is separate from the fields requested by Stride’s signup form.

Profile information

You provide your self-reported age, gender, who you want to meet, city, activity interests, biography, and profile photos. You may also provide optional gym, run-club, and tennis-court details. Gender and dating preferences may reveal sensitive information, including sexual orientation. Activity selections describe your interests; the current app does not collect HealthKit records, step counts, or recorded workout measurements.

Location

We collect the city/state, map-pin latitude and longitude, and search radius you select. Manually selected map coordinates can be precise location information. The current app does not request GPS permission or track background location. Google Sign-In may use IP addresses to estimate general location for fraud prevention. Apple Maps receives map-related requests. City autocomplete uses a directory bundled with the app.

Interactions, communications, and safety reports

We collect likes, passes, matches, blocks, message requests, message contents, participants, timestamps, and conversation read state. Reports can include a reason, optional explanation, relevant reported-content snapshots or references, and administrator review notes. We also receive information you send directly to the operator in support or privacy communications.

Purchases

We process purchase history, transaction and subscription information, verified membership, expiration, benefit usage, and Boost activity. Apple processes payments. Stride does not receive payment-card or bank-account details. RevenueCat receives your Stride account identifier and purchase/subscription information for verification, subscription management, and subscription analytics.

Device, usage, and technical information

Service requests provide IP addresses, device/app information, request timestamps, and errors to the services involved; technical troubleshooting records may be retained. Google Sign-In’s bundled privacy declaration includes device identifiers, user identifiers, other usage information, and other data used for functionality and/or analytics. Device identifiers are not necessarily advertising identifiers. Google Sign-In and RevenueCat have analytics uses as described in this policy.

3. Why we use information

Information supports the following purposes:

  • Create and secure accounts and display member profiles.
  • Apply age, activity, gender/preference, and geographic discovery settings, and prevent previously passed or blocked profiles from appearing where applicable.
  • Provide matching, message requests, conversations, and read receipts.
  • Process reports, investigate misuse, and protect members.
  • Verify subscriptions, enforce plan benefits and daily allowances, and prevent purchase fraud.
  • Provide notifications where enabled.
  • Troubleshoot problems, maintain service reliability, and support the provider analytics described above.
  • Respond to privacy requests and applicable legal obligations.

This policy explains our practices. Accepting or reading it does not provide blanket consent to every use of sensitive information. Any consent or permission required for a feature must be obtained through the appropriate app flow.

4. What other members can see

Eligible members may see the profile information made available through the app, including your name, age, gender, city, photos, activities, biography, and optional activity details. Email addresses and saved “who you want to meet” preference fields are not included in discovery responses.

Other members receive approximate distance information, not your saved map coordinates. Comparing distance estimates from different search areas may still reveal approximate proximity.

Disabling discovery hides your profile from new discovery results while preserving existing matches and conversations. Other members can retain screenshots or copies. Previously issued photo links may remain accessible until they expire, including after discovery is paused or a member is blocked. Pausing discovery does not make all previously shared information inaccessible.

Avoid sharing home addresses, private routines, or other information you do not want members to see.

5. Photos and messages

You select individual photos through the system photo picker. Selected photos are copied locally, resized for upload, and stored in private Supabase storage. Eligible members receive time-limited viewing links. The current photo flow does not use the camera or microphone. Stride does not currently perform facial recognition or independent identity verification. Signed-out demo profiles use fictional bundled imagery rather than registered member accounts.

Messages are stored in Supabase and are not end-to-end encrypted. Authorized operational access may be necessary for reports, troubleshooting, security, or lawful requests. A sender with Stride Pro may see when a recipient has read a message, including when the recipient uses the Free plan.

6. Service providers and sharing

The services involved in delivering Stride include:

  • Supabase: authentication, database, storage, backend functions, and related technical logs.
  • RevenueCat: purchase verification, subscription management infrastructure, and subscription analytics.
  • Apple: Apple sign-in when chosen, payments, maps, and iPhone notification delivery.
  • Google: Google sign-in, authentication/security processing, and SDK-declared analytics. Google also serves fonts on this website and provides the Gmail service used for contact emails.
  • Expo: app infrastructure and push delivery where enabled.
  • Cloudflare: website hosting and delivery, as described in the website section below.

Stride requires third parties receiving personal information from us to provide the same or equal protection described in this policy and required by applicable App Store guidelines. We use applicable service agreements, data-processing terms, confidentiality obligations, and technical and organizational safeguards to protect information processed on our behalf. Providers acting on our instructions may process that information only for the authorized services and other purposes permitted by applicable law. Apple and Google also process certain information independently under their own privacy policies when you use their services.

We share profile and conversation information with other members as needed to deliver those features. Authorized administrators can access reports and relevant content to review safety issues. Information may also be disclosed when necessary to comply with lawful obligations, protect users, or investigate misuse.

The inspected app has no identified advertising integration, and the inspected SDK privacy declarations mark tracking as off. This does not mean that no information is shared with service providers or that all provider processing is limited to app functionality.

Providers have their own terms and privacy notices governing their services. Relevant notices include Supabase Privacy Policy (Data Processing Addendum), RevenueCat Privacy Policy (Data Processing Addendum), Apple, Google, Expo Privacy Policy (Terms of Service), and Cloudflare Privacy Policy (Data Processing Addendum).

7. Notifications and permissions

Notification preferences are stored with your account. If push delivery is enabled and permission is granted, a push token can be associated with your account/session. Expo and Apple deliver iPhone notifications.

Message-preview preferences affect whether message text appears in alerts. You can change available preferences in Stride and permissions in iPhone Settings. Delivered notifications cannot be recalled.

8. Storage and security

The app stores a sign-in session, account-specific drafts, selected-photo files, and location-related cache on your device. This local storage is not an encrypted vault. Server access controls restrict access to profiles, conversations, reports, and membership information.

No storage system or transmission can be guaranteed completely secure. Keep your device and account credentials secure. This policy does not promise a particular processing country or that information stays within your country.

9. How long information is kept

Retention depends on the information, the purpose for keeping it, the controls you use, and the services processing it. The app’s deletion flow and provider-held records are separate.

  • Account, profile, photos, and associated service records: generally remain while your account exists, unless removed through available controls. Account deletion requests removal of the primary app records listed below.
  • Messages, interactions, and reports: are stored to operate conversations, matching, safety review, and related features. Reports can include copies of reported content. The current account-deletion flow removes reports by or about the deleted account and related primary conversation and interaction records.
  • Local drafts, selected-photo files, and location cache: support the app on your device. Account-specific drafts and caches on that device are cleared by the deletion flow.
  • Subscriptions and transactions: verified membership records associated with the account are removed through the app deletion flow. When you delete your Stride account, we also request deletion of the associated RevenueCat customer record. RevenueCat processes this request asynchronously. If cleanup cannot finish, your profile stays hidden and the app lets you retry. Apple subscriptions and transaction records are handled separately. Deleting your account does not cancel an Apple subscription.
  • Provider logs, backups, and technical records: Stride currently uses Supabase Free, which does not include scheduled project backups. We do not maintain separate manual database backups. The plan provides a one-day API/database log-access window; this does not mean every internal provider record is erased after one day. Provider-held technical records may remain under the provider’s applicable retention practices. The in-app deletion flow does not erase all provider-held technical records.
  • Support and privacy communications: are separate from app records and are not automatically deleted when an app account is deleted.

There is no single deletion period that applies to every category above. For help with records remaining after account deletion, or to request deletion of support communications or applicable provider-held data, email [email protected]. Some records may need to be retained for applicable legal obligations or legitimate security reasons. An account deletion does not mean that every copy held by every party is immediately erased.

10. Delete your account

In the app: Profile → Edit profile → Delete account

Identity confirmation is required. The implemented flow requests removal of your Supabase login and profile, uploaded photos, likes, passes, matches, message requests, conversations, reports by or about your account, notification records, and verified membership records associated with your account.

Apple sign-in authorization is revoked during deletion where applicable. If cleanup is interrupted, the profile is hidden and deletion can be retried. Account-specific drafts and caches on that device are cleared.

Signing out or uninstalling the app does not delete server records. When you delete your Stride account, we also request deletion of the associated RevenueCat customer record. RevenueCat processes this request asynchronously. If cleanup cannot finish, your profile stays hidden and the app lets you retry. Apple subscriptions and transaction records are handled separately. Deleting your account does not cancel an Apple subscription. The current deletion flow does not automatically erase Apple transaction records or all provider-held technical records. Other members may retain copies of information already received. Contact [email protected] for help and applicable residual-data requests.

Deleting the app or your Stride account does not cancel an Apple subscription. Manage subscriptions separately through Apple’s subscription settings.

11. Privacy choices and rights

You can edit profile information and photos, remove optional activity details, change dating preferences and search area, pause discovery, block or report another member, manage available notification settings, delete your account, and manage subscriptions through Apple.

Depending on applicable law, you may have rights to request access, correction, deletion, withdrawal of consent where applicable, or other rights such as restriction, objection, or a portable copy of information. Send requests to [email protected]. Describe the request and the account involved; do not send your password. Identity may need to be verified, and some information may need to be retained for legitimate legal or security reasons.

Revoking an Apple or Google connection is separate from deleting your Stride account. Changing permissions or withdrawing consent may affect features that depend on them.

12. Adults only

Stride is intended for adults aged 18 or older. Age is currently self-reported rather than independently verified for every member. Report suspected underage accounts through the app or email [email protected].

13. This website’s data practices

The website is a static landing page and privacy page hosted on Cloudflare Pages. Visiting it sends ordinary web-request information, such as your IP address, requested URL, browser/device information, and request time, to the hosting and delivery services. Their infrastructure may maintain technical or security logs separately from Stride mobile-app records.

The website loads its typography from Google Fonts. Your browser therefore makes requests to Google’s font servers, exposing request information such as your IP address and browser headers to Google.

The inspected website code does not set cookies or use browser local storage, install advertising pixels or analytics scripts, or collect information through a contact form. Its preview switches and “coming soon” dialog run in your browser without submitting profile or contact information. Hosting infrastructure may process technical information independently of this page code; the absence of page-level analytics is not a claim that no infrastructure logs exist.

Clicking an email link opens your email application. An email is sent only if you choose to send it, and its contents, address, and ordinary email metadata are processed by the email services involved, including Gmail for the operator’s inbox. This policy page does not require signing in, payment, or a file download.

14. Policy changes and contact

We may update this policy as Stride or its practices change. The date at the top identifies the latest update. For material changes, we will provide appropriate notice through the app, website, or another suitable channel as required by applicable law.

Camron Pourhassani
Operator of Stride: Active Dating
[email protected]

Back to top ↑