Privacy at a glance
Saywit processes the information needed to provide your account, conversations and the features you choose. Private message contents are encrypted on participants’ devices. Smart chats use service-side processing and, when needed for an enabled feature, the relevant AI or connected-service provider.
You control optional profile sharing, learning, connections and website measurement. Optional website measurement concerns public pages and completed registrations; it does not include your conversations or form contents. You can change your measurement choice using Privacy choices in the website footer.
We use necessary cookies and device storage to keep the service working and protect access. Optional measurement loads only with permission. You can contact us to request access, correction or deletion of personal information, or to withdraw consent. The sections below explain the data involved, recipients, retention and your rights.
01 · Who is responsible
Kamil Boberek, trading as Evlove Films, is the controller of personal data processed to operate Saywit. Contact us with privacy questions or requests using these details.
- Operator
- Kamil Boberek · Evlove Films
- Tax ID
- PL7272656853
- Address
- Różyckiego 7/96, 31-324, Poland
- Contact
- [email protected]
This notice covers Saywit. Services you connect, payment providers and AI providers may also process information under their own responsibilities and notices. Their role depends on the service and the account arrangement.
02 · Information we process
- Account and profile: account identifiers, password hashes, phone number and verification status, email address and confirmation status, display name, profile photo and visibility choices. Confirmation links establish access to an email inbox before the address can be used to sign in; phone ownership is verified separately by SMS.
- Conversations: participants, chat titles and mode, message times and delivery information, messages and files as described below, replies, reactions, edits and deletion records.
- Smart features: assistant requests and answers, retrieved sources, tool inputs and results, action permissions, reminders, context notes, optional learned context and search embeddings.
- Connections: selected services, encrypted credentials or authorization tokens, scopes, connection status and action records.
- Payments and usage: Stripe customer, subscription and transaction references, status, amounts, refunds and related accounting records; model, token, request and estimated-cost records. Saywit does not store your full payment-card number.
- Invitations and referral rewards: invitation attribution, verified-registration credit entries, reward codes and redemption status. Invitation delivery budgets store keyed hashes of recipient addresses and request sources, rather than a list of recipient email addresses. The delivery provider receives the address needed to send your requested invitation.
- Technical operation: sessions, device and notification identifiers, IP addresses and request or error metadata where recorded by the application or infrastructure, and support correspondence.
Information comes from you, people messaging you, your authorized connected services, and providers returning the result of a requested operation. Some profile or conversation context is derived from eligible messages rather than directly entered into a profile field.
Account and service information needed for a requested feature is necessary to provide that feature. Optional profile details, learning and optional device permissions are not required for free Private messaging.
03 · Private and Smart mean different things
Private chats
Private message and attachment contents are encrypted on the participants’ devices before upload. Saywit routes ciphertext and public device-key material; it does not receive the device decryption keys. Private contents are excluded from server-side AI processing and semantic indexing. Private search works with the history available locally on your device.
The server still handles metadata needed for the chat, including membership, chat title, message timing, delivery, event type and attachment size. Encryption does not hide those details or stop a recipient from saving, copying or sharing decrypted content. Device compromise can also expose it.
Smart chats
Smart chats are not end-to-end encrypted. Their content can be read by the service to deliver messages, run assistants and provide search. Depending on the enabled feature, the configured providers can receive relevant recent or retrieved messages, attachments or extracted content, permitted profile fields, context notes and connected-tool results.
Jev, provided through TypeSafe, makes fast contextual decisions. The selected assistant provider handles fuller responses and tool workflows. Background analysis uses the configured analysis provider. An assistant request marked “Only you” is hidden from other participants; that label does not prevent processing by Saywit or the relevant providers.
Search sends eligible text, images and extracted document content to Voyage AI to create embeddings. Audio and video can be transcribed locally on Saywit’s server; transcripts and selected video frames can then be used for embedding and search. Embeddings and source references are stored in the service’s Vectors index and checked against chat access.
Embeddings, generic member aliases and reduced context do not make conversation data anonymous. Text, photographs, voices and documents may still identify a person. There is no guarantee that sensitive information is automatically detected or removed before processing.
04 · Profile visibility and optional learning
Profile controls let you choose whether your display name, email and verified phone number are private, available to chat participants, available to AI, or available to both. “Both” does not publish a public web directory. Your photo can be private or visible in chats; profile photos are not sent as AI profile context.
When a profile field is private, the relevant profile disclosures are withheld; a generic member label can replace a hidden name. You still see your own details. Changing visibility affects later profile access, not messages, screenshots or information already received by another participant or provider. Typing a phone number or name into a message shares it according to the message’s chat mode.
Optional profile learning uses your own eligible Smart messages to summarize expressed preferences, habits and ideas and provide source-linked context. It is off by default. You can enable or pause it, review or forget remembered items, and clear learned context from your profile. Pausing learning stops new learning; it is separate from clearing what was already saved.
Learned context can be tentative and wrong. It is used for assistance and personalization, not as a verified psychological assessment. Private chat contents are excluded. Learned personal context is not supplied to public assistant replies. Written assistant context that you save as shared is available to participants in your Smart chats and to AI for assistance there, including public replies. Notes saved under the earlier private setting remain private until you explicitly share them or save an edited note using the shared-context interface. Shared chat-context notes are available within their Smart chat. These settings do not publish a public web directory.
Suggestions and summaries do not constitute decisions with legal or similarly significant effects. Saywit does not use profile learning to make such decisions about you. Saved action permissions are separate from learning and can be revoked.
05 · Why we process it
- Providing the service — GDPR Article 6(1)(b): account access, message delivery, requested Smart assistance and search, authorized connections, support needed for the service, subscriptions and payment administration.
- Your consent — Article 6(1)(a): optional profile learning and other optional processing for which we request consent. You can withdraw consent as easily as you give it; this does not affect processing that was lawful before withdrawal.
- Legitimate interests — Article 6(1)(f): proportionate security, fraud and abuse prevention, diagnosing failures and establishing or defending claims. Our interests are maintaining a secure, reliable service and protecting users and our legal rights, subject to your rights and reasonable expectations.
- Legal obligations — Article 6(1)(c): applicable accounting, tax, payment-related and other legal duties, including responding to valid requests from competent authorities.
Enabling a browser permission is a device control; it does not by itself replace any separate consent required for personal-data processing. We do not treat agreement to every optional feature as a condition of using Private messaging.
Conversation participants may share information about others. Do not put sensitive information into Smart processing unless you have a lawful basis and any necessary explicit consent. A general service agreement is not a blanket authorization to process special-category data.
06 · Services that may receive data
Access is limited to what is needed for the feature or responsibility involved. Relevant recipients include:
- Other chat participants: the messages and files addressed to them, shared chat context, written assistant context shared in their Smart chats, and profile fields you allow. Private assistant replies remain restricted to their requester.
- AI providers: TypeSafe/Jev for enabled contextual routing; the configured OpenAI, Anthropic, xAI (Grok) or Inception service for model work; and an own-account ChatGPT connection if used. Not every request is sent to every provider.
- Voyage AI: eligible Smart content used for embeddings and search. Vectors is the service’s search store, rather than a second AI model provider.
- Connected services: for example Google services, ClickUp or a custom MCP server you authorize. A tool may send content to that service and return information to the selected model.
- SMSAPI: the phone number and verification request needed to deliver and validate an SMS code. The verification service also processes delivery and security metadata.
- Twilio SendGrid: your email address, any greeting name included in the email, verification messages needed to confirm an address or continue signup, and invitations explicitly requested by a Saywit user. Delivery also involves email and security metadata. These messages do not enroll the recipient in marketing.
- Stripe: payment and subscription information, and payment details entered directly into its payment flow. Banks and payment networks also process the transaction.
- Infrastructure and support providers: hosting, storage, network delivery, notification delivery and authorized operational support; professional advisers or public authorities where necessary and lawful.
Own-key providers are also governed by your account settings and agreement with them. Provider logging, retention and model-training rules vary by product and account. Saywit does not promise that all providers retain nothing or that a setting on one provider applies to every other service.
International processing
Some providers and their support or infrastructure may process data outside the European Economic Area, including in the United States. Where required by the GDPR, transfers must use an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses, with additional measures where needed. The applicable arrangement depends on the provider and account; using an own key does not automatically remove transfer obligations.
Contact us for information about the providers involved in your service, processing locations, and the safeguards applicable to a transfer, including how to obtain a copy. Do not assume that Smart processing remains solely on the Saywit server or within Poland.
07 · Storage, edits and deletion
We retain service data for as long as it is needed for the active account, the conversations and features you use, and the purposes described here. Retention also depends on deletion requests, other participants’ rights, security needs, legal claims and statutory accounting or tax obligations. Different records have different requirements; there is no single automatic deletion period for all Saywit data.
Referral attribution in a signup session expires after 30 days. Invitation delivery-budget records are cleaned up after 24 hours when another invitation is sent. A minimal keyed hash of a verified email address or phone number that has already earned a referral credit can remain after account deletion to prevent repeated rewards for the same identity. This is pseudonymous information, not anonymous data, and is used only for referral-abuse prevention. Contact us to request a review of its retention.
Editing keeps a history. Earlier versions remain stored. Deleting a message removes its active content from the conversation, but the saved revision history can remain, and attachment or delivery records may remain. Hiding a chat is not the same as deleting it. A deletion in the interface is not a promise to erase all copies everywhere.
Search and learned-context references are revalidated or removed as sources change; background cleanup can take time. Clearing learned context is separate from deleting the original messages. Disabling learning does not automatically erase its existing records. Token and transaction records can remain independently of a hidden chat.
For account closure, a copy of your information, or erasure beyond the available controls, contact us. We will identify which data can be removed and explain any lawful reason to retain particular records. Data required for accounting, a dispute or another legal obligation may need to be kept with restricted use.
Recipients’ copies, connected-service records, provider records, backups and browser caches are distinct from the active chat. Some may need separate deletion steps or remain until their applicable retention cycle ends. We do not promise immediate removal from every backup or third-party system. You can clear browser storage yourself, but doing so can permanently remove your Private decryption keys.
08 · Security and your device
Private messaging uses a Signal-based implementation with per-device keys and ratcheting message encryption. Private attachments use AES-256-GCM. Private key material is held in an encrypted browser vault using Web Crypto and IndexedDB. The browser also holds the key needed to open that vault; this is not a separate hardware-backed or password-protected recovery vault.
Smart data is protected by transport security, authentication and access checks, rather than Private end-to-end encryption. Provider and connection credentials are encrypted on the server and decrypted when needed for an authorized request. Storage protection depends on the configured storage service; this notice does not claim that every stored Smart message is separately encrypted at rest.
We use necessary session and security cookies, including session and CSRF protection, and local storage for preferences, cached media, offline functionality and Private keys. These support requested features. Browser controls can clear this storage, but may sign you out or remove locally available history. Push notifications use your chosen browser’s delivery service when enabled; notification details may be visible on a device’s lock screen.
Optional website measurement
Optional website measurement helps us understand whether our advertising leads to completed Saywit registrations. Google Ads measurement on public pages loads only after you choose Allow measurement. Choosing Essential only keeps it off; this does not affect your account or conversations. You can change your choice using Privacy choices in the website footer.
With your permission, Google receives technical request information and ad-click identifiers, and can use advertising cookies to attribute a completed registration. The registration event describes a successful email signup; it contains no email address, name, account identifier, form contents, verification token or conversation data. We do not enable personalized advertising or enhanced conversions. Measurement is excluded from the chat app and account forms; the clean signup-completion page can report the completed registration.
Your browser remembers this optional choice for up to 180 days without a personal identifier. Withdrawing it stops later measurement, removes accessible Google Ads cookies and reloads the page to unload the measurement script. Previously sent information remains subject to Google’s processing and retention. Opening the verification link in another browser may prevent an ad click from being attributed to that registration.
Desktop app operation
Desktop document knowledge is optional. Choosing a folder or documents previews a selection; Start indexing authorizes uploading extracted text. Encrypted document chunks and searchable vectors are stored in our internal Vectors database; encrypted names and owner-scoped lifecycle records are stored in the application database. The server can decrypt selected chunks to create embeddings and answer authorized questions. This feature is not end-to-end encrypted. Voyage AI receives selected text and private search questions for embeddings. Up to five relevant chunks can be sent to your configured AI provider for an Only you answer. These sources are private to their owner and are excluded from shared assistant answers.
In the local AI dialog, Search selected cloud knowledge is off by default. Enabling it sends only the typed question to cloud search and retrieves up to five chunks for your local model. Loaded Private conversation history is not uploaded by that search; the local reply stays on your computer until you choose to share it. Pausing a source immediately excludes it from new retrieval. Removing a source removes access immediately and queues deletion of its encrypted chunks and vectors. Copies already included in answers or received by a provider are subject to their separate retention rules.
The signed-in desktop chat app reports its operating system, processor architecture, app version and approximate foreground activity to the service. A temporary session identifier changes when the app page or signed-in account changes. Activity covers time when the chat window is visible, focused and recently used, sampled every two minutes; keyboard values, chat content, model prompts and local files are not part of these reports. Hidden, idle, sleeping and offline time is excluded. The global service administrator sees aggregate downloads, active users, sessions and activity by operating system and app version.
Daily desktop usage records are associated with the signed-in account and use a 365-day retention window, with daily cleanup. Session replay records expire after 30 days without a report. Download measurement records the requested installer and version when delivery starts at the origin; it does not prove that an installation completed. Download links can include a fresh identifier for that single download. Only a keyed hash is stored for a 24-hour retry window and removed during daily cleanup, without an analytics cookie or persistent installation identifier. Infrastructure request logs remain subject to their separate retention described above.
Quote in Saywit browser extension
The Chrome and Firefox extension reads text only when you invoke it on a webpage. Clicking Choose a chat in the toolbar preview, or choosing Quote in Saywit in the selection context menu, hands your selected text, the source page title and its HTTP or HTTPS URL to Saywit so you can choose a chat and review a draft. It does not send a chat message automatically. Source links include their query string and fragment, which can contain private information; review them before sending.
The extension has no analytics, advertising, background page scanning, persistent extension storage, cookie access or saved account credentials. It does not collect your browsing history. It accesses the active page after your gesture using activeTab and scripting; contextMenus provides the selection action. Firefox declares selected website content and the source URL as websiteContent and browsingActivity for its built-in data-sharing consent.
The handoff uses a URL fragment, which is not sent in the HTTP request but can temporarily appear in browser history. The quote entry page omits website analytics and removes the fragment immediately. That tab holds the pending quote in session storage for up to 15 minutes to complete sign-in; adding or cancelling the quote clears it. The quote is bound to the signed-in account once claimed. Sending it applies the destination chat’s normal Private or Smart processing described above. Data is used to provide the requested quote-to-chat feature; the extension does not sell it or use it for advertising or creditworthiness decisions. You can cancel the draft, clear that tab’s session storage, or remove the extension. For information already sent as a message, use Saywit’s message and account controls or contact us using the details in this notice.
Quote in Saywit follows the Chrome Web Store User Data Policy, including its Limited Use requirements, when using or transferring quote information.
Keep your browser and device updated and protect access to them. Encryption cannot prevent someone with an unlocked device, compromised browser, or a recipient’s saved copy from reading content. New devices may not be able to decrypt earlier Private messages. Saywit does not claim that its implementation is independently audited or that any system eliminates all risk.
09 · Your rights and how to reach us
Subject to the conditions in the GDPR, you can request access and a copy, correction, erasure, restriction, and portability of qualifying data. You may object to processing based on legitimate interests and withdraw consent for optional processing. You can also raise concerns about profiling or automated processing.
Use the profile and learning controls where available, or contact us using the details at the beginning of this notice. We may ask for proportionate information to verify your identity and protect other users; do not send passwords, API keys or full payment-card details.
We normally respond within one month. If a request is complex or numerous requests require an extension, we will explain this within that first month; the GDPR permits up to two additional months in those circumstances. If we cannot fulfill a request, we will explain why and how you can challenge the decision.
You may complain to the President of the Polish Personal Data Protection Office (UODO) or another competent data-protection authority, including in the country where you live or work. You do not have to contact us first to exercise that right.
We update this notice when the service or processing changes. The version date appears above. Material new processing requiring your consent will not be authorized simply by publishing a revised notice.
Reference: General Data Protection Regulation.