RideCrew — Effective date: July 31, 2026 · Last updated: 2026-08-10
1. Who we are
RideCrew is a mobile app for tracking speed cameras, recording your own driving trips, and
sharing that activity with friends inside the app. This policy explains what personal data the
app and its backend collect, why, and what control you have over it.
RideCrew is operated by ("we", "us") Ivan Bilousov, a private individual acting as an independent
developer and service provider, located in Ukraine, processing personal data in accordance with
the laws of Ukraine. Operator contact for data matters:
support@ridecrew.online.
For any question about this policy or your data, contact us directly at
support@ridecrew.online — this is a
real, monitored address, not a placeholder.
2. Information we collect
We only collect what the app's own features actually need. Specifically:
Account information
Username and password. Your password is never stored in readable form — only
a one-way cryptographic hash (bcrypt) is kept, so we ourselves cannot see or recover your actual
password.
Birth date (optional). Used only to determine eligibility to use the service
(see Age requirement) and, if you choose to provide it, to unlock one
birthday-themed in-app achievement. We do not use it for any other purpose.
Avatar photo (optional). Stored on our server if you upload one.
Location and driving data
GPS location, including in the background when you've granted "Always"
permission — see the dedicated Background location section below for
exactly why and how this is used.
Trip routes, speed, distance, and duration for every recorded trip.
Motion-classification data (from your device's motion coprocessor) used only
to detect when a drive has actually started or stopped. We do not store raw motion sensor
readings — only the derived yes/no "this looks like driving" signal and its timestamp.
Trip capture diagnostics (only when needed). If the app detects a gap or
anomaly in a recorded route, it may send a small diagnostic record to our server for that one
trip — your device's available memory, thermal state, Low Power Mode status, and the timestamps
of the app moving to/from the background around that trip. This exists purely to help us find
and fix bugs in GPS recording; it is not sent for ordinary trips with no detected problem, and it
is never used to profile your behavior.
We never record audio. RideCrew has no microphone access and no in-cabin audio capture of any kind
— "voice" is never collected, regardless of what's happening in your car.
Social and content data
Your friends list and pending friend requests.
Reactions you leave on friends' trips.
Map "spots" you create (name, description, optional photo, location, and who you tag).
Reports you file against other users' profiles, spots, or trips, and users you block —
see Your rights for what these actually do.
Your cars/garage (make, model, engine, horsepower, tuning info you choose to enter).
Device and technical data
A push-notification device token, used solely to deliver notifications to your device via
Apple's push service.
Standard web-server access logs (IP address, request timestamp) generated automatically by
our infrastructure for security and operational purposes — this is default server behavior, not
something the app specifically collects about you.
Subscription status
We store whether your account is on the free or PRO tier, and where that status came from (a
purchase, a promo code, a referral bonus, or an administrative grant). We never see or
store your payment card details — all payment processing is handled entirely by Apple
through the App Store.
3. How we use this information
To operate the core features you use the app for: recording trips, alerting you to nearby
speed cameras, and running the social features (friends, leaderboard, spots).
To let friends you've added see the parts of your activity your chosen privacy mode allows
(see Who can see your information).
To send you the notifications you've opted into.
To diagnose and fix bugs — including the narrow, trip-scoped diagnostic data described above.
To enforce our Terms of Use, including reviewing reports of abuse and applying blocks.
To provide customer support when you contact us.
We do not use your data to build an advertising profile, and we do not sell it.
4. Legal bases for processing (where applicable, e.g. under GDPR)
Data
Basis
Account credentials, trips, cars, social data
Performance of our contract with you (providing the app's core functionality)
Background location
Your explicit, separately-requested consent (the iOS "Always" location permission), which you can withdraw at any time in Settings
Push notification token
Consent (the notification permission), used only for the notification types you've enabled
Trip capture diagnostics
Our legitimate interest in diagnosing and fixing real bugs in a safety-adjacent feature, limited to the minimum data needed and only sent when a genuine anomaly is detected
Server access logs
Our legitimate interest in operating a secure, reliable service
Birth date
Consent (entirely optional) and our legal obligation to verify the age requirement described below
5. Background location, in detail
RideCrew asks for "Always" (background) location access for exactly two reasons, and nothing
else: automatically starting trip recording without you having to open the app, and warning you
about nearby speed cameras even while the app is in the background or your phone is locked.
When background recording is active, the app periodically checks your motion state and — if it
confidently detects you've started driving — begins recording your route in the background. That
route (a sequence of GPS points, timestamps, and speeds) is stored so it can appear in your trip
history and, per your chosen privacy mode, be visible to your friends.
You can turn this off at any time in the app's own automatic-recording toggle or in
iOS Settings. If you do, RideCrew will no longer be able to start a trip automatically or warn you
about cameras while the app is closed or the screen is locked — you would still be able to record
a trip manually while the app is open in the foreground, and camera warnings would still work while
actively looking at the map. We never use background location for advertising, for tracking you
outside of trip recording, or for any purpose other than the two described above.
6. Who can see your information
Other RideCrew users can see, depending on context:
Your public profile (username, avatar, any earned badges).
Your aggregate leaderboard statistics (total distance, time in transit, and level) — never
your actual routes — visible to every user, regardless of your privacy mode.
Friends only: your live location and in-progress trip, and your trip history,
subject to the privacy mode below.
Map "spots" you create, visible to whoever you explicitly tag.
You control this with three privacy modes, changeable at any time in your profile:
Mode
What friends see
Normal (default)
Live location during an active trip, plus full trip history
Ghost
Trip history only — your live location and in-progress trips are hidden
Full privacy
Nothing — neither live location nor trip history is shown to friends
These restrictions are enforced by our server, not just hidden in the app's interface — a friend's
app cannot retrieve data your privacy mode has hidden, even by inspecting network traffic directly.
7. Third parties & service providers
We do not sell your data, and we do not use third-party advertising or user-behavior
analytics SDKs. The only outside parties involved in operating RideCrew today are:
Apple Inc. — for delivering push notifications (Apple Push Notification
service) and, for any paid subscription, for processing your payment entirely within the App
Store (we never receive your card details).
We may, in the future, integrate a third-party crash-reporting or aggregated technical-
diagnostics tool (the kind of service that reports app crashes and performance issues, not
a service that tracks how you use the app or builds a profile of you). If we do, we will update
this section to name the specific tool before it goes live, and its use will remain limited to
technical stability data — we do not plan to add user-behavior analytics of any kind.
8. Storage, security & retention
Your data is stored both locally on your device and on our own server infrastructure, hosted on
Hetzner Cloud, physically located in Falkenstein, Germany.
Passwords are hashed with bcrypt; your session token is stored server-side only as a
cryptographic hash, never in plain text.
We run an automated nightly database backup, kept for 14 days, stored only on the
server itself with no off-site copy — a deliberate operational choice, not an oversight.
Trips, spots, friends, and other content you create are kept for as long as your account
exists, or until you delete the specific item yourself. An expired "spot" stops being shown to
anyone once its expiry time passes, even if the underlying record hasn't been physically removed
from our database yet.
When you delete your account (see Your rights), all of the data listed
above is permanently and immediately deleted from our server — this is a real deletion, not a
deactivation.
9. Your rights
Depending on where you live, you may have some or all of the following rights over your data:
Access — most of your own data is already visible directly in the app (your
profile, trips, cars, friends, spots). For anything not visible in-app, email us and we'll
provide it.
Deletion — RideCrew has a genuine, self-service account deletion feature,
reachable in Settings → your danger-zone section. It permanently removes your profile, trips,
friendships, spots, and every other record tied to your account from our server, immediately, no
support ticket required. You can also email us to request deletion instead.
Blocking & reporting — you can block another user at any time from their
profile; this makes you mutually invisible to each other across friends, the leaderboard, and
spots, and can be reversed from Settings → Blocked users. You can report a profile, spot, or trip
that violates our Terms of Use directly from the app.
Objection / restriction — you can object to or ask us to restrict a specific
use of your data by emailing us.
Portability — the app does not yet have a self-service data-export button;
email us and we will provide a copy of your data in a common format.
Withdrawing consent — you can revoke location or notification permissions at
any time in iOS Settings, and disable automatic trip recording in the app itself.
To exercise any right not already self-service in the app, email
support@ridecrew.online. We will respond within a
reasonable time and, where applicable, within the timeframe required by law.
10. Age requirement
RideCrew is intended for users aged 16 and older. Registration requires you to confirm you meet
this age requirement, and if you choose to provide a birth date, we check it directly. This
confirmation is self-declared by the user — like most consumer apps, we have no independent way to
verify a person's real age — so it should be understood as an eligibility requirement we enforce in
good faith, not a guarantee that every account belongs to someone 16 or older.
We do not knowingly collect personal data from anyone under 16. If we become aware that we have
done so, we will delete that account and its data. If you believe a user under 16 is using
RideCrew, please contact us at the address above.
11. Cookies & analytics
RideCrew is a native mobile app, not a website — it does not use browser cookies. We do not use
any third-party user-behavior analytics or advertising-tracking tool. See
Third parties & service providers above for our narrow, honestly-
scoped plans around future crash-reporting/technical-diagnostics tooling, which is not behavioral
analytics.
12. International transfers
Our servers are located in Germany (European Union). If you use RideCrew from outside the EU/EEA,
your data will be transferred to and processed in the EU. If you use RideCrew from within the
EU/EEA, your data generally stays within the EU on our infrastructure.
13. Changes to this policy
We may update this policy as the app changes — for example, when we add a new feature that
collects a new kind of data, or when we integrate a new service provider. We will update the "Last
updated" date above when we do, and for material changes we will make a reasonable effort to notify
you in-app.