Privacy Policy

RiseLoop app · Last updated 5 November 2026 · If the Thai and English versions differ, the Thai version prevails.

Softever Company Limited (“we”) develops and operates the RiseLoop app and is the data controller under Thailand’s Personal Data Protection Act B.E. 2562 (PDPA).

1. What we collect

• Account data from Google Sign-In: your email, display name and Google account ID. We do not store your profile picture or access anything else in your Google account.
• Daily targets for energy, protein, carbohydrate, fat and water, and their history. You set them yourself, or the app calculates them from the goal questionnaire.
• Body data you enter: sex, birth date, height and weight log entries. Every field is optional.
• Goal questionnaire answers: activity level, weight goal, preferred pace and the calculated results. Each completed questionnaire is kept as history.
• Whether you are pregnant or breastfeeding: used only to calculate that questionnaire’s targets and never stored.
• Meal logs: food names, portions, date and meal slot, energy and nutrients, and the barcode of a product you log by scanning it, including items you save another way after a scan found no product.
• Label numbers you save with a barcode, and which account sent them — shown to other users who scan the same barcode as product information, never with who sent them.
• Nutrition-label photos taken with a barcode — you take them in label mode; kept temporarily for our team to review (see section 4).
• Label numbers you save for a barcode that already has shared data — kept for at most 30 days, or until our team has reviewed them, so our team can compare them with the shared numbers, without seeing your name or account.
• Daily water intake log: how much plain water you record for each day.
• Daily health journal: the drinking habits, mood, energy, stress, fever or injury, phone use before bed, late meals, bedtime and wake time, step count and activity durations you choose to enter. Every field is optional.
• Steps and sleep from Apple Health or Health Connect: your total step count for each day and your sleep time for each night, synced from Apple Health (iPhone) or Health Connect (Android) only when you choose to connect and allow it (see Data from Apple Health / Health Connect below).
• Journal request receipts: a request identifier and verification digest for each journal change, kept to prevent duplicate commands. They contain no journal answers.
• Food photos and any note you type with them, submitted for calorie estimation.
• Estimate results you have not saved as a meal, from a photo or from text: the food names, components, amounts, energy and nutrients estimated (not the text itself, though food names may match the words you typed). Kept so you can save them as a meal within 1 day, then deleted within 2 days (see section 4).
• A daily count of AI estimates (from photos, from text and label reads), used to enforce the usage allowance.
• Problem reports you send: your description, a screenshot in which your name, email, profile picture, photos, body data, goal questionnaire answers and daily journal values have already been covered with solid boxes on your device (food names, calorie numbers, nutrients, water intake, daily targets, and whether a day is logged and the streak count may still show), the app version and operating system, and your email only if you choose to let the team contact you.
• App error reports (only when you choose to send them): where in the code the error happened (stack frames), the error type name, app version, device model and operating system, RAM, disk, battery and orientation state, the Firebase installation ID, and a random diagnostics ID that we link to your account so the reports can be deleted. This ID is not anonymous. The app records it when it closes unexpectedly or hits an error, keeps it on your device until you choose to send it, then sends it to Google through Firebase Crashlytics (section 3). Set it under Profile → Error reports.
• Feedback you send through Apple’s TestFlight (iOS testers): the text, every screenshot you attach, device model, operating system and app version. These screenshots are not covered on your device, so they may show your name, body data or health log values that were on the screen when you sent them. We copy them from App Store Connect into our own system, keeping your Apple ID email only as a code that cannot be turned back into the email.
• Security records of sign-ins, consent, account deletion, and birth dates entered below the minimum age.

Weight, pregnancy or breastfeeding status, meal data, food photos and your daily health journal may reveal information about your health, so we treat them as sensitive. Body data is visible only to you. Body data, goal questionnaire answers and daily journal values are covered in any screenshot you send from the app (screenshots sent through TestFlight are not covered); food names, calorie numbers, nutrients, water intake, daily targets, and whether a day is logged and the streak count may show in a problem report you choose to send.

Daily journal changes not yet sent are stored as encrypted drafts on your device and sent to your account when you open the app with a working connection. Drafts are removed after acknowledgement. On sign-out or account deletion the app starts removing local drafts. If the app closes before cleanup finishes, an encrypted draft may remain and reappear for the same account; it is never used for a different account.

Data from Apple Health / Health Connect

This part applies only if you choose to connect Apple Health (iPhone) or Health Connect (Android) in the app and allow it in the system prompt. You can keep using RiseLoop without connecting.

