The billing service stores your Google subject identifier, verified email, account ID, hashed app sessions, Stripe customer and subscription identifiers, payment status and minimal support and event records. Google handles sign-in and Stripe handles card details and payment, including billing addresses and business tax IDs when required for tax calculation and invoices.
The billing API does not receive captured page data, saved profiles, snippets or workflow payloads. Those remain in your browser. Short-lived authentication records expire automatically. Contact support to request account-data deletion; billing and legally required records may be retained.
SlashFlow processes text templates, reusable profile fields, page content, contact and company details, locations, page URLs/titles, field mappings, reviewed records and local activity history to provide text expansion and browser workflows. Templates and page text can include communications you choose to write or reuse. Where enabled, the extension detects context on supported pages locally so you can review it, and processes editable-field input to match saved shortcuts. It does not send a keystroke log or browsing-history feed to the account service.
Templates, profiles, saved workflows, collected records and activity history are stored in your browser. Temporary page context and transfer state expire and are tied to the relevant tab/page. You can review and correct captured fields before a transfer, choose a destination, and export saved data. Browser-form submission remains your action. A chosen website receives the values you place into its form; clipboard and CSV exports go to the destinations you choose. Uninstalling or clearing extension storage can remove local records and does not cancel a paid subscription.
The billing API does not receive captured page data, saved profiles, snippets or workflow payloads. Google handles sign-in, Stripe handles hosted payments and billing information, and Cloudflare hosts the account service. The service uses account/session and subscription records to authenticate you and issue access. Its security controls process network information such as the connecting IP address for rate limiting; application logs record error categories and reconciliation results. Complimentary reviewer licences also store the account's grant period, approval reference and revocation state. They do not create paid subscriptions.
SlashFlow's use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use data to provide, maintain and secure SlashFlow's stated features. We do not sell user data, use it for personalized advertising, use it for creditworthiness or lending decisions, or transfer it for unrelated purposes. Transfers are limited to the destinations you choose for workflows, service providers needed for authentication, hosting and billing, and circumstances permitted by the policy, such as security or legal obligations.
We do not allow people to read user data except with your consent for specific support, when needed for security or legal compliance, or as otherwise permitted for aggregated, anonymized internal operations under the policy. Captured page content and templates remain local unless you choose to transfer or export them. Account-data deletion requests can be made to support@quantamq.com; necessary billing, security, approval and legally required records may be retained.
We retain account subscription history, trial issuance and the original trial start and end dates to provide trial access, prevent repeated trials and keep cancellation and billing accurate. These records do not contain your saved templates or captured page content.
When available, you can choose Share basic usage in the extension Account panel. It is off by default. If you enable it, successful text expansion, transfer or autofill sends only an action category to our account service, associated with your signed-in account. We retain your consent date, first-use date, first return within seven days and most recent UTC activity day while enabled, to understand and improve product adoption. We do not collect the template, shortcut, message, page URL, domain, captured fields or workflow payload. Our internal GrowthOps dashboard receives aggregate counts only. Turn sharing off in Account to erase these usage measurements; account-deletion requests also erase them. This does not erase billing records or cancel your subscription. Re-enabling starts a new measurement period. Billing records are also used for aggregate registration, trial and paid-account reporting.
Optional website sign-in uses verified Google sign-in to recognize the same account you use in the extension. Signing in does not automatically link a campaign source. Only if you explicitly consent after signing in do we associate four declared campaign labels (source, medium, campaign and creative) with your account. We use this association for aggregate account, verified trial-start and current-access reporting. Current paid access is not a record of a first payment or a revenue amount.
A separate, unchecked financial-reporting choice lets us associate verified payments made after that choice, and related refunds and disputes, with the campaign in aggregate reports. Earlier source choices do not automatically enable financial reporting. Financial facts remain in the billing service; customer identities and individual payment identifiers are not sent to the marketing dashboard. Reporting distinguishes gross payments, refunds and dispute status, and does not claim accounting revenue or that a campaign caused a purchase.
This choice is separate from Google Analytics consent and extension usage sharing. Account-source association does not send your account identity to Google Analytics. We do not guess your identity across a Chrome Web Store visit or installation, and a declared campaign source does not prove that a website visit caused an installation or purchase. Google Analytics does not load on the onboarding or account-source pages.
You can review your linked source and choose Withdraw source consent at Account source settings. Withdrawal erases the active account-source association used for future source reporting; older website sessions cannot recreate it. Withdrawal also removes financial source linkage from newly generated reports; an already collected dashboard snapshot can remain until the next successful refresh and is marked stale if refresh fails. Historical aggregate reports collected before withdrawal may remain in restricted local backups. Our scheduled backup sets normally use a 14-day retention policy, but the newest and manually retained backups may remain longer; this is not an absolute deletion deadline. Operational billing records remain separate from this optional association. Financial snapshots in the billing service retain operational facts without campaign labels. It does not cancel a subscription or change your extension access. For questions about account-data deletion or retained records, contact support.
With your permission, this website uses Google Analytics to measure page visits and clicks to the Chrome Web Store. These clicks are not confirmed extension installs or purchases. Google receives a cookie-based browser identifier, basic device and network information, this site's page path, limited campaign labels (source, medium, campaign and creative labels) and the referring site's origin. These labels use only letters, numbers, underscores or hyphens, up to 64 characters each. We do not send your account identity, form contents, URL fragments or other query parameters. Advertising personalization and Google signals are disabled.
Google Analytics loads only after you accept. Choose Decline to browse without it, or use Analytics choices on any website page to change or withdraw your choice. We remember that choice locally for up to 180 days. On withdrawal we stop collection on this site and clear its Google Analytics cookies; this does not erase data already sent to Google. We honor Do Not Track and Global Privacy Control. Website analytics is separate from the extension's optional usage measurement. Website typography also loads Google Fonts independently of your analytics choice.