Ortix Aislo Privacy Policy

• About users (the people who sign in): we decide how it is used, as this policy describes.
• About a shop's customers (names, phone numbers, vehicles, repair history): the shop decides how it is used, and we hold and process it for the shop under our data processing addendum. If you are a customer of a shop, the shop's own privacy notice applies, and the shop is the one to ask about your information.

Users can see and change their own details in the app, and a shop can export all of its data at any time in Settings › Data import and export. Wherever you live in the United States, you can ask us to tell you what personal information we hold about you, give you a copy, correct it or delete it. We do not sell or share personal information for targeted advertising, so there is nothing to opt out of. We will not treat you differently for using these rights.

• How to ask: use our contact form, with the email address on your account, or say which shop you are a customer of. We may ask for details to confirm who you are. An authorized agent can ask for you with your signed permission.
• When: we answer within 30 days, and in no case later than your state's law allows (45 days in most states).
• Shop customers: information a shop holds about you is the shop's. We pass your request to the shop and help it answer.
• Appeals: if we turn down a request, reply to our answer to appeal. If you are still unhappy, you can contact your state's attorney general.

• Account information: names, email addresses, phone numbers and roles of the people who use a shop's account, and sign-in records (time, device, IP address).
• Billing information: the shop's plan, usage and invoices. Card and bank details are handled by Stripe; we do not store card or bank account numbers.
• Phone app: a push notification token for the device, and the photos and scans a user takes in the app. The app keeps a copy of the shop's work on the phone so it works without a connection, and deletes it when the user signs out. It does not track location and contains no advertising or analytics code.
• Technical information: a sign-in cookie that keeps you signed in, and logs of requests and errors that we use to keep the service working and secure. We do not use advertising or tracking cookies.
• Support: what you tell us when you email or message us for help.

• Shop data: what a shop enters or imports: its customers and their contact details, vehicles and VINs, repair orders, estimates, inspections and photos, invoices, payments, parts, schedules, time records, messages and settings. We hold this for the shop and use it only to run Ortix Aislo for that shop.
• Customer actions on shop pages: when a customer approves an estimate, pays an invoice or books online from a link the shop sent, we record what they did, when, and from which IP address, so the shop has a record of the approval.
• Texting records: whether each customer agreed to texts, replies, STOP and HELP requests, and delivery reports from the carriers.

To provide Ortix Aislo: show and store the shop's records, send the texts and emails the shop sends to its customers, send notifications to users, take payments, sync to the accounting system the shop connects, give support, keep the service secure, prevent abuse, and meet legal duties. We email account owners about their account, billing, security and changes to our terms. We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not use it for advertising of any kind.

Only service providers that run parts of Ortix Aislo for us, under contract and only for that purpose: hosting and database (Render), network, file storage and bot protection (Cloudflare), payments and billing (Stripe), text messages and carrier registration (Telnyx), our own email (Google Workspace), and push notifications (Apple). The full list, with what each one handles and where, is on the subprocessors page.

When a shop connects another service, such as QuickBooks Online (Intuit), its own Gmail, or a parts supplier, we send that service the data the connection needs, at the shop's request. When a VIN is decoded, the VIN alone is sent to the US government's public vehicle database (NHTSA). We may disclose information when the law requires it, to protect people from harm, or as part of a sale or merger of our business, in which case this policy keeps applying to it.

A shop can connect its Gmail or Google Workspace mailbox in Settings › Email so that the emails it sends to its customers through Ortix Aislo come from its own address. This section describes the information we receive from Google when it does.

• What we access: the connected Google account's email address and Google account ID (from the openid and email scopes), and permission to send email as that address (the gmail.send scope), held as OAuth access and refresh tokens. We do not ask for, and cannot get, permission to read, search, label, change or delete anything in the mailbox, or to see its contacts or calendar.
• How we use it: only to send the emails that the shop and its staff send to the shop's own customers from Ortix Aislo (estimates, approval requests, invoices, receipts, statements, reminders, review requests, offers and messages they write), through Gmail, so they appear in the shop's Sent folder; to send a test email when the shop asks for one; and to show the shop which address is connected. Each email is one the shop chose to send or set up to be sent.
• What we do not do: we do not read the mailbox, use Google user data for advertising, sell it, or use it to build, train or improve artificial intelligence or machine-learning models. No person at Ortix Group reads it, except with the shop's permission for a specific support request, for security (for example, investigating abuse), or where the law requires it.
• Sharing: we do not transfer Google user data to anyone, except to the hosting providers in who we share it with that store it for us, or where the law requires it.
• Storage and protection: tokens are encrypted at rest (AES-256-GCM, with a separate key for each connection) and are only decrypted to send an email. Access to production systems is limited and audited; every connect and disconnect is recorded in the shop's audit log.
• Retention and deletion: we keep the tokens only while the mailbox is connected. When the shop clicks Disconnect, we revoke our access at Google and delete the tokens straight away. The emails a shop sent stay in its Ortix Aislo message history as part of its records, like any message it sends. A shop or the Google account owner can also remove our access at any time at myaccount.google.com/permissions; we then stop sending from that address. To have the connected address and account ID deleted too, ask through our contact form.

Ortix Aislo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• Shop data and account information: while the shop subscribes. After a shop cancels, its account stays export-only so it can take its data with it, until the shop asks us to delete it. If a shop stops paying, its data is deleted 120 days after the first failed payment, as the terms of service describe, and can be restored for 30 days after that.
• Backups: encrypted nightly backups are kept for 90 days, and one backup a month is kept for 7 years because shops' invoices and payments are accounting records. Backups are not used for anything except restoring data, and data deleted from Ortix Aislo leaves the backups as they expire.
• Logs: request and error logs are kept for no more than 30 days. Each shop's audit log is kept as long as the shop's data.
• Billing records: invoices and payments for a shop's subscription are kept for as long as tax law requires.
• Phone app: the copy on a phone is deleted when the user signs out.

Data is encrypted in transit (HTTPS) and at rest. Each shop's data is kept separate in the database, and every request is checked against the user's permissions on our servers. Secrets such as connection tokens are encrypted with their own keys. Backups are encrypted with a key held by Ortix Group. Two-step sign-in is available to every user, and changes to a shop's settings and records are written to an audit log that cannot be edited. Ortix Aislo is run from the United States, and information is stored there.

Ortix Aislo is a business tool and is not meant for children under 16. We do not knowingly collect their information.

We post every change here with a new version and date, listed under versions and changes, and email shop owners at least 30 days before a material change takes effect.

Ortix Group LLC · Contact form

• 2026-10-30Moved to /legal/privacy. Added the subprocessors by name, retention periods, backups and US state privacy rights.
• 2026-10-29First published version, with the Google user data section for Connect Gmail.

Questions: use our contact form.