Pewe Privacy Policy

Magsmi, a sole proprietor in the Republic of Korea, provides Pewe. The Magsmi Privacy Desk handles privacy matters and related complaints. Send privacy requests to support@magsmi.com.

The native app stores your household name, pet names, species, characteristics, birth dates, photos, target weights, weight history, memos, reminder settings, and preferences on your device. Photos are copied into the app's storage. Magsmi has no Pewe account or cloud sync and cannot see these records. Android cloud backup is off. Other device backups follow your platform settings.

With Pewe Pro, the app keeps a copy of each pet's name, species, current weight, weight date, weight change, and photo in storage its home screen widget can read, whether or not you add a widget. A widget shows one of your pets until you remove it.

Reminders are scheduled on your device. CSV, PDF, and backup exports go to your device's share sheet. Backups leave out photos and restore reminders paused. After you share a file, the app or place you choose controls it.

The native app includes Google AdMob, but ads are turned off, so the app does not request or show ads.

The Apps-in-Toss edition stores the following in Toss Storage: your household name, pet profiles, characteristics, birth dates, target weights, resized photos, weights, memos, preferences, reminders, purchase status, onboarding state, and when the app last asked for a review. Toss manages that storage under its own policy.

Buying or restoring a purchase opens Toss Login. The app sends the resulting authorization code and referrer to Magsmi's purchase service at api.toss.magsmi.com, which runs on Cloudflare. The service stores a pseudonymous subject, sessions that hold the Toss user key in encrypted form, and order, order event, and entitlement records in Cloudflare D1.

Free users see a Toss banner ad, which Toss serves under its own policy. Exports are saved through Toss, and backups leave out photos. This edition does not schedule notifications.

Pewe uses your records only to track your pets, remind you of care, and create the exports you ask for. Purchase information is used to provide and restore purchases, and support email is used to answer your request. Magsmi does not sell your information or use it for targeted advertising.

Records stay until you delete them. Archiving a pet hides it and keeps its records. Deleting a pet removes its weights and photo. Clearing app data or uninstalling the native app removes its records. In the Apps-in-Toss edition, Delete all pet data in Settings removes all your pets, including archived ones, with their photos and weights, and your reminders and household name from Toss Storage. It keeps your settings, purchase status, onboarding state, and review prompt timing. It does not change records held by the purchase service, which follow the unlinking and order-record rules below.

When Toss reports that you unlinked Pewe, Magsmi deletes the purchase service's user record with its sessions, orders, order events, and entitlements. A pseudonymous unlink marker stays for up to two hours so that a sign-in that started earlier cannot recreate the record. Unlinking does not clear your Pewe records in Toss Storage.

Korea's Act on Consumer Protection in Electronic Commerce requires contract, payment, and supply records to be kept for five years. Magsmi keeps a separate record of each verified Toss order for five years from the order's latest status date and deletes it when that period ends. It holds the order and product identifiers, the pseudonymous subject, and the purchase, grant, and refund status and dates. It remains after unlinking. Under the same Act, Magsmi keeps records of consumer complaints and disputes about these purchases, such as support emails, for three years.

If you email support@magsmi.com, Magsmi receives your email address, message, and any attachments. Magsmi keeps support messages only as long as needed to answer and follow up, and deletes them on request unless the law requires keeping them.

When a record is no longer needed and no law requires keeping it, Magsmi deletes the electronic copy it controls. A deleted record leaves the live database right away. Cloudflare D1's point-in-time recovery can restore it for up to 30 days, after which it is gone.

Apple and Google run the app stores and take payment for the native app. Toss runs the Apps-in-Toss platform, Toss Login, payment, Toss Storage, file saving, and banner ads. Each acts under its own policy.

Magsmi shares personal information only with the providers named in this policy and only for the purposes stated here. The recipients below receive personal information outside Korea.

