Privacy Policy

Effective October 1, 2026 · Updated October 4, 2026 · SPRANDEL LLC ("RO Engine", "we")

RO Engine is shop-management software for independent auto repair shops. This policy covers information about the people we deal with directly: visitors to roengine.com, people who ask us for a demo, and shop owners and staff who sign up for and use RO Engine.

Your shop's customer data isn't covered here. The customers, vehicles, repair orders, messages and calls a shop keeps in RO Engine belong to that shop, and we process them only on the shop's behalf under our agreement with it. If you're a customer of a shop that uses RO Engine, that shop's privacy policy applies. Contact the shop, and we'll help them with your request.

1. What we collect

When you visit roengine.com or the signup page

Analytics. Google Analytics sets cookies (_ga, _ga_*) and records the pages you view, how you arrived, your approximate location (from your IP address), and your device and browser.
Ad and campaign tags. If you arrive from an ad or a tagged link, we store the tags in a first-party cookie named re_attr for 90 days: Google's click IDs (gclid, gbraid, wbraid), campaign tags (utm_source, utm_medium, utm_campaign) and when we saw them.
Meta Pixel. Meta (Facebook and Instagram) sets cookies (_fbp, and _fbc when you arrive from one of our Meta ads) and receives the pages you view, when you click "Set up my shop", and when you send the question form — not what you type in it — along with your IP address and browser.

When you ask for a demo

Your name, shop name, email, phone, number of bays, current software and anything you write in the form, plus your IP address, browser and the page you came from.

When you sign up

Your name and email, your shop's name, web address, phone, city and state, and the optional answers you give (current software, how you heard about us, bays, technicians). If the re_attr cookie is present, we save its tags with your signup. Payment details go directly to Stripe, which processes them for us; we never see or store your full card or bank account number. To keep automated signups out, the signup form runs Cloudflare Turnstile, which checks your browser (including your IP address) for signs of a bot.

When your shop uses RO Engine

Account details for each staff login (name, email, role), sign-in and activity records needed for security and support, usage counts for billing and fair-use limits, and the messages you send us.

Product analytics. To learn how shops use RO Engine and where it's confusing, we record which pages staff open and which actions they take (for example "created a repair order", without its contents), and we use PostHog to record clicks and session replays of the staff screens. Replays mask everything typed and all text on the page, so they show layout and clicks, not your customers' names, phone numbers, vehicles or prices. Nothing is recorded on the pages your customers see (estimates, online booking).

Support access. To help you, RO Engine support can sign in to your shop for up to one hour at a time, without your password. Each sign-in is started by a named RO Engine staff member, recorded in our audit log, and listed for you in Settings → Users, where an Owner can turn support access off at any time (it's on by default).

2. How we use it

To run the website, the trial and the service, bill you, and support you.
To answer demo requests and send the emails you'd expect: trial reminders, receipts, service notices.
To understand which pages and campaigns bring shops to us, including telling Google Ads that an ad click led to a trial or a paid subscription so the ad is credited. We send the click ID and the conversion, not your name or email.
To measure our Meta ads and help Meta show them to people likely to be interested, using the Meta Pixel events described above.
To improve RO Engine, using the product analytics described above.
To keep the service secure, prevent abuse, and meet legal and tax obligations.

We don't sell your personal information or use it to train AI models. The Meta Pixel does share website activity with Meta for advertising, which some state laws call "sharing" for cross-context behavioral advertising; see section 4 to opt out.

3. Who we share it with

Only the service providers we use to run RO Engine, each bound to protect it:

Provider	What for
Google	Website analytics and ad measurement (Google Analytics, Google Ads); AI features
Meta	Ad measurement and delivery for our Facebook and Instagram ads (Meta Pixel)
PostHog	Product analytics and masked session replays of staff screens in the service
Stripe	Payments and subscriptions
Cloudflare	The bot check on the signup form (Turnstile)
Mailgun	Sending email
HostGator	Hosting roengine.com and the demo form
Telnyx, Retell, Anthropic	Phone, texting and AI features inside the service
Hosting and encrypted backup providers	Running and backing up the service

We'll also disclose information if the law requires it, to protect our rights or someone's safety, or to a buyer of the business, who will be bound by this policy. We'll keep this list current.

4. Cookies and your choices

Google Analytics: you can block it with your browser's cookie settings or Google's opt-out add-on. How Google uses the data: policies.google.com/technologies/partner-sites.
Meta Pixel: you can block it with your browser's cookie or tracking settings, and control how Meta uses activity from other websites in your Facebook or Instagram settings under Ad preferences → Activity information from ad partners. How Meta uses the data: facebook.com/privacy/policy.
re_attr: first-party, expires after 90 days, and is only read when you sign up. Clearing cookies for roengine.com removes it.
Blocking these cookies doesn't affect the website or signup.

5. How long we keep it

Account and billing records: while your shop subscribes, then until your data is deleted when the account ends, except billing and tax records we must keep by law.
Demo requests that don't become customers: 24 months. The IP address, browser and referring page stored with them: 90 days.
Analytics: Google Analytics keeps event-level data for 2 months. In-app usage records: 12 months. PostHog session replays: 30 days.

6. Security

Each shop has its own database; traffic is encrypted in transit; backups are encrypted; staff access is limited to what's needed. No system is perfectly secure. If a breach affects your personal information, we'll notify you as the law requires.

7. Your rights

You can ask to see, correct or delete the personal information we hold about you, or to stop receiving marketing email, by writing to privacy@roengine.com. We'll verify the request comes from you and answer within 30 days. Depending on where you live, you may have further rights; we won't treat you differently for using them.

8. Children

RO Engine is a business service. It isn't directed to children under 16, and we don't knowingly collect their information.

9. Changes

If we change this policy in a way that matters, we'll update the date above and, for current customers, email the account owner before the change takes effect.

10. Contact

SPRANDEL LLC · 432 N Main Ave, Fayetteville, AR 72701 · privacy@roengine.com