Privacy Policy
Privacy Policy
XESEEC Privacy Policy
XESEEC Privacy Policy
Effective Date: October 28, 2026
Last Updated: November 4, 2026
Effective Date: October 28, 2026
Last Updated: November 4, 2026
Privacy and Support Contact: support@xeseec.com
Privacy and Support Contact: support@xeseec.com
XESEEC respects your privacy and is committed to handling personal and wellness information responsibly.
This Privacy Policy explains how the XESEEC Android application (“XESEEC,” “the App,” “we,” “us,” or “our”) accesses, uses, stores and shares information.
XESEEC respects your privacy and is committed to handling personal and wellness information responsibly.
This Privacy Policy explains how the XESEEC Android application (“XESEEC,” “the App,” “we,” “us,” or “our”) accesses, uses, stores and shares information.
1. About XESEEC
XESEEC is a wellness tracking and informational application.
It helps users record and review information such as food, body composition, activity, sleep, daily wellness observations and personal journal entries.
XESEEC is not intended to diagnose, treat, cure or prevent disease and does not replace professional medical advice, diagnosis or treatment.
XESEEC is a wellness tracking and informational application.
It helps users record and review information such as food, body composition, activity, sleep, daily wellness observations and personal journal entries.
XESEEC is not intended to diagnose, treat, cure or prevent disease and does not replace professional medical advice, diagnosis or treatment.
2. Information You May Record
Depending on how you use the App, XESEEC may process information including:
food and nutrition records;
body composition measurements;
activity and post-meal activity;
sleep information;
daily wellness observations such as energy, digestion and stress;
personal journal entries;
blood pressure or blood glucose values entered by the user;
profile settings used to support wellness summaries; and
practitioner information or consultation notes entered during a consultation.
You decide what information you enter into the App.
Depending on how you use the App, XESEEC may process information including:
food and nutrition records;
body composition measurements;
activity and post-meal activity;
sleep information;
daily wellness observations such as energy, digestion and stress;
personal journal entries;
blood pressure or blood glucose values entered by the user;
profile settings used to support wellness summaries; and
practitioner information or consultation notes entered during a consultation.
You decide what information you enter into the App.
3. Local Storage
In the current XESEEC beta, user wellness records are stored locally on the user’s device using the App’s local database and application preferences.
XESEEC may use a separate backend service solely to validate participating clinic subscriptions and Clinic Partner access. Under the current app architecture, user wellness records remain stored locally on the user’s device and are not stored in the Clinic Subscription Registry.
Because the current service is primarily local to your device, XESEEC cannot remotely access or remotely delete information stored only on your device.
The Clinic Subscription Registry is not intended to store user wellness records, body composition data, food records, sleep data, blood pressure or blood glucose records, journals, practitioner notes, Clinic PDFs, or other patient-level health information.
Clinic subscription validation may process limited business metadata such as clinic identifier, clinic name, subscription status, plan and expiration date.
In the current XESEEC beta, user wellness records are stored locally on the user’s device using the App’s local database and application preferences.
XESEEC may use a separate backend service solely to validate participating clinic subscriptions and Clinic Partner access. Under the current app architecture, user wellness records remain stored locally on the user’s device and are not stored in the Clinic Subscription Registry.
Because the current service is primarily local to your device, XESEEC cannot remotely access or remotely delete information stored only on your device.
The Clinic Subscription Registry is not intended to store user wellness records, body composition data, food records, sleep data, blood pressure or blood glucose records, journals, practitioner notes, Clinic PDFs, or other patient-level health information.
Clinic subscription validation may process limited business metadata such as clinic identifier, clinic name, subscription status, plan and expiration date.
4. Voice Input and Speech Recognition
XESEEC may allow voice input using Android/system speech-recognition services.
Speech recognition may be processed by Android, the device manufacturer, or another speech-recognition provider according to that provider’s settings and privacy practices.
XESEEC receives and stores the resulting transcription text used for the selected App feature.
XESEEC does not intentionally save a raw audio recording of your voice as part of its own user records.
We do not represent that speech recognition is always processed offline.
XESEEC may allow voice input using Android/system speech-recognition services.
Speech recognition may be processed by Android, the device manufacturer, or another speech-recognition provider according to that provider’s settings and privacy practices.
XESEEC receives and stores the resulting transcription text used for the selected App feature.
XESEEC does not intentionally save a raw audio recording of your voice as part of its own user records.
We do not represent that speech recognition is always processed offline.
5. Health Connect
XESEEC may request permission to read supported information from Health Connect, currently including supported step and sleep information.
XESEEC’s current Health Connect integration is read-only.
XESEEC does not write wellness records back to Health Connect.
Health Connect information is used to provide user-requested wellness tracking and review features within the App.
XESEEC may request permission to read supported information from Health Connect, currently including supported step and sleep information.
XESEEC’s current Health Connect integration is read-only.
XESEEC does not write wellness records back to Health Connect.
Health Connect information is used to provide user-requested wellness tracking and review features within the App.
6. Reports and PDF Sharing
XESEEC can generate Personal and Clinic wellness reports locally on the user’s device.
When you choose to share a PDF, XESEEC uses Android’s sharing interface so that you can select the receiving application or destination.
XESEEC does not automatically send PDFs to a clinic, practitioner or XESEEC server.
Information may leave your device when you intentionally share it through another application. The receiving application’s privacy practices then apply to that copy.
XESEEC can generate Personal and Clinic wellness reports locally on the user’s device.
When you choose to share a PDF, XESEEC uses Android’s sharing interface so that you can select the receiving application or destination.
XESEEC does not automatically send PDFs to a clinic, practitioner or XESEEC server.
Information may leave your device when you intentionally share it through another application. The receiving application’s privacy practices then apply to that copy.
7. Personal Journal and Daily Notes
Personal journal entries (“나의 기록”) and daily notes (“오늘 한마디”) are intended as private user records.
They are not automatically included in XESEEC Clinic reports.
Users should review the contents of any report before sharing it.
Personal journal entries (“나의 기록”) and daily notes (“오늘 한마디”) are intended as private user records.
They are not automatically included in XESEEC Clinic reports.
Users should review the contents of any report before sharing it.
8. Practitioner Notes
During an in-person consultation, practitioner information and notes may be entered into XESEEC for use in generating the Clinic report.
In the current beta, these notes are used locally for report generation and are not automatically uploaded to an XESEEC server.
The user controls whether a resulting report is shared.
During an in-person consultation, practitioner information and notes may be entered into XESEEC for use in generating the Clinic report.
In the current beta, these notes are used locally for report generation and are not automatically uploaded to an XESEEC server.
The user controls whether a resulting report is shared.
9. Data Sharing
Under the current app architecture, user wellness records remain stored locally on the user’s device. A separate backend service may be used solely to validate participating clinic subscriptions and Clinic Partner access, rather than to receive or store user wellness records.
XESEEC does not sell your personal wellness information.
Information may be disclosed outside the App when:
you intentionally share a PDF or other content using Android’s sharing functions;
Android/system services process information required for a feature such as speech recognition or Health Connect; or
disclosure is required or authorized by applicable law.
Services outside XESEEC may have their own privacy policies and data-handling practices.
Under the current app architecture, user wellness records remain stored locally on the user’s device. A separate backend service may be used solely to validate participating clinic subscriptions and Clinic Partner access, rather than to receive or store user wellness records.
XESEEC does not sell your personal wellness information.
Information may be disclosed outside the App when:
you intentionally share a PDF or other content using Android’s sharing functions;
Android/system services process information required for a feature such as speech recognition or Health Connect; or
disclosure is required or authorized by applicable law.
Services outside XESEEC may have their own privacy policies and data-handling practices.
10. Backup and Device Transfer
XESEEC configures Android backup and device-transfer rules to exclude the primary XESEEC user database and user-profile preferences from supported Android cloud backup and device-to-device transfer mechanisms.
These controls apply to XESEEC’s configuration and do not control independent copies that a user has intentionally exported or shared.
XESEEC configures Android backup and device-transfer rules to exclude the primary XESEEC user database and user-profile preferences from supported Android cloud backup and device-to-device transfer mechanisms.
These controls apply to XESEEC’s configuration and do not control independent copies that a user has intentionally exported or shared.
11. Data Retention
Locally stored XESEEC data generally remains on the user’s device until the user:
deletes an individual record where deletion is available;
uses Delete All Data / 모든 데이터 삭제;
clears the App’s storage through Android; or
uninstalls the App, subject to Android’s operating-system behavior.
XESEEC does not currently maintain a remote copy of the user’s locally stored wellness database.
Locally stored XESEEC data generally remains on the user’s device until the user:
deletes an individual record where deletion is available;
uses Delete All Data / 모든 데이터 삭제;
clears the App’s storage through Android; or
uninstalls the App, subject to Android’s operating-system behavior.
XESEEC does not currently maintain a remote copy of the user’s locally stored wellness database.
12. Delete All Data
XESEEC provides a Delete All Data / 모든 데이터 삭제 function in Settings.
This function removes supported XESEEC user records and profile information stored by the App.
It does not delete:
data stored in Health Connect;
information stored by other applications;
copies of PDFs or information that you previously shared or saved outside XESEEC.
Because current wellness records are stored locally, XESEEC cannot remotely perform this deletion on your device.
XESEEC provides a Delete All Data / 모든 데이터 삭제 function in Settings.
This function removes supported XESEEC user records and profile information stored by the App.
It does not delete:
data stored in Health Connect;
information stored by other applications;
copies of PDFs or information that you previously shared or saved outside XESEEC.
Because current wellness records are stored locally, XESEEC cannot remotely perform this deletion on your device.
13. Accounts
The current XESEEC beta does not require an XESEEC user account or login.
Accordingly, there is currently no separate XESEEC cloud account to delete.
The current XESEEC beta does not require an XESEEC user account or login.
Accordingly, there is currently no separate XESEEC cloud account to delete.
14. Security
XESEEC uses platform and application-level safeguards appropriate to the current local-storage architecture, including Android application sandboxing and configured backup exclusions.
No method of electronic storage or processing can be guaranteed to be completely secure.
XESEEC does not claim that its local database uses SQLCipher or equivalent database-level encryption unless such protection is specifically implemented in a future version.
XESEEC uses platform and application-level safeguards appropriate to the current local-storage architecture, including Android application sandboxing and configured backup exclusions.
No method of electronic storage or processing can be guaranteed to be completely secure.
XESEEC does not claim that its local database uses SQLCipher or equivalent database-level encryption unless such protection is specifically implemented in a future version.
15. Children
XESEEC is not designed as a service specifically directed to children.
If future versions introduce features specifically intended for children, this Privacy Policy and related controls will be updated as required.
XESEEC is not designed as a service specifically directed to children.
If future versions introduce features specifically intended for children, this Privacy Policy and related controls will be updated as required.
16. Changes to This Privacy Policy
XESEEC may update this Privacy Policy as the App, its integrations or its services change.
The updated policy will show a revised “Last Updated” date.
Material changes to how personal or sensitive information is handled may also be communicated within the App or through other appropriate means.
XESEEC may update this Privacy Policy as the App, its integrations or its services change.
The updated policy will show a revised “Last Updated” date.
Material changes to how personal or sensitive information is handled may also be communicated within the App or through other appropriate means.
17. Contact Us
For questions, concerns or requests relating to privacy or support, contact:
XESEEC
Users in British Columbia may also have rights under applicable privacy legislation, including British Columbia’s Personal Information Protection Act.
For questions, concerns or requests relating to privacy or support, contact:
XESEEC
Users in British Columbia may also have rights under applicable privacy legislation, including British Columbia’s Personal Information Protection Act.