Privacy Policy

SumAlaizer processes account data, Topics, source URLs, generated Summaries, citations, preferences, and operational records needed to provide and secure the service.

Authentication

Email accounts store a one-way password hash. Google sign-in stores the provider’s stable account identifier and verified email. SumAlaizer does not store Google passwords.

Payments

Payments are completed on Wallet’s hosted checkout. SumAlaizer stores order and transaction identifiers, amount, currency, plan, and status, but not payment-card credentials or raw payment callback bodies.

AI processing and sources

Source material and task instructions may be sent to configured AI providers to produce summaries. Secrets and payment credentials are excluded from prompts. Provider retention depends on the deployed provider agreement.

Optional product analytics

With your analytics consent, GA4 receives page and product events, browser and session identifiers, campaign tags, and server-confirmed registrations, purchases and refunds. Financial events include a transaction identifier, currency and amount where supported. Summary text, source URLs, private searches and account identifiers are excluded. Advertising measurement requires separate consent; personalization stays off. You can withdraw consent below, including for queued server events. Attribution receipts expire after 90 days of inactivity; order attribution is retained for up to 90 days.

Retention and security

Data is retained while your account or operational obligations require it. Access is tenant-authorized; sensitive credentials remain server-side. Backups and logs are protected and retained for bounded operational periods.

Your choices

You can change your preferences and sign out all sessions. Account export and deletion requests will be handled through the operator’s support process until self-service controls are available.

Optional authenticated sources

Only with your source-specific permission, the Chrome extension sends that site's cookies and the localStorage/sessionStorage keys you select to the configured SumAlaizer server. These can grant access to your site account. Snapshots are encrypted in transit in production and at rest, used only to read that source, and never included in AI prompts. The selected source content is sent to configured AI providers for private summaries. Optional updates on later visits require the same app account, approved origin and storage keys. Consent lasts up to 30 days. Disconnect in the group's Source access settings deletes the active saved session and stops future processing; existing summaries and operational backups follow the retention policy above. You can also withdraw Chrome site permissions. No raw snapshot is stored in the extension or included in diagnostic logs.