Privacy policy

Sayfolio is operated by individual developer Chen YiChieh. Contact: lawliet357@gmail.com. This policy covers the app and support website. Policy version: 2026-09-18. From 1.0.16, AI data-sharing permission is saved per account; older versions still request operation-specific consent. The data-handling policy version remains 2026-09-18; the account-permission disclosure version is 2026-09-20.

Recordings, imports, transcripts, notes and revisions are stored on your device. Recording, playback, reading, editing and exporting do not start AI sharing. Imported videos are processed locally to extract audio; the original video is not sent to Gemini. Manual ZIP backups use the system Files picker with your chosen device, iCloud Drive or enabled Google Drive file provider. This is not automatic sync or direct Google Drive OAuth access. ZIP files exclude keys, sessions and credit balances, and are not password-encrypted. Your chosen storage provider's terms apply; you manage those copies.

Sayfolio's backend runs on Google Cloud in us-central1, United States, for computation and temporary storage. Google Gemini is the separate AI recipient generating transcripts and notes. Content may cross national borders; Google's processing is not guaranteed to stay in the backend region. Both hosted and BYOK processing pass through Sayfolio, not directly from the device to Google.

• Transcription: the selected audio and necessary language/processing settings, to create a transcript.
• Notes: the selected transcript revision, template and custom instructions, to generate notes. Notes-only generation or regeneration does not resend original audio.
• Combined processing: the corresponding data for each stage above.

Content may include voices, names or other personal information. Only share content you are authorized to use.

From 1.0.16, the first AI processing request displays the data, recipients, purposes and retention, with an initially unchecked confirmation that you are 18 or older and will only upload content you have permission to process. Selecting Agree and get quote explicitly permits Sayfolio’s US backend and Google Gemini to receive recordings, transcripts, processing settings and custom instructions for transcription and AI notes you request with that account. Permission is remembered for the same account, policy, recipients and purposes; it does not authorize automatic uploads of other content. View or withdraw it in Settings → Privacy → AI data-sharing permission. Withdrawal prevents starting new processing with old quotes and requires agreement again next time; it does not automatically cancel jobs already started. Local recordings and saved results remain available. Changes to the disclosed policy, recipients or purposes require renewed agreement.

Every operation still needs a quote and your Start processing confirmation before content upload, job creation or credit reservation. A quote sends settings and custom instructions but does not start audio/transcript processing or reserve credits. BYOK stages use no platform credits; Google bills separately. Changed content/settings invalidate the quote while account permission remains. Cancelling a quote does not withdraw account permission or undo settings already shared. Job cancellation stops subsequent work but cannot recall data already received by Google. Successfully delivered stages remain chargeable at the confirmed rate; unfinished reservations are released. Partial results remain until acknowledgement or expiry cleanup. Declining leaves local features available. Authentication and service-configuration requests are distinct from AI content transmission.

Before a key is transmitted, the app requests consent for encrypted storage on Sayfolio's backend and authentication/calls to Google Gemini. Key validation does not send recordings. Keys are retained until removed or the account is deleted. Existing keys need the new confirmation before further processing. BYOK requires your declaration that the Gemini project's Cloud Billing account is active. A green validation check does not verify billing; stop using a key if billing is disabled.

Hosted processing uses paid Gemini. The Gemini terms exclude paid prompts/responses from product improvement, but allow security/legal retention and international processing. The incorporated processor addendum provides instructed processing, confidentiality, access controls, encryption and incident notification. Google Cloud infrastructure is covered separately by its Cloud addendum. These safeguards are our third-party protection basis, not promises of zero retention, no human access or US-only processing. BYOK billing status remains a user declaration, not technical verification.

Account permission is stored separately with account, permission and policy versions, time, recipients, purposes and withdrawal status, without content or keys. It remains during the account’s lifetime; withdrawal immediately invalidates it, and account deletion removes it. Agreement after withdrawal creates a new permission ID and cannot revive old quotes.

Local results remain under your control. Sayfolio deletes corresponding temporary content after the app verifies delivery and acknowledges it (ACK). An approximately 23-hour deadline is set when temporary objects or results are written; a new processing stage or note generation sets a new deadline for that stage's content. For unacknowledged content, scheduled cleanup targets removal within 24 hours and retries failures. This is not cloud backup and does not control Google's separate retention. Transfers use HTTPS and backend storage is encrypted.

Consent receipts contain account linkage, policy version, time, scope, recipients, source/operation identifiers, lifecycle timestamps and content/settings hashes, not source text or keys. They are removed by cleanup 30 days after an operation's terminal state is recorded; unused receipts expire after 30 days. Account deletion removes them. Paid-project declaration version/time remain with the credential.

Operational records include request paths, IP addresses, time, status, duration, sizes, error codes and model usage. App logs do not contain recordings, transcripts, prompts, keys or consent receipts. General Google Cloud logs retain 30 days; required audit logs retain 400 days.

Sign in with Apple identifiers associate accounts, jobs, regions and credits. The app does not request Apple name/email scopes. Tokens needed for Apple authorization revocation are encrypted. Apple processes payments; Sayfolio receives no card/bank details. Transaction identifiers, verified status, balance, usage and refund records remain while the account exists for settlement, duplicate prevention and disputes. Sandbox and production credits are separate.

You can remove keys, delete local notes or delete the account in the app. Account deletion clears associated jobs, keys, consents and account records. If Apple authorization revocation fails, the encrypted token remains for retry until successful. Minimal transaction identifiers, account hashes and deletion/notification records have no automatic expiry, to prevent replayed purchases; they contain no audio/transcripts. Hashes are not necessarily anonymous. Your separate cloud backups are not deleted.

Contact us to request access, correction, restriction or deletion. We verify identity and explain required retention; do not send passwords, keys or private recordings. The tool is for professional use by adults 18 and over, not medical diagnosis. There is no public social platform, advertising SDK or cross-app tracking, and we do not sell personal data. Cloudflare Pages serves the website and may process connection/security data. Email support processes the information you choose to send. Material changes to purposes or recipients will be disclosed and consent renewed where applicable.

The website stores your manually selected display language in this browser; choosing Auto clears that preference. The feedback form prepares email content in your browser and does not submit it automatically. Opening your mail app or Gmail transfers the entered information into a draft in your chosen mail service for you to review and send.