• What we read: only your total step count for each day and your sleep time for each night, counting only time asleep, not time in bed before you fall asleep. The app asks for permission to read only; it does not write anything to Apple Health or Health Connect.
• When we read it: only while the app is open: when you connect, when you open or return to the app, when you open the daily journal, when you pull the screen down to refresh, and when you tap try again. It does not read while the app is in the background. When you first connect, it reads up to 30 days back.
• Where it is kept: we send the values, by day, including the name of the app the data came from, such as WHOOP, to be stored in your account on our servers (as described in section 3). In this phase they are not shared with family members or other users. They are not stored in iCloud. On your device, the app keeps, encrypted, only whether you are connected, when it last synced, and the dates and kinds of values this device sent, with no step count or sleep time.
• How we use it: only to show it in your daily journal. We do not use it for advertising, marketing or data mining, do not send it to AI, do not sell it, and do not disclose or share it with anyone else. A screenshot you choose to send in a problem report covers these values with solid boxes.
• Steps you type yourself: you can type your step count yourself in the daily journal. A typed value is shown instead of the synced one. Typed values are kept and deleted like the daily health journal.
• Stopping and deleting: you can stop connecting in Profile and choose to stop syncing only (keeping the synced data) or to stop and delete the synced data. When you are not connected, you can delete the synced data in Profile. Synced data is deleted from our systems at once; values you typed yourself stay. If another device on this account is still connected, it will sync its recent days again. You can also revoke RiseLoop’s permission to read in your device’s Apple Health or Health Connect settings, which stops the app reading but does not delete data already synced.
• Deleting your account: synced data is deleted with your account (section 4).

All photo metadata (EXIF), including location, is removed before a photo is stored. Barcodes are read on your device; camera images in barcode mode never leave it. The app does not collect your location, contacts or audio. It has no ads, no analytics other than the barcode reader’s usage data and the error reports you choose to send, both described in section 3, and no cross-app tracking. Problem reports are sent only when you choose to send one. Error reports are sent only when you choose (ask first, or send automatically). They contain no health data, photos, name, email, account ID or tokens, and we do not use Google Analytics. The app reads the device’s motion sensor only to detect that you shook the phone; it is not stored and never leaves your device.

2. Purposes and legal bases

• Providing the service: accounts and sign-in (contract, PDPA s.24(3)).
• Logging and showing your meals (explicit consent, PDPA s.26, for health-related data).
• Estimating calories and nutrients from your photos or from text you type, when you choose to use it (explicit consent, PDPA s.26, for health-related data).
• To show the steps and sleep synced from Apple Health or Health Connect in your daily journal. This data is not sent to AI and, in this phase, is not shared with family members or other users (explicit consent, PDPA s.26, for health-related data).
• To record and display your daily health entries and calculate consecutive logged days. Journal entries are not sent to AI and, in this phase, are not shared with family members or other users (explicit consent, PDPA s.26, for health-related data).
• Calculating your energy, nutrient and water targets from your body data and questionnaire answers. This runs on our servers and is not shared with anyone (explicit consent, PDPA s.26).
• Reviewing and fixing the problems you report (explicit consent, PDPA s.26, because a screenshot may contain health data).
• Finding and fixing app errors from the error reports you choose to send (legal basis: consent, section 19 PDPA). The choice is optional and does not affect using the app. You can withdraw it at any time under Profile → Error reports → Do not send reports.
• Sharing label numbers as product information, and checking their accuracy from label photos and the numbers other users save (legitimate interest, PDPA s.24(5)).
• Security: preventing abuse, limiting the closed beta to invited users, enforcing the minimum age, and keeping evidence of consent (legitimate interest, PDPA s.24(5)).

We do not sell your data and do not use it for advertising.

3. Who we share it with

During the closed beta, RiseLoop’s servers, database, photo storage and backups run on the company’s own machine at our office in Thailand. The recipients of data from us are as follows.

• Google: for Google Sign-In, for food estimation from a photo or from typed text and for reading nutrition-label photos with Google Gemini (Google deletes them after reading; we keep the photo temporarily, see section 4), and for barcode reading with Google ML Kit. For a photo estimate we send only the metadata-stripped photo and your note; for a typed-text estimate we send only the text you type; never your name, email or account ID. We use Google’s paid service, whose terms state that the data is not used to improve Google’s products. This processing may take place outside Thailand. ML Kit reads barcodes on your device and sends Google neither the image nor the code, but it sends its own usage data (device model and OS, app name and version, performance statistics) so Google can maintain and improve ML Kit. Error reports through Google Firebase Crashlytics, which Google processes on our behalf and which may take place outside Thailand: until you choose to send, the app does not contact Google for this. After you choose, the app contacts Google at three places: the Crashlytics settings, Firebase Installations (for the installation ID) and the Crashlytics report upload. The data is what section 1 lists, including the random diagnostics ID linked to your account and the error type name that Firebase records with every report. We do not use it for advertising.
• Anthropic (the provider of Claude), when the team uses Claude to help analyse problem reports you send (description and screenshots). The sender is shown as a code and we do not send your email or account, but the text and screenshots may contain information that was on your screen or that you typed (may be processed outside Thailand)
• Open Food Facts: an open food product database. When a product you scan is not yet in our database, our server sends only its barcode to look it up, never anything about you.
• Other users see label numbers you saved with a barcode as product information, without your name or account.
• Cloudflare: hosts riseloop.app.
• Google Workspace: the email provider for riseloop.app, when you write to an address in section 9.
• Authorities, when required by law.

