Privacy Policy

Quorvia Trade is a business-to-business quoting, ordering, and scheduling portal used by window-treatment retailers, dealers, and their staff. This policy explains what we collect, why, and what we never do with it.

What we collect

• Account data — the name, email address, and role of each person invited into a company account, so we can tell them apart and show them their own work.
• Business records — quotes, orders, purchase orders, appointments, and the customer contact details a retailer enters in order to serve their own customers.
• Google user data — only if a person explicitly connects their Google Calendar. See below.

Google user data

Connecting a Google Calendar is optional, per person, and reversible. When someone connects one, we ask Google for permission to manage calendar events (calendar.events) and to read the email address of the account being connected, so the person can confirm which calendar they linked.

• What we do with it. When a visit is booked, rescheduled, or cancelled on that person’s schedule in Quorvia Trade, we create, update, or delete the matching event in their Google Calendar. To avoid double-booking, we also read the start and end times of the other events on that calendar, so the schedule can show when the person is already busy. These are the only purposes of the connection.
• What we store. The Google refresh token, the connected account’s email address, and the id of each event we created, so we can update the right one later. Tokens are stored server-side and are never sent to a browser.
• What we never do. From the other events on a connected calendar we use only their start and end times, held in memory to show busy time; we do not store, display, index or analyse their titles, descriptions, attendees or locations. We do not sell Google user data, transfer it to advertisers or data brokers, or use it to develop, improve or train generalized AI or machine-learning models. We do not use it for advertising of any kind.
• Limited Use. Quorvia Trade’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• How to disconnect. Use Disconnect in the Calendars panel on the Schedule screen: we delete the stored token immediately and stop writing to that calendar. You can also revoke our access at any time from your Google Account permissions. Events already written to a calendar belong to that calendar; delete them there if you want them gone.

QuickBooks Online (Intuit)

If your organization connects QuickBooks Online, Quorvia Trade uses Intuit's authorization flow (OAuth 2.0). You sign in to Intuit, choose the company, and approve access; we never see or store your Intuit password. We request only the QuickBooks Online Accounting scope.

• What we do. We send your quotes as Estimates and your orders and invoices as Invoices, and the payments and refunds recorded against them, to your QuickBooks company. To do this we create or match Customers and read your Chart of Accounts, items, tax codes, classes, terms, payment methods, company information and preferences so documents are mapped correctly.
• What we store. The connection (your QuickBooks company ID), the OAuth tokens, encrypted at rest, and the identifiers and sync status linking each of your records to its QuickBooks document. We keep only what the sync needs; QuickBooks remains the system of record for the documents it holds.
• What we never do. We do not sell QuickBooks data, share it with advertisers or data brokers, or use it for any purpose other than the sync you set up. Only the people in your organization with permission to manage integrations can connect, change or disconnect QuickBooks.
• Disconnecting. You can disconnect at any time in Settings › Integrations › QuickBooks, or revoke access in your Intuit account. Disconnecting revokes our tokens at Intuit and deletes them from our systems; documents already in QuickBooks stay there, and the links to them are kept so that reconnecting the same company resumes without creating duplicates. To have those links removed too, contact us.

Who can see what

Each company account is isolated. Staff see only their own company’s records, and only the parts their role permits. We access customer data ourselves only when it is necessary to operate the service or to resolve a support request an account has raised with us.

How we protect your data

Data is encrypted in transit with HTTPS/TLS and encrypted at rest by our database host. Each company’s records are separated by database row-level security, and staff access is limited by role. Google OAuth tokens (including the refresh token for Google Calendar) are kept in a server-only table that browsers cannot read; they are never sent to a browser, our application never writes them to logs or error reports, and they are deleted when a calendar is disconnected. Access to the production systems and their credentials is limited to the authorized personnel who need it to run the service. If we learn of unauthorized access to personal data, we will notify the affected accounts.

Service providers

We run on infrastructure operated by our hosting and database providers, and use Google APIs for the calendar feature described above. We do not share data with anyone else except where the law requires it.

Voice recordings you add to feedback, and recordings you use to look up a product by voice, are sent to Google (Gemini API) to be turned into text. To write a summary of a long voice note, or a shorter version of a reply, the text is also sent to Google. Recordings added to feedback are deleted 60 days after your feedback is closed; the text stays.

When you type an address into a form (a new contact, a contact's address, the online booking page), once you have typed three characters the text is sent to Google (Maps Places API) to suggest matching addresses, and "Check address" sends the whole address. Google returns the suggestions and, for the one you pick, its position; we keep the address you save and that position, and nothing else from the lookup.

Mobile app

The Quorvia Trade app for iPhone and Android uses the same account and the same records as the web portal. It collects nothing beyond what you enter: your sign-in email and name, and the customers, jobs, visits, estimates, payments and orders you record. The app contains no advertising or tracking SDKs, does not track you across other companies’ apps or websites, and does not access your location, contacts, camera or photos.

Deleting your account

You can delete your account at any time: in the app, open Account → Delete account and confirm with your password; without the app, follow the steps on our account deletion page or email us. Deleting closes your sign-in permanently and removes your name, email address and phone number from your profile. Quotes, orders, invoices, payments and messages you took part in are kept as the business records of the companies involved, without your personal details. Details: Delete your account.

Retention and deletion

Business records are kept for as long as the account is active, because quotes and orders are the account’s own commercial history. Google tokens are deleted the moment a calendar is disconnected. To have an account and its data deleted, email rui.wang@theblindbots.com.

Changes

If this policy changes in a way that affects how Google user data is handled, we will update the date at the top of this page before the change takes effect.