Privacy Policy
Curblane ("Curblane," "we," "us") is a fleet-management dashboard for Turo hosts. This policy explains what we collect, why, and your choices. Curblane is an independent product and is not affiliated with, endorsed by, or sponsored by Turo Inc.
What we collect
- Account data: your email address (for login via magic-link) and basic account settings.
- Fleet data you enter or import: the business records you add to run your fleet. Vehicles (including VINs and license plates you choose to enter), bookings, guests' first names and trip details, tolls, expenses, parking, loans, payouts, reimbursements, and maintenance logs. You can type these in or import them from Turo files (trip/earnings CSVs, receipts, emails) and toll/parking statements. This is your business data; you own it.
- Files you import yourself are parsed in your browser and discarded: when you import a CSV, a receipt, or an email file yourself, the raw file is parsed on your device and only the structured records are kept. The original file (and any payment fragments or third-party identifiers it contains) is discarded right after parsing. It is not uploaded or stored. We keep guests' first names only, never full names or driver-license IDs. Email forwarding is the exception, and only if you turn it on. That path is described below. Until that option is shown in your account, we do not receive your Turo mail.
- Email forwarding (optional): if you turn it on, a filter in your email account sends Turo trip notifications to a private Curblane address. Our servers receive those messages. What arrives, what we keep, how long we keep it, and how you turn it off are in Email forwarding below.
- Payment data: if you subscribe, billing is handled by Stripe. Curblane never sees or stores your full card number. Stripe processes it. We store only your plan status and a Stripe customer/subscription identifier.
- Usage analytics: if we use product analytics (e.g., PostHog), we collect only behavioral events (which features you open, when you upgrade) and coarse properties (plan, approximate fleet-size bucket, and, if you arrived from one of our campaign links, which link introduced you) to improve the product. We never send your fleet financial values or identifiers (dollar amounts, VINs, plates) to analytics.
- Local storage / cookies: the app stores data in your browser (
localStorage) so it works offline and loads fast; essential cookies keep you signed in. Analytics may set cookies subject to your consent where required. If you arrive from one of our campaign links, the landing and sign-in pages keep that link's campaign tags (source, medium, campaign, content, term. Never the page you came from, the full address, or anything about you) in your browser for up to 30 days, so that if you create an account we can record which post introduced you. They are removed when you sign up, when they expire, or when you delete your account, and nothing is kept at all if your browser sends the Global Privacy Control signal.
The landing page and the sign-in page may record anonymized session replays through PostHog. Everything you type is masked, and text that shows an email address is masked too. The app itself is not recorded. If your browser sends the Global Privacy Control signal, we do not record.
How we use it
To provide and sync the dashboard across your devices, authenticate you, process subscriptions, provide support, keep the service secure, and improve the product. We do not sell your personal information, and we do not use your fleet data to advertise to you.
Legal bases (GDPR, where applicable)
Performance of our contract with you (providing the service); our legitimate interest in securing and improving the product; your consent (e.g., non-essential analytics cookies); and compliance with law.
Who we share it with (subprocessors)
We share data only with vendors that run the service, under their own terms:
- Supabase. Database + authentication (your account and fleet data, isolated per-account; sends the login-link emails).
- Stripe. Subscription billing and card processing.
- Netlify. Application hosting.
- PostHog. Product analytics (behavioral events only).
- Cloudflare, optional email forwarding only. If you turn forwarding on, Cloudflare receives each forwarded message and runs our in-memory parse. We do not use Cloudflare as a mailbox or an archive, and Cloudflare does not hold your fleet for any other feature.
If we add a vendor (e.g., an email newsletter provider), we'll update this list. We may disclose information if required by law, or to protect rights, safety, and the integrity of the service. We do not sell data or share it with advertisers.
Data isolation & security
Each host's data is isolated at the database level using row-level security, so one account cannot access another's records. Photos you upload for a vehicle are stored in a private bucket: only your account can read or change them, and the app shows them through a short-lived link rather than a public web address. Data is encrypted in transit (HTTPS/TLS). No system is perfectly secure, but we work to protect your information and limit access to what's needed to run the service.
Email forwarding (optional)
Email forwarding is off unless you turn it on. The control appears in your account only after we enable it. Until you see it, we do not receive your Turo mail. This section is what happens if you turn it on.
What you do. Account → Connect by email forwarding gives you one private address,
import+curb-… plus a secret shown once, at in.curblane.app. You add that address in Gmail and create one filter so new messages
from noreply@mail.turo.com forward themselves. An email you forward by hand is discarded: it no
longer comes from Turo, so we do not import it. We do not ask for access to your mailbox. Toll, parking, and
loan mail are not part of this.
What we receive. Each Turo trip notification that filter sends, and, once, Gmail's own confirmation
message (from forwarding-noreply@google.com) so the filter can be switched on. A message that is
too large to be one trip email is discarded without being parsed.
Where it is processed. Cloudflare receives the message and hands it to our email worker, which also
runs on Cloudflare. The worker holds the message in memory only. It checks three things before it keeps
anything: the envelope address is your private address (not an address typed in the message), Cloudflare's own
authentication result shows a DKIM pass for Turo (or for Google, on that one confirmation), and the From
address is Turo's mail.turo.com (or Google's confirmation sender). It then reads the message with
the same parser as a file you drop in, keeps only the trip fields below, and sends those fields to our app on
Netlify. Netlify saves them in your account in our database (Supabase), the same place as trips you import
yourself. The message is not written to Netlify or to the database.
What we keep. Reservation ID, trip start and end, earnings, which of your vehicles (Turo's id for that listing, not a VIN or a plate), the pickup or delivery location the email states, and the guest's first name. A cancellation is stored as cancelled. The server checks the list again and drops anything else.
What we do not keep. The email itself, including its body and any attachments. The guest's phone number, surname, and Turo profile id, link, or photo. The text of a message the guest sent you. Those emails import nothing. Plates and VINs, if they appear in the message, are discarded with it. We do not log the message, the guest's name, phone number, or surname, or a plate or VIN. Logs are counts (how many trips were added or updated) and error codes.
The address. We store the curb-… part of your address so we know the mail is yours, and
a hash of the secret half, not the secret itself, plus the time a forward last arrived. That id
is not your password. The full address is shown once, when it is created. An address you already use,
from before that secret half, keeps working until you regenerate it. Keep the address private anyway:
someone who has the full address and can send mail that passes the Turo checks could add trips to your
bookings. Regenerating the address turns the old one off immediately and issues a new secret. There is one
active address per account.
How long we keep it. The trip fields stay with your fleet data while your account is open, including the restore points (snapshots) described below. The original email is not in those snapshots. The worker drops it when it finishes, and we do not keep a copy. Your forwarding address stays on the account until you turn forwarding off or delete the account. Turning it off marks the address off immediately, so it cannot import again, and that off switch stays until the account is deleted.
How to turn it off. In the app: Account → Connect by email forwarding → Turn off forwarding. Also delete the Gmail filter, and remove the address under Gmail → Settings → Forwarding, so Gmail stops sending. You can do that and keep the account. Trip details already imported stay until you delete those trips or delete the account. Account → Delete account erases the fleet data, the snapshots, the guest first names in them, and the forwarding address, immediately. Or email hello@curblane.app from your account address and we will erase it within 30 days.
Gmail's confirmation. To verify the address, our worker opens only the confirmation link on
mail.google.com or mail-settings.google.com, and only the link that confirms
forwarding. It follows a redirect only when the next page is still that confirmation link, then submits
the confirm form. It does not follow a redirect away from that link, and it does not store the confirmation
email.
Data retention & deletion
- We keep your data while your account is open.
- On downgrade or cancellation, we retain your data (your account persists; cars beyond the free limit become read-only) so you can resume anytime.
- To delete your account, you can do it yourself in Account → Delete account: this
permanently erases your account and all of its data. Your fleet records, restore points (snapshots),
any photos you uploaded, and any email-forwarding address, and cancels any active subscription,
immediately and irreversibly.
A full backup downloads first, and you confirm by typing
DELETE. Prefer we handle it for you? Email hello@curblane.app from your account address and we’ll erase your data within 30 days. Either way, you can export your full data at any time from within the app before deleting.
Your rights
Depending on where you live (e.g., GDPR/EEA, UK, California/CCPA), you may have the right to access, export/port, correct, or delete your data, and to object to or restrict certain processing. You can export your full data from within the app at any time. To exercise other rights, email hello@curblane.app; we'll respond within the timeframe the law requires. We won't discriminate against you for exercising these rights.
International users
Curblane is operated in the United States; if you use it from elsewhere, your data is processed in the US and other countries where our subprocessors operate.
Children
Curblane is a business tool for adults and is not directed to anyone under 18. We don't knowingly collect data from children.
Changes
We may update this policy; we'll post the new effective date here and, for material changes, notify you by email.
Contact
Questions or requests: hello@curblane.app.