Authorised Softever administrators can see only users’ email, display name and sign-up date, the problem reports you send, the product label numbers users share, the label photos kept for review, and the numbers other users saved for the same barcode, without seeing the sender’s name or account. A report shows the sender as a code, not a name or email, unless you choose to be contacted. Feedback sent through TestFlight always shows the sender as a code. Label numbers never show who sent them. Administrators cannot see your meal logs, daily journal, synced steps and sleep, or photos, except what appears in a screenshot you send and the label photos kept for review. Every time a report is opened it is logged, and so is every correction, hide or unhide of label numbers. Every time a label is opened or reviewed it is logged.

4. Retention

• Account data, meals and meal photos: kept until you delete them or your account.
• Body data, weight log entries and questionnaire history: kept until you delete that entry in the app or delete your account.
• Target history: kept until you delete your account.
• Daily water intake log: kept until you delete your account.
• Daily health journal: kept until you delete that day’s entry or your account. Deleting a day removes its answers. Request identifiers and verification digests are retained until account deletion to prevent duplicate commands. These receipts do not contain journal answers.
• Steps and sleep synced from Apple Health or Health Connect: kept until you delete the synced data in Profile or delete your account. Stopping sync alone does not delete data already synced. When you delete, the synced data is deleted from our systems at once, but if another device on this account is still connected, it will sync its recent days again.
• Problem reports: kept until the team deletes that report or you delete your account.
• Feedback through TestFlight: kept until the team deletes it, you delete the account that uses the same email as your Apple ID, or you ask us by email to delete it (we delete it both in our system and in App Store Connect).
• Error reports. Google keeps reports for 90 days before it starts deleting them. When you choose not to send reports, or delete your account, we ask Google to delete the reports tied to your diagnostics ID and follow up on the request. Deletion at Google is completed within 30 days, which is longer than the 7 days for the rest of your account data.
• Photos and estimate results you never save as a meal: photos are deleted immediately if the estimate fails. If an estimate from a photo or from text succeeds but you do not save it, its photos and result are deleted within 2 days.
• Nutrition-label photos: deleted within 24 hours if not saved. If the numbers are shared, or differ from the shared numbers, kept until our team has reviewed them and for at most 30 days, and deleted with your account.
• Label numbers saved for a barcode that already has shared data (the copy our team compares): at most 30 days, or until our team has reviewed them, and deleted with your account.
• When you delete your account: all of the above is deleted within 7 days, except the records listed next.
• Kept after account deletion, for security, abuse prevention and evidence of consent:
  • Records of sign-ins, consent, account deletion and below-minimum-age birth dates, in pseudonymous form (your email is stored only as a keyed hash), for 1 year.
  • The email address your beta invitation was sent to, until the closed beta ends.
• Product label numbers you shared with a barcode stay as product information, linked to no account. Label numbers that are not shared are visible only to you in the app (our team sees the copy kept for comparison, as above, without your name or account) and are deleted with your account.
• Database backups: expire within 7 days.

5. Deleting your account

In the app, go to Profile → Delete account. To request deletion without the app, see riseloop.app/account-deletion.

Deleting your account also asks Google to delete your error reports (section 4).

6. Security

All data is sent over encrypted connections (HTTPS). Access is limited to staff who need it, and health data is never written to system logs.

7. Your rights

Under the PDPA you may:

• access your data and get a copy of it
• have your data transferred to another service
• have your data corrected
• have your data deleted
• have its use restricted
• object to its processing
• withdraw consent at any time; this does not affect processing already carried out
• complain to Thailand’s Personal Data Protection Committee

Contact us using the details in section 9 to use any of these rights. We respond within 30 days.

8. Minors

RiseLoop is intended for users aged 20 and over (the age of majority in Thailand). We do not knowingly collect data from minors. If you enter a birth date under 20, the date is not saved, but we record that an under-age date was entered so that our staff can review the account. If we learn that an account belongs to a minor, we delete it and tell you.

9. Contact

Softever Company Limited (Head office)
44/21 Soi Ladprao 15 Yaek 11, Chomphon, Chatuchak, Bangkok 10900, Thailand
Tax ID 0105554136728
+66 2 227 0645

