External Transmission of User Information

日本語

Effective date: September 8, 2026

This English translation is provided for convenience. The Japanese version is the official text, and in the event of any inconsistency the Japanese version prevails.

fridge (the “Service”) does not include information collection modules for advertising or behavioural advertising, such as advertising SDKs or advertising analytics SDKs.

To improve the quality of the Service, however, usage information is sent from users’ devices to the Operator’s server. The Operator uses infrastructure supplied by Cloudflare, Inc. for this processing, so the information reaches Cloudflare. Information is also sent to external providers for app update delivery, purchase management, authentication, data storage and similar functions.

Under Article 27-12 of Japan’s Telecommunications Business Act, the Operator discloses the information transmitted, its recipients and its purposes of use below.

1. User information transmitted

(1) Transmission for usage analytics

ItemDetails
Information transmittedTypes of screens viewed; names and timestamps of operation events; app version; device platform (iOS/Android); a random identifier generated on the device for each period of use (unrelated to the user ID or any device identifier, and replaced with a different value once the app has been closed for a while); the authentication token used to authenticate the transmission; and the IP address that necessarily accompanies the communication
RecipientThe Operator’s server (using Cloudflare, Inc. in the United States as server and analytics infrastructure)
Purposes of useOperator: to analyse use of the Service and improve its quality. Cloudflare, Inc.: to provide server and analytics infrastructure to the Operator (Cloudflare Privacy Policy)

Names, email addresses and the content of posts are not sent in this transmission. The information sent is used only to aggregate and analyse usage, and becomes unavailable three months after it is recorded.

(2) Transmission to check for app updates

ItemDetails
Information transmittedDevice platform; app version (the unit to which an update applies); update channel; identifier of the currently applied update; a random identifier generated and stored on the device for each app installation (EAS Client ID, which is unrelated to the user ID or a device-specific ID and is lost when the app is deleted); and the IP address that necessarily accompanies the communication. If the app terminated abnormally during the previous launch, an error message indicating the cause (up to the first 1,024 characters) is also sent.
Recipient650 Industries, Inc. (Expo, United States)
Purposes of useOperator: to deliver app updates (patches) and understand defects in delivered updates. 650 Industries, Inc.: to provide its app update delivery service (Expo Privacy Policy)

The Operator does not add custom headers containing user information to this transmission.

(3) Transmission to manage purchase status

ItemDetails
Information transmittedUser ID (the Service account ID); App Store / Google Play purchase receipt information; device locale (language and region) and currency code; device platform; and the IP address that necessarily accompanies the communication
RecipientRevenueCat, Inc. (United States)
Purposes of useOperator: to manage the purchase status of paid plans, fridge ticket packs and photobooks (receipt verification and determining purchase/cancellation status), and to aggregate and analyse purchase activity. RevenueCat, Inc.: to provide purchase management and purchase analytics services to the Operator (RevenueCat Privacy Policy)

The Operator does not configure RevenueCat to receive contact information such as email addresses or advertising identifiers (IDFA / advertising ID). Purchase history is recorded against the user ID described above.

2. Transmissions necessary to provide the Service (for reference)

The following transmissions occur, only to the extent necessary, when the corresponding feature is used. They are organised by purpose rather than provider because the purpose, information and storage destination may differ even for the same provider. The Operator considers these transmissions truly necessary to provide the Service and therefore exempt from the notification and disclosure requirements under Article 27-12(1) of the Telecommunications Business Act, but lists them here for transparency.

TriggerInformation transmittedRecipientPurpose
Account registration or sign-inEmail address, password, authentication token and IP addressGoogle LLC (Firebase Authentication, United States)Identity verification and session maintenance
Viewing and synchronising posts, comments and GroupsPost text, comments, reactions, tags, Group and membership information, and user IDGoogle LLC (Cloud Firestore, United States)Data storage and synchronisation
Uploading or viewing photos and videosPhoto or video file, signed token used for viewing, user ID and IP addressCloudflare, Inc. (United States)Media storage and delivery
Enabling push notificationsPush notification token and device platformGoogle LLC (Firebase Cloud Messaging, United States)Notification delivery
App launch (misuse prevention)Token attesting to the integrity of the device and appApple Inc. (App Attest, with DeviceCheck as a fallback on unsupported devices) / Google LLC (Play Integrity)Preventing access by tampered apps and automated misuse
Communication with the Operator’s server (photo/video transfers above and the analytics transmission in 1(1))Source IP address and communication metadata such as request timestamp and destinationCloudflare, Inc. (United States)Protecting communications (encryption and blocking unauthorised access). Transmissions to Google, Apple, RevenueCat and Expo go directly to those providers and do not pass through Cloudflare.

For information about each provider’s handling of information, see Google’s Telecommunications Business Act disclosures, the Cloudflare Privacy Policy and the Apple Privacy Policy.

The Service does not include a mechanism that sends usage information to a third-party analytics service (a third-party analytics SDK). The analytics in 1(1) is performed by the Operator using Cloudflare’s infrastructure.

Automated review of reported content by Anthropic PBC and forwarding inquiries to the Operator through Discord Inc. are server-to-server transmissions, not transmissions from the user’s device. See Section 6 of the Privacy Policy.

3. Stopping transmission and deleting information already obtained

Stopping future transmissions and deleting information already obtained are separate procedures.

Stopping transmission

TransmissionHow to stop it
(1) Usage analyticsThere is no setting to disable this transmission individually. It occurs only while signed in, so signing out stops it. Deleting (uninstalling) the app stops all future transmissions.
(2) App update checksThis occurs when the app starts. If the Operator distributes an urgent fix, it may also occur while the app is open when it returns from the background. It continues after account deletion for as long as the app remains on the device. Delete the app to stop it.
(3) Purchase-status managementPurchase-related transmissions do not occur if you do not purchase a paid plan, fridge ticket packs or photobooks. Deleting the app stops future transmissions.
Transmissions in Section 2These stop when you do not use the relevant feature, sign out, or delete the app.

Deleting information already obtained

If a new information collection module is introduced, the Operator will update this page and provide notice as required by law.

Contact

info@fridge-co.com