sayso BY VEREANT

Sayso privacy notice

Last updated: 31 October 2026

Sayso by Vereant gives teams a place for conversations and shared work. This notice explains how the current app handles your information. For privacy questions or requests, contact Lorenzo Naidoo at lorenzo.d.naidoo@gmail.com.

Your account and workspace

Sayso stores your name, email address, sign-in identity and the profile details you choose to provide. If you use a password, Sayso stores a salted password hash, not the password itself. It also stores the messages, files, drafts, reminders, scheduled messages, canvases, lists and preferences you create.

Public channels are available to members of their workspace. Private channels and direct messages follow conversation membership. Being a workspace owner or administrator does not give someone access to private conversations they have not joined. People who can read content may copy or export it.

Google sign-in and optional connections

Google sign-in uses your Google account identifier, verified email address and name to identify your Sayso account. Sayso does not receive your Google password.

Connecting Google Drive and Calendar is a separate choice. The connection requests read-only Drive file metadata and Calendar event access. Sayso uses file names, types, modification times and links to help you find files. It uses event titles, times, locations, descriptions and links to show events from your primary calendar. It does not use this connection to read Drive file contents, change files or edit calendar events.

Only you can browse the Google account connected to your Sayso account. Opening a result takes you to Google; it does not share the result with your workspace. You can choose to share a link yourself in a conversation.

Sayso stores your connected Google email, granted permissions and encrypted access and refresh tokens so the connection can keep working. File and event results are fetched when you browse them; Sayso does not save those results in its database. Disconnecting Google in Apps removes the stored connection and asks Google to revoke access. You can also remove access directly in your Google Account.

Sayso uses Google user data only for the features described here. It does not sell that data, use it for advertising or use it to train general-purpose AI models. Sayso's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements: Google API Services User Data Policy.

Google may process Calendar API information in the United States and other countries where it operates, under Google's terms and privacy policies.

Hosting and other services

Cloudflare hosts Sayso and stores its application data and uploaded files. Sayso uses HTTPS, restricted application access and encrypted Google connection tokens. Messages are not end-to-end encrypted: the service processes them to provide collaboration and search.

Optional GitHub webhooks post configured repository events into a chosen channel. If you create a token for an external agent, that agent can search, read or post messages within the permissions you give it and your current conversation access. You can revoke the token. The Google browsing connection is not exposed through Sayso's agent tools.

Calls request browser permission for microphone, camera or screen access. The current deployment uses direct peer connections with a connection-discovery service; it does not automatically record calls. Audio or video clips you deliberately record and send are stored as message attachments.

Retention and your choices

Ordinary conversation history does not expire automatically. You can edit or delete your own messages. A deleted message is recoverable by its author for 30 days; its content and attachments are then removed from the live app. Identifiers may remain to preserve thread structure. Deletion does not recall copies another participant has already saved or exported.

You can update your profile, export conversation data you can access, disconnect Google and revoke agent tokens. Contact us for account-level access or deletion requests; there is no self-service account-deletion screen yet.

Your browser stores a sign-in cookie and local preferences, drafts and pending messages to support your session and recover interrupted work. Sayso and its hosting provider process technical request information for operation and security, including error records and temporary rate-limit identifiers. Sayso does not include advertising trackers.

We will update this notice before materially changing the uses described here and request fresh consent where required.