Privacy Policy
This policy explains what RME collects, why we use it, and the choices available to you.
1. Scope
This Privacy Policy applies to the RME website, release-update list, mobile applications, and related services (collectively, the “Services”). Features described here may change as the Services develop.
2. Information we collect
Information you provide
- Release-list and account contact details such as your name, email address, optional phone number, selected device platform, release interest, and communication preferences.
- Account and profile information, including display name, username, biography, profile photos, vehicle information, interests, and birth date when required for eligibility.
- Contact or address information you choose to provide for an account, creator, marketplace, billing, legal, or support purpose, which may include other contact details or a physical or mailing address.
- Content and communications, including photos, videos, audio contained in submitted media, posts, reviews, listings, reports, support requests, and in-app messages.
- Optional location or place information you choose to add to a post, profile, review, event, or listing.
- Purchase history, subscription, entitlement, and account-linking information, such as the Ember pack or Premium plan selected, transaction amount, currency, tax, payment and renewal status, benefit period, provider customer and transaction references, creator-code attribution, friend-referral attribution and verified setup completion, earned Premium months and pending provider fulfillment, and refund or dispute status. Other financial records may include creator earnings, payout eligibility, or related account status. RME does not receive your full card number from Stripe.
RME supports optional Ember purchases and paid Premium. Purchase-history records cover provider-verified purchases, subscription and renewal state, earned or promotional Ember activity, permanent unlocks, complimentary Premium access records, and records needed to restore, refund, or resolve a provider transaction. Billing providers process payment credentials; RME uses verified transaction records to provide the matching value or access.
Referral phone verification: If you choose to qualify for referral rewards, we use your phone number and verification result to confirm control of that number and prevent duplicate rewards. Supabase and our SMS verification provider, Twilio, process the number and verification messages for this purpose. Your phone number is not displayed on your profile or shared with the person who referred you. This verification is separate from normal sign-in and is not an identity or age-document check.
Signing in with Google or Apple
If you choose to create or sign in to your account with Google or Apple, that provider shares a limited set of information with RME after you approve it: your name, your email address, and, for Google, your profile photo. Apple may give us a private relay email address instead of your real one if you choose "Hide My Email." Apple may share your name only the first time you sign in.
We use this information only to create your account, sign you in, contact you about your account, and suggest a display name you can change at any time. Your Google profile photo is kept with your sign-in record but is not shown on your RME profile unless you add a photo yourself. We do not receive your Google or Apple password, and we do not request access to your contacts, calendar, files, or any other Google or Apple account data. Our authentication provider, Supabase, processes this sign-in on our behalf. If you delete your RME account, we also ask Apple to revoke RME's access where Apple supports it. You can remove RME's access at any time in your Google Account or Apple ID settings.
Information collected automatically
When you use the Services, we may receive your RME user identifier, device identifiers, device and browser information, IP address, timestamps, product interactions, search queries or search history, diagnostic events, other technical or security data, security logs, and approximate location inferred from network information. The website may temporarily process IP addresses to prevent abuse of sign-in and other website features.
Cookies and similar technologies
RME members sign in and make purchases only in the RME apps for iPhone and Android. The website does not currently offer member sign-in or purchases. It uses only cookies that are needed to provide the features you request, and we do not use advertising or cross-site tracking cookies. The sign-in and payment cookies below apply only if website sign-in or purchases are offered again.
- Sign-in session cookies. When you sign in to the website's Ember shop, our authentication provider, Supabase, sets session cookies whose names begin with
sb-. They keep you signed in, are not readable by page scripts, and are removed when you sign out or the session ends. - Sign-in link cookie. When you request an email sign-in link, the website sets a
rme_magic_link_statecookie that expires within 10 minutes. It is sent only to the sign-in confirmation address and confirms that the link is completed in the browser that requested it. - Security check. Signing in, creating an account, and resetting a password in the RME apps (and on the website, if website sign-in is offered) use Cloudflare Turnstile to distinguish people from automated abuse. Cloudflare may process browser and device signals for that check under its own privacy terms.
- Payment pages. Stripe-hosted checkout and billing pages are operated by Stripe and may use their own cookies under Stripe's privacy terms.
You can block or delete cookies in your browser settings, but website sign-in and purchases will not work without the cookies described above.
Invite-link analytics
When someone opens a personal or creator invite link on the website, we record that the link was opened so we can measure referral activity. To count each visitor at most once per day without storing an IP address, the website combines the visitor's IP address, the referral code, and the current UTC date and stores only a keyed, one-way hash of those values together with the referral code. The hash cannot be linked across different codes or days, and the IP address itself is not stored. We associate these open counts with the account that owns the referral code for internal referral, fraud-prevention, and product analytics. Opening an invite link does not create an account, record a referral, or earn a reward.
Location information
If you enable location features in the app, RME may process precise or approximate device location to show nearby places or people. You can control location permission through your device and in-app privacy settings. Avoid sharing a precise overnight location publicly when doing so could put you or others at risk.
Trailprint: Recording starts only when you choose to start it and grant the required location permission. RME records precise GPS points, timestamps, and accuracy to save your route and calculate Trailprint distance, area, and streaks. On supported mobile devices, recording may continue while RME is in the background or your phone is locked until you tap Stop revealing. Routes are private by default. You can choose who can see a privacy-filtered shared view through the visibility controls. Sharing limits the detail visible to other members; it does not reduce the precision of your own stored history. Stopping recording ends new location collection but does not erase saved history. You can export or permanently delete that history in the app and revoke location permission in your device settings.
3. How we use information
- Provide, maintain, personalize, and improve the Services.
- Operate the waitlist, beta program, account system, maps, social features, messaging, and marketplace.
- Send launch notices and, where you opt in, occasional product or community updates.
- Detect spam, fraud, unsafe behavior, policy violations, and technical problems.
- Respond to support requests and enforce our Terms and Safety Guidelines.
- Comply with legal obligations and protect users, RME, and the public.
4. How we share information
We may share information with service providers that host or support the Services, such as cloud hosting, database, analytics, security, communication, and artificial-intelligence (AI) image-generation vendors. We may also disclose information when required by law, to protect safety or rights, in connection with a business transaction, or when you direct us to share it. Public profile, post, listing, review, and event information can be visible to other users according to your settings and the feature used.
AI-generated images: When you ask RME to create an AI-generated image, such as an icon for your rig or vehicle, the photo or image you choose and your related instructions are sent to an AI image-generation service provider, which processes them to create the requested image on our behalf. This happens only when you request a generated image.
When you choose a paid service through Stripe, Apple, or Google, that provider may collect payment, billing-address, device, and fraud-prevention information under its own privacy terms. RME may receive provider references and verified lifecycle events needed to service or resolve the correct account record; we do not locate a Stripe billing account by email alone.
RME 1.0 mobile apps do not expose an Android external-link purchase path and do not send a Play reporting token to this website. RME does not place a Play reporting token in a website URL or browser storage.
RME does not sell personal information. We do not share personal information for cross-context behavioral advertising.
5. Retention and security
We retain information for as long as reasonably needed to provide the Services, meet legal obligations, resolve disputes, and prevent abuse. Retention periods vary by data type. We use administrative, technical, and organizational safeguards, but no online service can guarantee absolute security.
After an account is deleted, we may retain a limited, access-controlled hashed identity and reward history where necessary to prevent repeated signup or referral rewards. This record is used for fraud prevention, not public profiling or marketing. A hash remains protected account-related information; contact privacy support about applicable access, deletion, or retention questions.
6. Your choices and rights
You may unsubscribe from optional updates, adjust device permissions, change available profile and location settings, or request access, correction, deletion, or a copy of your personal information. Some records may be retained when required for security, fraud prevention, or legal compliance.
Residents of certain U.S. states may have additional rights to know, correct, delete, or obtain a portable copy of personal information and to appeal a denied request. We will not discriminate against you for exercising applicable privacy rights.
7. Age eligibility
Normal RME account eligibility and normal account-based Services are limited to people who are at least 18 years old. The Services are not directed to children, and RME does not knowingly permit a person under 18 to maintain normal account access.
RME may collect a birth date to determine account eligibility and enforce the adult-only rule. If RME determines that an account holder is under 18, normal product access will be disabled while limited privacy, support, data-export, sign-out, and account-deletion controls remain available. If you believe a person under 18 has provided personal information to RME, use the in-app reporting control where available or contact RME through an approved support channel without sending passwords, identification documents, suspected illegal material, or other unnecessary sensitive information.
RME's adult-only eligibility rule does not reduce its child-safety obligations. The separate Child Safety Standards continue to prohibit child sexual abuse and exploitation and child sexual abuse material across every RME service and account.
8. International use
RME is operated from the United States. If you access the Services elsewhere, your information may be processed in the United States or other countries where our providers operate.
9. Changes to this policy
We may update this policy as the Services develop. We will change the effective date above and provide additional notice or request renewed consent when required. If renewed consent is required and is not provided, normal product access may remain unavailable while approved privacy, support, data-export, sign-out, and account-deletion controls remain accessible.
10. Contact us
For privacy questions or requests, email privacy@roammeetexplore.com. Please do not send passwords, government identification, or other sensitive information by email unless we specifically request it through a secure method.