日本語

"LabColony" ("the App") respects your privacy. This policy explains what information the App handles and how it is used.

Developer Information

• Developer: Akira Sugiyama (Cedarlab)
• Location: Japan. As this is an individual developer, detailed address information will be disclosed without delay through the contact email when legally required or reasonably requested.
• App: LabColony
• Contact: legal@cedarlab.dev

1. Information Handled on Your Device

If cloud sync is not enabled, the App's record data is stored only on your device. The iOS app uses SQLite. Main data includes:

• Room, rack, and cage information, including names, layouts, status, and notes
• Animal information, including animal code, species, strain, genotype, sex, date of birth, and status
• Animal cage membership history and move history
• Breeding records and death/euthanasia records
• Administration records, procedure records, and body weight records
• Identification data such as ear punches, tail marks, body marks, and tattoos
• Routine tasks, master data, species-specific settings, and display settings
• Local data required for backup and restore

This information is used for recording, viewing, summarizing, CSV export, backup, and restore of research animal colony records. Unless cloud sync is enabled, it is not sent to the developer's servers.

Information you enter about third parties: If you enter personal or confidential information in animal codes, strains, genotypes, procedure details, staff names, notes, or similar fields, please follow your institution's rules and enter only the minimum information required for management.

2. Information Handled by Cloud Sync

When cloud sync is enabled, the App sends sync-target record data to a Supabase cloud environment. This may include the room, rack, cage, animal, breeding, administration, procedure, death, body weight, routine task, master data, and settings information described in Section 1.

Cloud sync is used to share data across multiple devices using the same account or, in the future, through shared lab features. Sync requires a Supabase Auth account. Email address, authentication tokens, user ID, registered device ID, sync status, and entitlement information may also be handled.

Sync data is managed with Supabase Row Level Security, authentication, and sync RPC authorization checks so that it is used only by the logged-in user or shared lab members. If you enable cloud sync, please also follow the data-management rules of your institution or lab.

3. Account Information

Login is required for purchase restore, cloud sync, registered device management, and future lab sharing features. The App uses Supabase Auth and handles email address, authentication tokens, user ID, and related information. You can change your email address or delete your account from the app settings.

When account deletion is performed, the App deletes cloud account-related data and local data on this device. If a network error prevents cloud-side deletion, run account deletion again while online.

4. Information Handled by Third-Party Services

4.1 Google AdMob (Advertising)

The free plan displays ads through Google AdMob. AdMob may handle the following information for ad delivery:

• Identifiers - advertising identifier (IDFA), only when allowed by App Tracking Transparency (ATT)
• Usage data - ad requests, ad impressions, and interactions with the ad SDK
• Location - country or region-level approximate location inferred from IP address
• Diagnostics - crash data, performance data, and technical SDK diagnostics

The App uses the ad SDK according to Google User Messaging Platform (UMP) consent management and the iOS App Tracking Transparency (ATT) permission status. If ATT is not allowed, IDFA cannot be used. In applicable regions, a UMP consent form may be displayed. Paid plans do not display ads.

Google's privacy policy: https://policies.google.com/privacy
Ad personalization settings / opt-out: https://adssettings.google.com/

4.2 Apple App Store / StoreKit

In-app purchases are processed through Apple App Store / StoreKit. The developer does not have access to payment information such as credit card numbers. Refunds are handled by Apple under Apple's policies.

Apple's privacy policy: https://www.apple.com/legal/privacy/

4.3 RevenueCat

The App uses RevenueCat for checking in-app purchase status, restoring purchases, and managing subscription entitlements. RevenueCat handles purchase status, app user ID, product IDs, subscription status, and related information. To associate purchases with the correct account, the App uses the logged-in Supabase user ID as the RevenueCat app user ID.

RevenueCat's privacy policy: https://www.revenuecat.com/privacy/

4.4 Supabase

The App uses Supabase for account authentication, cloud sync, entitlement information, registered device management, and future lab sharing features. When cloud sync is enabled, sync-target data and account-related information are processed on Supabase.

Supabase privacy policy: https://supabase.com/privacy

5. Information the App Itself Does Not Collect

The App itself does not collect the following for unrelated purposes (except for cloud sync described in Section 2, third-party services described in Section 4, and information voluntarily provided by email described in Section 6):

• Device GPS location
• Contacts, photos, calendar, or microphone data
• Patient information for medical or clinical purposes
• Payment information such as credit card numbers

6. Email Support

If you contact legal@cedarlab.dev or support@cedarlab.dev, the following information may be obtained and processed:

• Sender email address
• Name, organization, or similar information included in the sender field or signature
• Email body, environment information, and attachments such as bug report screenshots

Purpose: replying to inquiries, investigating bugs, and handling privacy-rights requests.

Retention: Support and privacy correspondence is retained for up to 12 months after the inquiry is resolved, then deleted. You may request deletion at any time by replying to the thread or contacting legal@cedarlab.dev.

7. Children's Privacy

The App is not directed to children under 13. We do not knowingly collect personal information from children under 13.

8. Data Storage and Deletion

Local data is retained while the app remains installed on your device. Deleting the app deletes the App-related local data on the device. Individual records can also be deleted within the App.

If cloud sync is enabled, cloud sync data is retained as necessary to provide the account and sync features. Account deletion can request deletion of cloud account-related data.

Information held by Google AdMob, Apple, RevenueCat, and Supabase is managed according to each provider's policy. Please refer to each provider's privacy policy for data deletion and restriction options.

9. Rights of Residents in the EEA / UK (GDPR)

The current version of the App is distributed primarily in Japan and the United States. This section applies if distribution is expanded to the EEA / UK in the future or if applicable law requires it.

The data controller for the App is Akira Sugiyama (Cedarlab), an individual developer residing in Japan. To the extent applicable, you may have rights to access, rectify, erase, restrict processing of, object to processing of, or port your personal data, withdraw consent, and lodge a complaint with a supervisory authority. To exercise these rights, please contact the email address in Section 12.

10. Changes to This Privacy Policy

If this policy is updated, the "Last updated" date on this page will be changed. Material changes may also be announced within the App.

11. Governing Law

This policy is governed by the laws of Japan.

12. Contact

Questions about this policy, data deletion requests, or reports of inappropriate ads displayed in the App should be sent to legal@cedarlab.dev.