• Privacy and personal data, including requests to exercise your rights and to delete your account: privacy@riseloop.app
• Help with using the app: support@riseloop.app
• Reporting a vulnerability or security incident: security@riseloop.app

Mail to all three addresses reaches Softever’s RiseLoop team.

10. Changes

If we change how we collect or use data, we will update this page and the date at the top. We will notify you in the app before any material change takes effect.

11. Change history

This list records what each round changed. The text in force is the content above on this page.

5 November 2026

• Error reports. If you choose to send error reports (set under Profile; optional; it does not affect using the app), the app sends them to Google through Firebase Crashlytics: where in the code the error happened, app version, device model and operating system, RAM, disk, battery and orientation state, the Firebase installation ID, and a random diagnostics ID that we link to your account so the reports can be deleted. It is not anonymous. No health data, photos, name or email. Until you choose, the app does not contact Google for this. Google keeps reports for 90 days and may process them outside Thailand. When you choose not to send reports or delete your account, we ask Google to delete your reports; this is completed within 30 days.

3 November 2026

• Data from Apple Health / Health Connect. When you connect, we read your daily step count and nightly sleep time (up to 30 days back when you first connect) to show in your daily journal. We do not use it for advertising, do not send it to AI and do not share it with others. You can stop connecting in Profile, choosing to keep or delete the synced data. The data is kept until you delete it or delete your account. You can type your step count yourself in the daily journal; a typed value is shown instead of the synced one.

2 November 2026

• TestFlight feedback. Added feedback sent through TestFlight: we keep a copy of the text and screenshots (not covered), and we do not keep the email.
• Claude helps analyse problem reports. The team uses Anthropic’s Claude to help analyse problem reports you send (description and screenshots). The sender is shown as a code and we do not send your email or account, but the text and screenshots may contain information that was on your screen or that you typed (may be processed outside Thailand).

30 October 2026

• AI search. The text you type to say what you ate is sent to Google Gemini to estimate energy and nutrients. We do not send your account details (name, email, account ID). This processing may take place outside Thailand.
• Unsaved estimates. Photos and estimate results (food names, components, amounts and nutrients) from a photo or from text that you did not save as a meal are deleted within 2 days, instead of being kept until you delete your account. We do not store the text itself, but food names in the result may match the words you typed.
• Where data is kept. Revises section 3: during the closed beta, the servers, database, photo storage and backups run on the company’s own machine at our office in Thailand, not on Amazon Web Services as the previous version said.

29 October 2026

• Daily health journal. We keep the daily health entries you choose to enter: drinking, mood, energy, stress, fever or injury, phone use before bed, late meals, bedtime and wake time, and activities, to show them to you and count consecutive logged days. They are not sent to AI and, in this phase, are not shared with family members or other users. Changes not yet sent are kept as an encrypted draft on your device until they are sent. Entries are kept until you delete that day or your account; request identifiers that prevent duplicate sends, which contain no answers, are kept until you delete your account.
• Problem reports. Follows up “Problem reports” from 9 October 2026: screenshots in a report also cover daily journal values, but still show whether a day is logged and the streak count.
• Food label numbers. Follows up “Food label numbers” from 9 October 2026: label photos taken with a barcode are kept temporarily for our team to review. If not saved, they are deleted within 24 hours; if shared, or if the numbers differ from the shared numbers, they are kept for at most 30 days. Our team sees the photos and numbers, but not the sender’s name or account.

9 October 2026

• Problem reports. When you send a problem report, we keep your description, the app version, the operating system, and a screenshot in which your name, email, photos, body data and goal questionnaire answers are already covered on your device. Food names, calories, nutrients, water intake and daily targets may still show. Authorised administrators can open reports and see the sender as a code, unless you choose to be contacted by email. Reports are kept until the team deletes them or you delete your account. (Revised again on 29 October 2026.)
• Food label numbers. Nutrition label numbers you check and save for a product with a barcode may be shown to other users who scan the same barcode, never with who sent them. Numbers shared as product information stay after you delete your account, linked to no account, and the team may correct or hide them. Label photos are sent to Google Gemini to read the numbers, then deleted (this may take place outside Thailand) (followed up in the 29 October 2026 round).

7 October 2026

• Barcode scanning. Meal logs keep the barcode of a product you scan. For a product we do not have yet, we send only the barcode to Open Food Facts. The barcode reader, Google ML Kit, runs on your phone and sends its own usage data to Google.

5 October 2026

• Water log. We keep how much water you log each day, until you delete your account.

1 October 2026

• Basis for meal logs. Logging and showing your meals rests on your explicit consent (PDPA s.26), because it is health-related data.
• Records kept as evidence. Besides sign-ins and account deletion, we record consent, and a birth date entered below the minimum age without keeping that birth date. These records are kept for 1 year in a form that does not directly identify you.

28 September 2026

• First version. First published.