Yanchi Privacy Policy
Yanchiii safety, privacy, account and AI-use information.
Yanchi Privacy Policy
Last updated: August 17, 2026
Yanchi is a private journaling, planner, reflection, and cycle-management companion. This policy explains the real data the Yanchi plugin may collect and how it is handled.
Data Yanchi collects
- Account data: name, email address, phone number when provided, password authentication status, password reset support status, and terms/privacy acceptance timestamp.
- Journal data: journal titles, dates, journal text, selected feelings, optional uploaded images, reflection questions, reflection type, AI reflection answers, follow-up conversations, question-guide learning conversations, and saved threads.
- Planner data: daily plans, future tasks, weekly tasks, yearly goals, planner reviews, completed task counts, and saved daily reviews.
- Cycle data: period dates, cycle settings, flow, pain, energy, sleep, mood, body signals, private notes, saved cycle logs, cycle insights, and Ask Yanchi cycle conversations.
- Talk to Yanchiii data: user questions, assistant replies, saved chat titles, dates, and saved conversation history.
- App settings: language preference, reminder settings, voice preference, theme preference, privacy settings, and usage preferences.
- Payment data: if subscriptions, wallet points, Telebirr, card payments, or other payment services are added, payment processors may handle transaction details. Yanchi should not store full card numbers.
- Technical data: device/browser storage, IP address and server logs handled by WordPress/hosting, crash or security logs, and cookies used for login/session security.
Why Yanchi collects this data
Yanchi uses this information to create accounts, protect login access, save journals, run AI reflections, maintain planner and cycle records, show saved conversations, manage points/wallet features, provide support, improve safety notices, and allow export or deletion requests.
Where data is stored
In this plugin version, journal, planner, cycle, image, and saved conversation data is primarily stored in the user’s browser local storage unless server synchronization is later enabled. Local application storage is namespaced per authenticated WordPress account on that browser, with guest data kept in a separate guest namespace, to reduce accidental cross-account exposure on shared devices. Account registration, login, password reset, and related account metadata are stored in WordPress. WordPress hosting may also create security, error, and access logs.
AI providers and prompt processing
When a user deliberately asks for Yanchi reflection, planner guidance, cycle guidance, or chat responses, the current prompt and relevant user-enabled context may be sent to the configured AI provider to generate a response. Cross-feature cycle memory is off by default. This build sends OpenAI Responses API requests with application-state storage disabled (store=false), but the AI provider may still retain limited service or abuse-monitoring data under its API data policy.
Yanchiii memory controls
Users can separately control journal memory, planner memory, reflection memory, and cross-feature cycle context in Settings. These controls determine what past browser-local context may be attached to future AI requests; they do not upload the local library by themselves.
Product and investor analytics
If privacy-safe product analytics is enabled, Yanchiii records content-free activity events such as app opens, journal saves, completed reflections, planner activity, cycle-log saves, AI request status, token counts, and point usage. Investor analytics does not store journal text, reflection answers, cycle notes, chat messages, names, emails, profile photos, raw prompts, or raw IP addresses. Registered-user analytics can be exported or erased through WordPress privacy tools, and the in-app setting can disable new product-analytics events.
Security and encryption
Yanchi should be served only through HTTPS. WordPress stores passwords using WordPress password hashing. Browser-stored app data is controlled by the user’s device/browser and is not automatically encrypted by Yanchi. Server encryption, backups, database protection, and log retention depend on the hosting configuration. For commercial launch, we recommend HTTPS, secure SMTP, updated WordPress, restricted admin access, backups, and server-side encryption if sync is added.
Data sharing
Yanchi does not sell personal data. Data may be processed by WordPress hosting, email delivery/SMTP services, the configured AI provider, payment processors if later added, and support/security tools required to operate the service. Investor/product analytics in this build is first-party and content-free.
Data retention
Local app data remains in the browser until the user deletes it, clears browser storage, changes device/browser, or uses Yanchi deletion/export controls. WordPress account data remains until the user requests deletion or an administrator removes it. Content-free product analytics is automatically removed after the configured analytics retention period (400 days in this build).
User rights: export and deletion
Users can export local Yanchi data from settings, delete local data from the app/browser, and request account or server-side data deletion through the Account and Data Deletion page. Deleting browser data may remove local journals, planner records, cycle logs, and saved chats on that device.
Children and age
Yanchi is not designed as a children’s app and should not be used by children without appropriate guardian consent and local legal compliance.
Contact
For privacy requests, data export/deletion, or questions, contact tedyestif@gmail.com.