Privacy Policy

Last updated: July 15, 2026

Data We Collect

We collect account details, business workspace details, business profile and document settings, integration connection status, imported source records, native Sales Docs records, customer records, recovery opportunities, prevention rules, email delivery metadata, activity history, cookie preferences, diagnostics, and billing status.

QuickBooks Data

When a user connects QuickBooks, the app requests accounting access so it can read customers, invoices, estimates, payments, credit memos, balances, dates, purchase order fields, and related metadata. The app does not write invoices, estimates, payments, customers, or other accounting records back to QuickBooks.

Stripe Data

When a user connects Stripe, the app reads payment-source records such as customers, payment intents, charges, invoices, quotes, refunds, disputes, balances, dates, and related metadata so it can detect payment recovery opportunities. For native invoice payments, Stripe processes payment details. The app stores payment session, invoice, amount, and status metadata, but it does not store full card numbers.

Sales Docs Data

Sales Docs records can include customer names, customer emails, bill-to details, estimates, invoices, line items, prices, taxes, due dates, expiration dates, purchase order details, payment instructions, public response tokens, PDF settings, email recipients, CC recipients, sent-email events, and payment history. Velryq uses this data to create and send documents, detect native document blockers, request POs, send payment links, and track recovery actions.

AI-Assisted Features

When AI-assisted message drafting or feedback is used, relevant opportunity details, rule signals, source context, and user feedback may be sent to OpenAI to generate or improve draft messages. Users should review AI-generated content before sending or relying on it.

How Data Is Used

Data is used to detect overdue invoices, stale estimates, accepted-not-invoiced work, missing or required PO signals, failed payments, open quotes, refund or dispute review needs, duplicate or credit leakage risks, and other recoverable revenue opportunities. Activity and recovery actions are stored so users can track what was reviewed, contacted, recovered, dismissed, snoozed, or saved as a prevention rule.

Service Providers

The app uses Supabase for authentication and database storage, Stripe for billing and connected payment-source records, Intuit QuickBooks for accounting data access, Azure Communication Services for transactional and Sales Docs email, Sentry for error diagnostics, Vercel for hosting and anonymized web analytics, and OpenAI for AI-assisted message drafting when enabled.

Cookies And Diagnostics

Velryq uses essential cookies and similar browser storage for sign-in, security, OAuth connection checks, billing redirects, cookie preferences, and account preferences such as theme. These are needed for the requested service. Vercel Web Analytics helps measure aggregate traffic such as page views, referrers, countries, browsers, operating systems, and device types without using cookies. Optional browser diagnostics are only enabled after a user accepts non-essential cookies.

Choices

Users can accept or reject non-essential browser diagnostics from the cookie notice. Rejecting non-essential cookies does not block sign-in, billing, QuickBooks, Stripe, Sales Docs, or security features. Users can disconnect connected sources, delete available native records through the app where supported, and contact support for workspace data requests.

Retention And Deletion

Users can disconnect QuickBooks or Stripe from the Integrations page. QuickBooks disconnect removes its stored tokens. Stripe disconnect stops payment actions and sync but retains the encrypted OAuth grant solely for easy reconnect while Velryq remains installed in Stripe; removing Velryq in Stripe revokes that grant completely. Disconnect does not automatically delete previously imported records, native documents, findings, recovery actions, billing records, or audit history. Users can schedule account deletion from Account settings. See the account deletion instructionsfor the exact steps. Velryq immediately locks the account, stops scheduled sync, and cancels recurring Velryq billing while preserving the workspace for a 30-day restoration period. If the user does not restore the account before the deadline, Velryq permanently deletes the authentication account, workspace records, connected-source tokens and imports, stored business assets, and related application metadata. Third-party providers may retain records they are independently required to keep. Contact support for export requests or deletion questions.

During a temporary security block, workspace data remains stored and billing or scheduled integrations may continue while the review is open. During a longer administrative suspension, Velryq retains the Auth account and workspace data but blocks access, cancels recurring Velryq billing, turns off scheduled integrations, and stops new customer estimate responses and invoice Checkout. Enabling a suspended account does not automatically restart billing or scheduled integrations. Administrative suspension is separate from permanent account deletion.

Contact

For privacy questions, contact support at support@velryq.com.