Recipient: RevenueCat, Inc. Destination: the United States, on Amazon Web Services. Items: an anonymous app user ID, product, transaction, and entitlement state, and routine device and network data. When and how: over an encrypted connection when a native store build opens and when you buy or restore Pewe Pro. Purpose: offering, verifying, and restoring purchases. Retention: RevenueCat keeps purchase records for as long as it needs them to provide and restore purchases, prevent fraud, resolve disputes, and meet legal obligations. You can ask Magsmi to have your records deleted. Deleting them does not remove your purchase, and restoring it later from the App Store or Google Play creates a new record. Privacy contact: 1032 E Brandon Blvd #3003, Brandon, FL 33511, United States, compliance@revenuecat.com. Refusing: do not use the native app, which starts RevenueCat when it opens. The Apps-in-Toss edition does not use RevenueCat.

Recipient: Cloudflare, Inc. Destination: primarily the United States and the European Economic Area, with access from other countries where Cloudflare operates. Items: request data such as your IP address, the account, entitlement, purchase-record, and security data of the Apps-in-Toss purchase service, and the addresses, headers, message, and attachments of support email it forwards. When and how: over an encrypted connection when the native app checks the magsmi.com release file, you open Magsmi's legal or support pages, or you sign in, buy, or restore a purchase in the Apps-in-Toss edition, and through Email Routing when you email support. Purpose: delivering the release file, delivering Magsmi's legal and support pages, running the Toss purchase service, and forwarding support email. Retention: Magsmi keeps the records it stores there for the periods in the retention section above. Cloudflare keeps routine request and security records for as long as the purposes in its privacy policy and its legal obligations require. Privacy contact: dpo@cloudflare.com. Refusing: do not use the native app, which checks the release file, do not open Magsmi's legal or support pages, do not sign in, buy, or restore a purchase in the Apps-in-Toss edition, and do not email support. The Apps-in-Toss edition's free features keep working, but you cannot buy or restore a purchase there. Magsmi cannot answer a request it does not receive.

Recipient: Google LLC. Destination: the United States and Google servers around the world. Items: the sender and recipient addresses, headers, message, and attachments of support email. When and how: when you email support, Cloudflare Email Routing forwards the message to Magsmi's consumer Gmail mailbox. Support email uses standard encrypted email transport where your email provider supports it. Purpose: receiving, reading, and answering support requests. Retention: Gmail keeps the message until Magsmi deletes it under this policy. Google says its complete deletion process generally takes about two months and encrypted backups can retain data for up to six months. Privacy contact: the options at https://support.google.com/policies/answer/9581826. Google's privacy policy is at https://policies.google.com/privacy. Refusing: do not email support. Magsmi cannot answer a request it does not receive.

Recipient: 650 Industries, Inc. (Expo). Destination: the United States. Items: a random installation ID, the platform and app and update versions, routine network data such as your IP address, and, after a failed start, up to 1,024 characters of the error message. Update requests do not include what you record in the app. When and how: over an encrypted connection when the native app checks for or downloads an update. Purpose: delivering app updates. Retention: Expo keeps this information only as long as reasonably necessary for the purposes in its privacy policy, under applicable law. Privacy contact: https://expo.dev/contact. Refusing: do not use the native app, which checks for updates. The Apps-in-Toss edition does not use Expo.

Depending on applicable law, you can ask Magsmi to access, correct, delete, or stop processing information it controls, or withdraw consent, by emailing support@magsmi.com. Records the law requires Magsmi to keep stay until their period ends. In Korea, you can also contact the Privacy Infringement Report Center at 118 or the Personal Information Dispute Mediation Committee at 1833-6972.

The app's network requests use HTTPS. The Toss purchase service also uses mutual TLS (mTLS) for calls to Toss, stores sessions only as hashes that expire after one hour, encrypts the Toss user key, limits sign-in attempts by IP address, and checks each order with Toss before granting access.

Magsmi posts changes to this policy here with a new effective date and gives additional notice where the law requires it.