Skip to content
Yerki
How it worksPrivacySupportRequest access
Menu
How it worksPrivacySupportRequest access

Trust

Privacy

This policy explains the information Yerki needs to provide professional memory, where it is processed and the choices available during private beta.

Last updated 16 July 2026

Who this policy is for

This policy applies to the Yerki private-beta website, web workspace and forthcoming native iPad beta. Yerki is still in development. Material changes to the product or its processors will be reflected here before a broader release.

Information Yerki handles

Depending on the features you use, Yerki may handle:

  • account email, user identifier and authentication records;
  • Memory titles, writing, visual documents and searchable canvas text;
  • audio recordings and timestamped transcript segments;
  • files, images and other attachments;
  • actions, decisions, risks and evidence references derived from your content;
  • projects, tags, people or topics you add or that Yerki identifies from your content;
  • local save, sync, error and security metadata needed to operate and protect the service.

Yerki does not include advertising, cross-site tracking, behavioural profiling or a marketing analytics platform on this website.

Why information is used

Information is used to authenticate your account, save and synchronise your Memories, play recordings, produce transcripts, search your own content, return supporting evidence, operate requested intelligence features, provide support and protect the service.

Yerki does not sell your content and does not use it for advertising.

Local device storage

The web workspace is local-first. Current work is saved in browser storage before cloud synchronisation. The native app is designed to use protected app storage and local files. Local data may remain on a device until you remove it, clear the browser profile or complete a supported deletion flow.

Clearing browser data can remove local-only work that has not successfully synchronised. Yerki shows actionable offline or failure states when it can verify them, but private-beta software may still contain defects.

Cloud sync and private storage

When cloud sync is enabled, Yerki uses Supabase for authentication, database storage and private object storage. User-owned rows are protected by ownership policies, and recordings and attachments are stored in private buckets under authenticated user paths. Signed URLs may be issued for time-limited upload or playback after ownership checks.

Transcription and intelligence

When you use transcription or provider-backed intelligence, the relevant audio, writing or evidence may be sent through Yerki’s server to OpenAI for processing. Provider credentials remain server-side. OpenAI states that API inputs and outputs are not used to train its models by default unless the customer opts in, and that API data may be retained for abuse monitoring under its applicable controls.

Yerki may store the resulting transcript, evidence links and structured items in your account so they remain available with the Memory. AI output can be incomplete or wrong and should be checked against the linked source.

Service providers

Confirmed infrastructure providers currently include Vercel for website and server hosting, Supabase for authentication and data services, OpenAI for requested transcription or intelligence processing, and Apple for future TestFlight distribution and native platform services. Each provider processes information under its own terms and Yerki’s service configuration.

Security

Yerki uses authenticated accounts, encrypted transport, private storage, server-side secrets and user-ownership controls. No internet service can promise absolute security. Please report a suspected vulnerability through the contact on the Security page.

Retention and deletion

Yerki retains account and Memory data while needed to provide the private beta, resolve support or security issues and meet legal obligations. Local device copies and provider backups can take time to expire after deletion.

Per-Memory removal exists in parts of the current product. Safe, complete server-side account deletion is not yet finished and remains an App Store release blocker. See Account deletion for the current limitation and support route.

Your choices and rights

You can ask for access, correction, export or deletion of personal information by contacting privacy@yerki.app. Yerki may need to verify that the request comes from the account holder. Available rights depend on where you live; this policy does not replace legal advice.

International processing

Yerki’s providers may process information in countries other than your own. Appropriate transfer safeguards and final data-region choices require founder and legal review before public launch.

Children

Yerki is a professional product and is not directed to children. The private beta is not intended for anyone under 16.

Changes

This policy will be updated when Yerki’s product, providers or legal obligations change. The date above identifies the current version.

Contact

Privacy questions can be sent to privacy@yerki.app. General support is available at support@yerki.app.

Yerki

Capture the meeting. Keep the thinking.

PrivacyTermsSecuritySupportAccount deletionTestFlightContact

© 2026 Yerki. Private beta.

No advertising, tracking pixels or behavioural analytics.