Privacy notice

Version beta-2026-09-25

Quack invite-only beta — privacy notice

Effective September 25, 2026 · Version beta-2026-09-25.

Who operates Quack

Quack is operated by Kiamichi Skies LLC. Questions about privacy, access or account closure can be sent to j.paul.grayson@icloud.com. The initial free, invite-only beta is intended for United States residents age 18 or older.

Information Quack handles

Quack stores account and sign-in information; conversation membership and invitations; shared messages and checkpoints; AI connection permissions; private AI activity, task requests and reply drafts; review and publication records; and operational records used to run, troubleshoot and secure the service. Where used, attachments and notification subscriptions are also handled by Quack. Support requests contain the information you choose to provide.

Reply drafts can retain both the original AI text and the version edited for publication. Dismissing a draft prevents publication but does not currently erase its stored record. A task expiring or being cancelled does not itself erase the task record.

We use this information to provide collaboration, enforce access choices, deliver requested notifications, investigate problems and recover the service from backups.

Who can see what

Conversation members can see shared messages. Addressing a message to one person does not hide it from other conversation members. Review the conversation and recipients before sending.

AI reply drafts, delegated tasks and private AI activity are restricted to their owner's authorized workflow; they are not shared with other conversation members merely because they were created. “Private” does not mean inaccessible to the service operator for necessary administration or support, or inaccessible to the AI provider that processes the request.

Joining a conversation does not authorize an AI. You separately choose which conversations a compatible connection may access. Your private chat in another AI app stays there unless you or that app sends information into Quack. Information retrieved from Quack by an authorized AI is processed under that provider's own policies and account settings.

Quack’s application and sign-in databases run on operator-managed equipment in the United States, with encrypted recovery copies on a separate operator-managed computer in the same office. DigitalOcean hosts the public gateway in New York. We use Whois.com DNS and Tailscale for relevant network functions, Brevo for account email, Resend for operator alerts, and browser/device push services for optional notifications. Privacy/support correspondence is handled through iCloud Mail.

When you request a hosted AI response, OpenRouter routes the supplied text to an inference provider for the selected model. Quack requires endpoints OpenRouter identifies as having zero data retention and denies data-collection routes for those hosted requests. If no qualifying endpoint is available, the request can fail. Usage metadata may still be retained. This restriction does not govern your independently connected AI accounts. When you connect an external AI or bot, its provider and any chosen messaging service process information according to your authorization and their own terms/settings. These services may process information outside the United States. Quack does not promise that every external provider follows the same retention or model-training practices. We may also disclose information when legally required or necessary to investigate abuse and protect the service and its users.

Cookies and device storage

Quack uses functional cookies for sign-in and invitations, browser session storage for navigation and unfinished requests, and a service worker/device subscription for optional push notifications. Unfinished-request recovery can store unsent text in your browser. The main Quack app does not currently use advertising pixels or third-party analytics SDKs. If we introduce advertising measurement, we will update this notice and provide any applicable choices.

Your controls

You can review and edit a private reply before sending it, dismiss it without publishing it, and revoke an AI connection or its conversation access. Revocation stops new authorized retrieval; it cannot recall information already obtained by another participant or provider. Cancellation may not stop an AI call already running or its associated charge.

To request access, correction, account closure or deletion, email the privacy contact using your account address. We will verify control of the account using proportionate checks. Do not send passwords, authentication codes, private keys or sign-in links.

Retention and deletion

Recovery backups use a rolling 30-day retention period. Eligible terminal private draft and task content is removed after 30 days; pending drafts awaiting review are preserved. Minimal status and replay-prevention records may remain after content removal. These cleanup jobs run hourly and require operational monitoring. Verified deletion requests have a 30-day completion target, subject to applicable requirements, with account removal handled by the operator rather than an automatic self-service feature.

On account deletion, Quack will remove the departing user’s identifying account/profile details from shared-conversation attribution while preserving conversation history for remaining participants. Requests to remove specific message content will be reviewed separately. Preserved text can still contain names or other identifying information; removing profile attribution does not make an entire conversation anonymous.

Account closure revokes app and AI access, removes private content covered by the closure procedure, and removes the verified sign-in identity. Other records, including legacy fields, attachments, security and support information, require a request-specific review. Backups age out under the backup retention period; recovery requires replaying the current deletion ledger before reopening access. Copies held independently by other participants or AI providers are outside Quack's direct deletion control. Any retained information and the reason for retaining it should be explained in the response to the request.

Private activity history and account preferences remain available while your account is active, unless you request deletion; the 30-day draft cleanup does not erase all activity history. Shared messages remain available to conversation members as described above.

Application and sign-in service logs have a 30-day retention setting with hourly cleanup and size limits that may remove logs sooner. If the server is stopped, scheduled cleanup resumes when it runs again. Other infrastructure, security and provider records do not all use that same automatic schedule. We review those records for operational need and include them in applicable deletion-request reviews.

We review support correspondence 90 days after resolution and remove information no longer needed, unless an ongoing security, legal or support matter requires it. We retain a minimal record of policy acknowledgment and deletion handling when needed to document your choices, resolve disputes or prevent restored backups from reactivating a deleted account. These records are reviewed when your account is closed. External email and AI providers control retention of their own copies.

Security and notifications

Quack uses access controls and protected backups. It does not offer end-to-end encryption of shared conversations. No service can guarantee uninterrupted access or complete security. Keep your sign-in details private and share only information appropriate for an early beta.

Browser and device settings affect notifications. You can check Quack directly if a notification does not arrive.

Changes

We will identify the effective date of the published notice and inform beta participants of material changes before applying them where required. Contact the address above with questions.