Hushweft / privacy
How data moves through Hushweft
Hushweft aims to minimize what it keeps and gives you control over connected accounts. Some processing is necessary to search the web, read the accounts you connect, provide summaries you request, and manage payments.
Sign-in and account profile
Creating a Hushweft account processes your name and email address and stores them with Better Auth. Email/password sign-in stores a password hash, not the password itself. The authentication service also keeps session and verification records; session metadata may include an IP address and browser user agent. If a deployment enables an OAuth sign-in provider, its sign-in tokens and profile data are handled by Better Auth and that provider. Account deletion sends a confirmation email through the Polsia email service, then removes the Hushweft login and its related account/session records after confirmation.
Search and sourced answers
Search works without a Hushweft account or session. Your query is sent to the Polsia web-search proxy to retrieve results, which the web-search service caches for one hour. The optional AI-answer setting is on by default. For factual answers, Hushweft sends the query and the result titles, URLs, and snippets used for the answer to the Polsia AI proxy. Arithmetic and supported linear or quadratic equations are solved locally; if the local solver cannot solve a math expression, only the query is sent to the AI proxy for a math-only answer. Turn the AI-answer option off to skip AI requests while keeping web results. Search terms and result text are not written to Hushweft’s database, durable app cache, or application logs, and Hushweft does not retain search metadata. Polsia proxies process requests; their downstream provider processing and retention are not verified or controlled by Hushweft. Avoid entering personal or sensitive details in a search query.
Connected accounts and inbox
Before a connection starts, Hushweft shows the provider permissions and current limitations. For currently supported mail connections, Hushweft fetches recent message identifiers, sender, subject, date, read state, and (for Gmail and Outlook) a short preview into a no-store response for your session. Notification records and message bodies are not saved in Hushweft storage. The encrypted account identifier, encrypted provider token or iCloud app-specific password, granted-scope description, sync timestamp, and a short error code are retained while the account is connected. Temporary OAuth state is stored as a hash and expires after ten minutes.
AI summaries
A summary is requested only when you choose it for a message. Hushweft fetches up to 6,000 characters of that message into the request process and sends the selected text to the Polsia AI proxy. The generated summary, category, and priority are returned to your browser session and are not saved as a notification record. The message body is not put into durable app logs or caches. Provider and Polsia processing or retention practices are governed by those services; Hushweft does not promise zero processing or make an unverified retention or model-training promise.
Provider access and actions
Google, Microsoft, and Apple/iCloud each receive the OAuth consent or app-specific password needed to provide the listed mailbox access. Hushweft requests no send or delete feature. Mark-read and archive are sent to the connected provider and the inbox reflects success only after the provider responds successfully. Disconnecting deletes the encrypted Hushweft connection record; it does not itself revoke access at the external provider, so also remove Hushweft from the provider’s security or connected-app settings. Other providers are shown as limited or unsupported unless their APIs expose a suitable, approved notification feed.
Preferences, subscriptions, and deletion
Hushweft stores your assistant toggle, digest choice, quiet-hour values, and per-category and per-account preferences. These settings currently control the in-app experience; the app does not send push notifications or scheduled digests. Subscription status is checked through the Polsia-managed Stripe billing flow and is not copied into Hushweft’s database. Stripe and Polsia receive the email/payment information needed to create and manage billing. Deleting your Hushweft account removes connected-account credentials and identifiers, preferences, temporary OAuth state, and your Hushweft login. Provider and payment services may retain records under their own policies.
Optional contact form
If you send feedback through the contact form, your name, email address, message, and submission time are stored in Hushweft’s ContactMessage database table and submitted to the founder’s Polsia dashboard. If that submission service cannot record it, Hushweft sends a notification to the company inbox through Polsia’s email service. Contact messages do not have an automatic expiry in the current app; contact Hushweft to request deletion. Do not include search queries, connected-account messages, or other sensitive details in a contact request.
Page-view measurement
The shared app template can enable a Polsia page-view tracking beacon when the deployment sets POLSIA_ANALYTICS_SLUG. When enabled, it stores a visitor identifier named polsia_vid in localStorage and sends it with page views and the configured slug to POLSIA_API_BASE_URL (default https://polsia.com), at /api/beacon/pixel. Hushweft has no app-owned switch for this framework-mounted tracker; the deployment operator can disable it by leaving POLSIA_ANALYTICS_SLUG unset. This is page-view tracking, even though it is not advertising or cross-site tracking. The deployed setting was not available to verify in this build.
This notice describes the current Hushweft implementation. Provider capabilities, legal requirements, and third-party handling can change; review the approved launch disclosures with the owner before distribution.