Privacy Policy

This policy describes how SomaTrace (operated by Tsai Cheng En as an individual, "we") collects, uses, and protects data when providing the service.

  1. Our users are mostly manual and somatic practitioners. For the client records a user creates within the service, the user is the collector and controller, and we provide cloud storage and processing only on the user's instructions.
  2. Data we process includes: (a) account data — email, sign-in time, display name, terms-acceptance record, marketing opt-in; (b) payment data — subscription and purchase status, payment transaction identifiers (excluding full card numbers), and, where the user enables online collection, the order number, amount, payment status, and transaction identifier of their clients' online payments (excluding full card numbers); (c) client records created by the user — client basics (mobile number, age band, sex, dominant hand, occupation, exercise habits, injury history, preference and contraindication notes), chief complaints and body observations (regions, symptom qualities, dynamic tests, visceral and fascial observations, self-rated discomfort 0–10), session records and reviews, and AI-generated reports; (d) device and push — device identifier, push token, push preferences; (e) system logs — usage, errors, and AI-call audit records (excluding client content); (f) integration data — when a user connects a LINE Official Account, their own payment gateway, or Google Calendar, the stored connection credentials for those third-party services; (for LINE) the LINE user ID, display name, profile picture, and conversation message content of clients who interact with the user; and (for Google Calendar) the email address and display name of the connected Google account, the names of the selected calendars and the start and end times of their busy periods, plus the event titles and event identifiers of calendars the user owns.
  3. Some client records are health-related sensitive data. We obtain them only when the user actively enters them, process them only to the extent necessary to provide the service, and do not use them for medical diagnosis.
  4. Purposes of collection and processing: account management and authentication, cloud sync, payment processing, customer support, system reliability monitoring, and improvement of the service and its features.
  5. To improve features and content quality, we may de-identify client data (removing fields that directly identify a specific person, such as names, and excluding free-text notes and original chief-complaint text) and analyse only the aggregated statistics and patterns (for example, which body-region and symptom combinations are most common, or feature-adoption rates). Such analysis is performed only in an aggregated form that cannot be traced back to a specific individual, is never used to identify a specific client or user, and is never sold.
  6. "AI summaries & reports" does not call an AI model from this service. The service only assembles the record content the user selects into text (excluding the client's name and contact details, and replacing strings that match the name, phone or email on a best-effort basis); the user copies it into their own ChatGPT account, sends it there, and pastes the reply back into the service. Transmission and processing of that text are governed by the user's agreement with OpenAI and do not pass through this service. Reports that older versions generated with a server-side model (Anthropic or OpenAI) remain available to view, edit and delete; that feature has been retired. A few AI features the service still runs (for example canvas layout suggestions and voice transcription) transmit the content those features need to Anthropic or OpenAI, excluding the client's name and contact details.
  7. To provide the service, we engage the following processors to handle the data necessary for their function: Supabase (cloud database and storage), Anthropic and OpenAI (the few AI features the service still runs), NewebPay (subscription collection for this service, and online collection enabled by the user), LINE (LY Corporation, booking and message delivery), Apple and Google (push notifications), Google (calendar integration, at the user's option), RevenueCat (iOS purchase validation), and Resend (system email). Each processor receives only the data necessary to perform its function and may not use it for other purposes.
  8. Payment information is processed by a third-party payment provider; we do not store full credit-card data.
  9. When a user connects a LINE Official Account, clients may interact with the user and complete bookings through LINE; their LINE user ID, display name, and message content are synced into the service so the user can reply and manage them in the inbox. For such client data, the user is the collector and controller, and we process it only on their instructions. Message delivery is provided by LINE (LY Corporation)'s Messaging API.
  10. A user may connect their own third-party payment gateway to collect deposits or fees from their clients. Clients' online payments are processed by the gateway chosen by the user; we store only the transaction identifier, amount, and payment status, and do not store full credit-card data. For clients' payment data, the user is the collector and we process it only on their instructions.
  11. A user may choose to connect Google Calendar so the service can work out when they are available. Once connected, we store the email address and display name of the connected Google account so the user can tell which account is connected; for the calendars the user selects we read and store the calendar name and the start and end times of busy periods; for calendars the user owns we additionally read and store event titles and event identifiers, solely so the user can tell which event a blocked period belongs to on their own screen. We do not read attendees, locations, or event descriptions. The public booking page shows only that a period is unavailable; it never shows event content or calendar information. If the user also enables writing appointments to a calendar, confirmed appointments (including the client's name as recorded and the service name) are written to the calendar they nominate. When the user disconnects in settings or deletes their account, this account and calendar data is deleted together with the authorisation credentials.
  12. Our use of user data obtained from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements: the data is used only to provide the availability and appointment-writing features described above, is not used for advertising, is not sold, and is not used to train generalized AI models.
  13. Some processors' servers are located outside Taiwan (for example, the United States and Japan). By using the service you understand and consent to the international transfers necessary to provide it; we require processors to adopt reasonable security safeguards.
  14. We use TLS encryption in transit, encryption at rest, and Row Level Security to isolate each user's client records from one another; payment data is handled by the payment provider in encrypted form. Connection credentials for third-party services that a user connects (LINE Official Account, their own payment gateway, Google Calendar) are additionally encrypted at the application layer and never stored in plaintext.
  15. Client and account data are retained for the duration of service use; after a user deletes a client or account, the data is removed from operational systems within a reasonable period (except where retention is required by law or during existing backup-rotation periods).
  16. Users may, within the app or by contacting support, access, correct, export, or delete their data. A client wishing to exercise their rights should contact the user (the collector) they are served by, and we will assist that user.
  17. Users located in the EU or other regions may, to the extent required by local law, exercise rights of access, correction, deletion, restriction of processing, or objection.
  18. The service does not use third-party advertising or behavioural-tracking analytics tools.
  19. In the event of a data breach that may harm rights or interests, we will, in accordance with the law, notify affected parties within a reasonable period and take remedial measures.
  20. If this policy is updated, the changes will be published on this page with an updated "last updated" date; material changes will be separately highlighted.
  21. For questions or to exercise your rights, contact support at support@mail.somatrace.app; operator: Tsai Cheng En.