Know what you’re sending.

Content used for a check

A website check fetches a bounded set of public pages from the URL you supply. A draft check also processes your draft and any supplied audience, effective date or replacement URL. An instruction check processes the Markdown files, relative paths, scope and precedence that you or your authorized agent explicitly submit.

That content goes to SyncWise’s hosted service and its configured model service to produce findings. Results include captured source text, quoted evidence and source fingerprints. Only submit material you are authorized to share; remove secrets and unnecessary personal information first.

The connector does not independently collect your conversation history, search your filesystem, or publish changes. Your agent platform controls its own conversation, file access and storage, and may retain the returned results under its own policies.

Accounts, credit and operational records

Clerk handles sign-in and account linking. SyncWise uses your authenticated identity and verified email to associate your account and limit trial-credit abuse. Its account store retains derived identity and email hashes, credit balances, API-key hashes and metadata, audit operation records, and checkout records. The full API key is shown when created; the account store keeps its hash for authentication.

Stripe handles checkout and payment details. SyncWise records the checkout identifiers, amounts and crediting status rather than storing card details. A checkout labelled test or sandbox does not make a real payment.

Hosting and authentication services process technical request information. SyncWise’s audit usage logs record operational metadata such as the model, token counts, cost and generation identifier where available. The application’s audit logging code does not intentionally log submitted text, model prompts or credentials. If you contact support, we also receive the information you include in your message.

Services involved

• Vercel: website and API hosting, and AI Gateway routing of audit requests.
• Model providers: the current website analyzer uses an Anthropic Claude model through AI Gateway. Draft and instruction analyzers use server-configured models; the audit’s analysis metadata identifies the model used. Gateway routing may involve an upstream hosting provider.
• Optional draft prefilter: when enabled by the operator, TypeSafe’s Jev model receives the submitted draft, audience/date context and captured public page text to select pages for the main auditor. This experimental feature is off by default. Results identify whether it ran and which pages were omitted from the main review. See TypeSafe’s data-handling terms.
• Clerk: authentication and OAuth account linking.
• Upstash Redis: account, credit, checkout and audit-replay storage.
• Stripe: checkout and payment processing, including sandbox checkout during testing.
• GoatCounter: cookie-free website analytics on public pages, including pageviews, referrers, campaign information, browser, screen size and approximate location. Account, sign-in, sign-up and OAuth pages are excluded. See GoatCounter’s privacy notice.

Provider retention, routing and processing locations are separate from SyncWise’s application cache. We do not currently promise zero data retention or a particular processing region across these services. Contact us before submitting material that requires a specific contractual processing arrangement.

Provider information: Vercel, Anthropic commercial privacy, Clerk, Upstash and Stripe. Their public notices do not establish a special retention agreement for SyncWise.

Storage and retention

• Audit replay: the server’s saved response expires 24 hours after settlement. It can contain the submitted draft or instruction text and captured website sources. Expiry of this cache is not deletion from every provider, browser, agent or downloaded file.
• Account and billing metadata: account, trial-eligibility, key, checkout and audit-ledger records currently have no automatic expiry in the application. They support access control, credit reconciliation and prevention of duplicate charges. The account view shows recent history, not the entire set of retained records.
• Your browser: local storage keeps the last website check, the last draft check, saved review decisions, recheck summaries and theme preference until overwritten or cleared. Tab session storage keeps form text, including a draft, and pending-request information for sign-in returns and retries. Signing out does not clear all of this local data.
• Other copies: downloads, support correspondence, infrastructure logs and provider records have separate lifecycles. There is no single verified deletion period covering them all.