Privacy, explained.

Who we are

PayQuery is operated by Sultans of SaaS. This notice explains how we use information across the website and reporting service. Contact help@payquery.app about privacy or your information. Workspace owners decide which billing accounts to connect and how to use or share their reports. If your information appears in a company's billing records, that company may also need to handle your request about those records.

Information we handle

• Accounts: email, authentication information, workspace names, memberships, preferences and support correspondence.
• Connected data: supported Stripe and Paddle records, including customer names, emails and addresses, payment and subscription details, invoices, refunds, payment-method descriptors and metadata. We store source objects alongside reporting tables.
• Connections and reports: encrypted provider keys and signing secrets, sync history, saved SQL, dashboard settings, sharing permissions, recipient addresses and shared-result caches.
• Billing and usage: PayQuery subscription and invoice information, masked payment-method details, AI usage, page analytics, network-derived demo limits and service diagnostics. Stripe collects payment details through its hosted checkout and portal.

Why we use it

We use information to provide accounts, imports, reports, sharing and AI drafting; manage subscriptions; deliver service emails; answer support requests; and protect and maintain the service.

Where applicable law requires a legal basis, account and subscription processing supports our agreement with you. Service security, abuse prevention and reliability support our legitimate interests in running PayQuery. We also process information when required by law, and rely on consent where we ask for it. Connected billing information is processed according to the workspace's instructions and settings.

Ask AI

Ask AI sends your question, documented table and column descriptions, and SQL-writing instructions to Anthropic. A correction request can also include the previous generated draft and validation feedback. Drafting does not automatically read or send imported customer rows or query results. Anything you type into the question is included in that request; leave out passwords, API keys and unnecessary personal information.

Services that help run PayQuery

We use Vercel for hosting and analytics, Supabase for authentication and database storage, Inngest for background processing, Anthropic for AI drafting, Resend for email, and Stripe for PayQuery subscriptions. Your connected Stripe and Paddle accounts supply the billing data you import.

Inngest receives verified webhook event payloads, which can include billing and customer information. Resend processes recipient addresses and email content. Operational alerts contain failure categories, counts, times and internal IDs, rather than SQL or customer records. Service providers may process information outside your country; using PayQuery does not mean that all processing stays in your country.

Report sharing

Reports default to workspace access. Owners and editors can enable a public link or restrict a link to selected email addresses. Public links can be opened by anyone who has them. Invited readers sign in and verify an allowed address. Shared results include all returned columns, even those hidden in a visualisation. Changing back to workspace access disables the shared link, but cannot recall copies already downloaded.

Cookies, browser storage and analytics

Authentication and routing cookies support sign-in and onboarding. Browser storage keeps interface preferences, recoverable editor drafts and recent SQL history; demo reports and dashboards can be saved there too. Stale editor and history entries are rejected after seven days when read. This does not erase an unopened browser's storage.

Our analytics integration removes query parameters and fragments from page URLs and excludes shared-report pages. Demo rate limiting stores a daily keyed network identifier instead of the raw IP in its usage table, retaining the current and previous UTC day. Hosting providers also process technical network information to serve requests.

Retention and deletion

We retain account and workspace information to provide your reports, maintain the service and handle billing, disputes and applicable legal obligations. Retention depends on the data's purpose and whether it is still needed. Canceling a subscription does not automatically delete imports, saved reports or dashboards.

Contact help@payquery.app to request account or workspace deletion. We may need to verify your identity or authority and explain any information that must be retained. Revoking a provider key stops future API access; disable its webhook separately to stop event deliveries. Neither action deletes previously imported data.

Your rights and choices

Depending on applicable law, you may have rights to access, correct, delete or receive a portable copy of your personal information, restrict processing, object to processing based on legitimate interests, or withdraw consent where used. Contact help@payquery.app to exercise a right or raise a concern. You may also complain to the relevant data-protection authority where those rights apply. Workspace billing and sharing choices remain available through their settings.

Updates to this notice

We may update this notice as the service or its data handling changes. The date above identifies the current version. Where a change requires additional notice or a choice under applicable law, we will provide it.