Information you provide
Saynote stores account information such as your email address and display name, the audio or text you upload, transcripts, summaries, tasks, projects, settings and build activity. Passwords are stored as salted hashes. Login sessions use protected session credentials.
Audio and AI processing
Recordings are sent to the service for processing. The current stack uses Groq for transcription, Alibaba Cloud Qwen for notes and questions, and pyannote for speaker grouping and optional voice matching. These providers receive the content needed to perform the feature. Audio processing is not entirely on your device.
Before AI processing, Saynote asks you to review these services and allow sharing. Your choice is saved to your account with the disclosure version and time. Declining keeps saved notes readable. You can withdraw permission for future processing in Settings; this stops waiting work but cannot recall requests already sent. A change to the providers requires a new choice. Deleting saved recordings or your account is a separate action.
Optional voice enrollment requires your confirmation. A saved voice profile helps match your voice in later recordings. You can skip enrollment or delete the saved profile in Settings. Deleting a voice profile does not delete its original memo; manage that recording separately.
Accounts and connected tools
Apple or Google may provide identity information when you use their sign-in options. Saynote associates a verified provider identity with your account. On the web, Google may load its sign-in library when enabled. Providers’ own privacy policies apply to their services.
When you pair a Mac, build briefs, progress, tool questions and results pass through Saynote. Coding runs through your own tool account on that computer. Its credentials stay with the tool. Generated project files remain on the Mac unless you separately choose to share or publish them. Your chosen AI provider processes coding requests under its own terms.
Optional iPhone camera access scans the pairing QR code shown by your Mac. Camera images are processed on your device and are not uploaded. The pairing code is sent to Saynote to connect that computer to your account.
Actions on your paired Mac
You can authorize a specific calendar event, reminder or message from the phone or web workspace. Saynote stores the reviewed details, destination, schedule and result in your account, with the action payload encrypted in service storage. Your paired Mac retrieves those details and uses only the capabilities you enable there. Calendar conflict checks stay on that Mac. Message sending does not upload your conversation history. Local recovery files retain pending actions until their results sync.
The iPhone keeps an interrupted request in its Keychain. The web app keeps an interrupted request in that tab’s session storage so a reload can recover the same action. These drafts may contain the recipient and message you entered. They are removed after the server confirms the saved request. A scheduled action can be cancelled before execution begins. A message handoff to Messages does not prove delivery.
Memory, people and daily planning
Saynote can suggest source-linked memories from recordings. Suggestions remain separate until you save them. You can edit memories, keep earlier decisions in history, or delete them. Editing a transcript withdraws memories derived from it; deleting a recording removes its derived memories and edit history. Deleting a memory also prevents that exact source passage from suggesting it again.
Names, context, and optional contact details you enter are stored in your account. Phone numbers and email addresses in saved contacts are encrypted in service storage. Choosing a contact can fill a reviewed message; it does not send anything by itself. Deleting a person removes their linked memories. Your tasks and recordings remain.
Relevant saved memories from the selected project may be shared with the configured notes AI when processing a new recording. Saved contact phone numbers and email addresses are not included in that context. Today uses your tasks, dates, pins, follow-up dates and snoozes. It does not read your mailbox to detect replies. You can turn off new memory suggestions while keeping saved context.
Infrastructure and local browser data
Cloudflare and the website hosting service deliver the website and route requests. The current beta’s processing service and storage are hosted on a development Mac. This is not a guarantee of uninterrupted availability. Optional voice profiles and operator credentials are encrypted in service storage; we do not describe every saved recording as end-to-end encrypted.
The web app uses a session cookie to keep you signed in and browser storage for preferences and pending uploads. Audio waiting to upload can remain in that browser until it is uploaded or removed. Google Fonts is used for website typography. No advertising tracking is intentionally included in this website.
How your information is used
We use information to provide the requested features, maintain your account, manage access and usage, resolve support issues and operate the service. Your private recordings are not public website content and are excluded from search indexing. We do not sell your recordings.
Your controls
You can edit or delete recordings, export supported data, delete an optional voice profile, revoke a connected Mac and delete your account from Settings. Some information may remain temporarily in operational backups or records required to resolve security, support or legal obligations. Contact us if you need help with a data request.
Recording other people
Only upload or record content you are allowed to use. Inform participants and obtain any permissions required for your situation. Review AI output before relying on names, dates, commitments or speaker identification.
Contact and changes
Contact support@tikliverankings.com for privacy questions or data requests. This policy will be updated when the service or its data practices change, with the effective date shown here.