Privacy policy

• Account identity data supplied through Firebase Authentication, such as your user identifier, email address, and sign-in provider.
• Your source recordings, transcripts, timestamps, categories, preferences, and the technical state needed to sync and recover them.
• Operational records such as checksums, upload receipts, retry state, device-neutral identifiers, diagnostics, and security logs.
• Subscription, allowance, and usage records. Payment-card details remain with Stripe, Apple, or Google and are not stored by Saylog.

We process this data to authenticate you, durably store and synchronize recordings, produce and display transcripts, support playback and search, meter transcription allowance, prevent abuse, diagnose failures, and answer support or deletion requests.

Saylog does not sell your recordings or transcripts, use them for advertising, or add an interpretation layer that profiles their meaning.

These processors receive only the data needed for their role and may process it in other countries under their own security and legal safeguards.

• Google Cloud hosts source audio, PostgreSQL workflow data, and the server infrastructure; Firebase provides authentication.
• Groq is the default speech-to-text processor. xAI can process audio when you deliberately use an alternative or the internal comparison lab.
• Vercel hosts the web interface. Stripe Managed Payments, Apple, or Google process purchases made through their respective channels.

Source audio is retained so you can consult it and so failed transcription can be retried. When you delete a recording, Saylog records the deletion and asynchronously removes its cloud objects; bounded backups and security logs may retain residual data for a limited operational period.

You may ask to access, correct, export, or delete account data by emailing hello@saylog.app from the address associated with the account. We may retain records required for security, fraud prevention, accounting, or law.

Supported clients keep encrypted-device or browser-local journals and cached data so recording and sync can survive interruption. Browser storage can be evicted by the browser; the interface identifies best-effort storage when persistence is unavailable.

Saylog uses authenticated, user-scoped access and immutable object verification. No internet service can promise zero risk, so please protect your device and sign-in account.

We will update this page when the service or its providers materially change. Questions and privacy requests can be sent to hello@saylog.app.