Privacy Policy

Effective and last updated: October 15, 2026

This policy explains how the Sayloe development team (“Sayloe”, “we”, “us”) handles information through the Sayloe Mac application, its supporting cloud services and sayloe.com. For questions or privacy requests, contact sayloe@molabuzz.com.

1. Text and permissions in the Mac app

When you trigger a translation, Sayloe processes your selected text, source and target languages, translation results and a translation back into your language. The app also uses temporary context, such as the active application, selection position and whether a field supports editing, to place the preview and avoid replacing the wrong text.

macOS Accessibility permission enables supported selection capture and replacement. Where Accessibility cannot retrieve text, Sayloe may temporarily use the clipboard to capture the selection. Copy and supported paste operations also use the clipboard. The app attempts to preserve and restore clipboard contents during temporary capture or replacement; copying a translation intentionally places that result on your clipboard. Your Mac’s clipboard managers or other software may keep their own copies.

Preferences, such as your language, engine and shortcut choices, are stored locally. Where credentials are needed, supported builds use macOS Keychain for session tokens, device credentials or user-supplied API keys. Removing the app may not remove Keychain entries or all local preferences.

Apple translation

The Apple engine uses Apple’s system Translation framework and available language models. Availability and downloads depend on your macOS version, device and language pair. This engine does not send your selected text to Google through Sayloe’s cloud translation service. Apple’s system services and downloads are subject to Apple’s privacy information.

Google and cloud translation

Using a cloud engine requires transmitting text for processing. In builds configured for Sayloe’s cloud service, requests pass through that service to the translation provider. A translation request includes the selected text, language information, engine, operation identifiers and authentication or device credentials. Back translation sends the translated result for a further translation. Development or individually configured builds may connect directly to a provider using an API key.

Cloud providers have their own processing, security and retention practices. See Google’s Privacy Policy and, where Google Cloud is used, Google Cloud’s Privacy Notice. We do not promise that cloud translation is entirely on-device or that a provider retains no data.

The first-release plan does not make Google LLM or Gemini available to customers. This policy does not imply that an upcoming engine, login option or other feature is available in every installed version. We will review these disclosures when processing changes.

2. Sign-in, device identity and daily allowances

Where cloud access is enabled, a generated device identifier and a device credential allow the service to authenticate a device, apply guest allowances and prevent abuse. These are not a claim that guest use is unidentifiable: network and service metadata may also be processed.

If you choose to sign in with Google, Google handles your credentials in its authentication flow. Sayloe’s configured authentication service uses Supabase Auth. It processes account identifiers, email and basic profile information supplied through the authorization flow, along with access and refresh tokens. Sayloe does not ask for your Google password or request permission to read Gmail messages or Google Drive documents as part of this sign-in flow.

The supporting service maintains device and account associations, daily usage counters, request states, timestamps, engine and cost metadata, and security/rate-limit information. Request or network hashes may be used to detect retries and abuse. These records help enforce allowances and avoid charging the same operation twice. Signing out removes the local account session, but does not erase server-side account or usage records. Revoking access at Google does not by itself delete those records.

See Supabase’s Privacy Policy for its practices. Features depend on the app build and configured services; the website’s preset demonstration does not sign you in or call a live translation engine.

3. Website information, cookies and analytics

Hosting and security providers, including Vercel, process technical request information such as IP addresses, browser information, requested URLs, timestamps and error/security information to deliver and protect the website. Protected deployments may also use Vercel authentication and session cookies. See Vercel’s Privacy Policy.

The production website integrates Google Analytics 4 (measurement ID G-GXX3JQ5NE5) to understand visits and interactions. Analytics can use cookies and browser/device identifiers and process page URLs, referral information, browser/device characteristics, approximate geography and interaction events. Our custom events record fixed labels for actions such as viewing engine information, using the preset demo or clicking early access; they are not intended to contain selected app text, translations, email addresses or form values. Google Signals and advertising personalization are disabled in our tag configuration. Analytics is excluded from preview and local builds.

For more information, see how Google uses information from partner sites and Google’s cookie information. You can block or clear cookies in your browser or use Google’s Analytics opt-out browser add-on where supported. These controls do not necessarily stop essential hosting or security logging.

The website currently shows preset demonstration text and a coming-soon early-access message; it does not currently offer a working registration form or collect subscription payments. If you email us, we receive your address, message and any attachments and use them to respond. Please do not include sensitive translation content in a support request unless necessary.

4. Why information is used and shared

We use the information described above to provide translations and previews, authenticate users and devices, enforce allowances, secure and troubleshoot the service, respond to requests and understand website use. Information is disclosed to the relevant translation, authentication, infrastructure and analytics providers for these functions. We do not sell your selected translation text or use it as an advertising audience. We do not use selected text to train our own translation model.

We may disclose information where required by applicable law, to respond to lawful requests, to protect users or the service, or in a business transfer subject to appropriate protections. Providers may process data in countries other than your own. Their policies and applicable agreements govern their processing; we do not make a blanket claim that every provider never logs or trains on data.

5. Storage, retention and security

App translation sessions and comparison results are held in memory while needed for the current workflow; Sayloe does not provide a persistent, user-browsable translation history. Cloud service code includes an encrypted retry/result cache configured with a ten-minute validity window. Expiry prevents normal reuse; physical cleanup, infrastructure logs and backups may outlast that window. This is not a promise that every copy is deleted exactly ten minutes after processing.

Account, device, allowance and operational records are retained as needed to operate accounts, enforce limits, investigate abuse, meet legal obligations and resolve disputes. A fixed deletion schedule for all such records has not yet been established. Hosting, authentication, translation and analytics providers also apply their own retention settings and policies.

We use measures such as HTTPS, Keychain credential storage and encrypted cloud retry results where those features are configured. No storage or transmission method is completely secure. This policy does not imply that selected text never leaves your Mac or that no operational metadata is stored.

6. Your choices and privacy requests

• Choose what text to translate and avoid submitting sensitive information unnecessarily.
• Choose Apple translation where supported if you do not want to use Google cloud translation.
• Revoke Accessibility permission in macOS System Settings to stop the associated capture and replacement capabilities.
• Sign out of cloud services and manage Google authorization in your Google account.
• Use browser privacy settings and Google’s opt-out tools for website analytics.

Depending on your location, you may have rights to request access, correction, deletion, portability, restriction or objection to processing, or withdraw consent where processing relies on consent. Email sayloe@molabuzz.com with your request. We may need to verify your identity without requesting your password. We handle requests under applicable law; some information may need to be retained for security or legal reasons. You may also have the right to complain to your local data protection authority.

7. Children

Sayloe is intended for general productivity use and is not directed to children under 13. If you believe a child has provided personal information to us, contact us so we can review and take appropriate action.

8. Changes to this policy

We may update this policy as the app, services or applicable requirements change. We will update the date at the top and provide additional notice where required. A planned feature described here is not an announcement that it has launched.

9. Contact

For privacy questions or data requests, contact the Sayloe development team at sayloe@molabuzz.com. Website: https://sayloe.com.