Pashaberi Privacy Policy

This page is an English translation provided for reference. The Japanese version is authoritative（日本語版が正本です）: 日本語版

Established: September 6, 2026 Last updated: October 1, 2026 Business name: MuggyTea

Introduction

The photos you take with Pashaberi, the voices you record, and the text you type into captions and speech bubbles are stored in the app's private storage area on your device. Photos, recordings and text you enter are not sent to the developer. Your data leaves the device only when it is included in an OS backup, or when you yourself export or share it (§1 and §6).

The free version uses Google's advertising service (AdMob). To deliver ads, information about your device is sent to Google. See §2 for details.

1. Information stored on your device and never sent to the developer

The following are stored in the app's private storage area. They are never sent to the developer's server.

Information	Where it is stored
Photos you take	The app's private area (not visible to other apps)
Voice recordings	Same as above
Text typed into captions and speech bubbles	Same as above (the app's internal database)
4-frame story arrangements	Same as above
App settings (such as autoplay on/off)	Same as above

The app itself has no communication feature that transmits any of these externally. In addition to advertising and purchase processing, Android and iOS versions that include usage analysis communicate with Google Analytics only with your consent. iOS version 1.0.0 builds 11 and 12 do not perform this analysis (§2-7).

However, in the following three cases your data does leave the app's private storage area. We state this clearly to avoid any misunderstanding.

OS backups iPhone iCloud backups and Android automatic backups to your Google account run according to your device settings. What the app includes in or excludes from backups is described in §6.
Saving to your device's Photos app (on by default) Photos with sound that you take are also saved to your device's Photos app. They are saved to your own photo library and are not sent to the developer's server. You can turn this off in the settings. See 1-1 for details.
Your own exports and shares When you use "Save to Photos" or the share sheet, a copy remains at the destination you chose. What happens to it from there is under your control.

Your photos and voices are passed to other apps or posted to social media only when you tap "Share." The developer never sends them automatically.

1-1. Saving to your device's Photos app

After a shot is taken and saved, that photo is also saved to your device's Photos app. This is on by default. You can turn it off in the app's settings screen → "Camera" → "Also save to Photos."

Item	Details
What is saved	The photo and voice as taken. Items with a voice are saved as a video (MP4); items without a voice are saved as an image (JPEG)
Where it is saved	Your device's Photos app (photo library). It stays under your control and is not sent to the developer's server
Onward sync	Your photo library may sync to a cloud service (iCloud Photos, Google Photos backup, and so on) according to your device settings. Whether and where it syncs depends on your settings
What is not included	4-frame stories and captions or speech bubbles added later are not included (only the photo and voice as taken at the moment of shooting are saved)
Permission	On iOS, the first time this saving runs, the app asks for permission to add to Photos (§4). Even if you decline, taking photos and saving and viewing them inside the app continue to work
After turning it off	Items you take from then on are no longer saved to the Photos app. Items already saved remain in the Photos app; delete them there if you no longer want them

2. Information collected for advertising and usage analysis

The free version shows banner ads at the bottom of the gallery screen and the 4-frame story list screen. Ads are delivered using Google's Google Mobile Ads SDK (AdMob).

2-1. Information Google collects

According to Google's public documentation, the Google Mobile Ads SDK collects the following information.

Information	Details
IP address	Used to estimate the device's approximate region
Device identifiers / advertising ID	Used for ad delivery and aggregation (see 2-2)
Ad data (records of ads shown)	A record of which ads were displayed
App interactions (launches, ad views and taps, and so on)	Used to aggregate usage
Diagnostics (crash records, performance, and so on)	Used to investigate and improve the SDK

Sources: App store data disclosure (AdMob / iOS) / Google Play data disclosure (AdMob / Android)

Because an approximate region can be estimated from the IP address, our privacy declarations on both the App Store and Google Play include "approximate location." The app does not request any location permission. It does not obtain precise GPS location.

This information is sent to Google's servers. The transmission is encrypted with TLS (source: the Android documentation above). The developer does not receive this information. All the developer can see in the AdMob console is aggregate figures: how many times ads were shown and how much revenue resulted.

2-2. We do not use ads selected based on your past behavior

For every ad request in the app, Pashaberi explicitly disables ads selected based on past behavior (personalized ads). Google calls ads served with this setting "non-personalized ads."

Non-personalized ads are selected based not on your behavioral history but on things such as your rough region and the content of the app you are viewing.

This does not mean identifiers are no longer collected. According to Google, even for non-personalized ads, cookies and mobile advertising IDs are still used for frequency capping (so the same ad is not shown too often) and for aggregate reporting. We state honestly that "not personalized" does not mean "nothing is collected."

Source: About non-personalized ads (AdMob Help)

2-3. Tracking on iOS

The iOS version does not display the App Tracking Transparency prompt (the dialog asking permission to track). Because permission is never requested, the advertising identifier used for tracking (IDFA) is not obtained. We do not deliver ads linked to your activity in other companies' apps or websites.

2-4. The advertising ID on Android

On Android, the Google Mobile Ads SDK uses the advertising ID (AAID). For this reason the app includes the com.google.android.gms.permission.AD_ID permission.

You can reset or delete the advertising ID at any time from your device settings. Try Android's "Settings → Privacy → Ads."

2-5. Google's privacy policy

How Google handles information is defined by Google's own policies.

Information Google collects is handled under Google's own policies and the AdMob terms. The developer can view aggregate advertising reports, but cannot view or delete the underlying advertising data. Usage analytics is described separately in §2-7.

2-6. How to stop the ads

If you purchase Pro (a one-time purchase), ads are no longer shown. Whether the advertising library starts differs by OS, as follows.

iOS: The advertising machinery is not started until the app finishes checking your purchase status with the store at launch. On a device confirmed as Pro, the advertising library is never started.
Android: The decision is based on the purchase status stored on the device. Once Pro has been confirmed on a device the library does not start, but in states where no purchase status is stored on the device — for example right after reinstalling the app — it may start while the check is still in progress.
Immediately after purchasing: Only the display disappears. Because there is no way to stop a library that has already started, quit and relaunch the app; from the next launch on, it will not start.

2-7. Usage analysis to improve the app

iOS version 1.0.0 builds 11 and 12 do not include Google Analytics for Firebase. They do not send usage data to this service or provide an analytics setting. Advertising SDK data is described in §2-1 through §2-6.

The following applies to Android and iOS versions that include usage analysis. With your consent, we use Google Analytics for Firebase to understand which features are used and improve Pashaberi. This is optional for both free and Pro users. You can use capture, playback, sharing and other features without agreeing.

Data includes app launches, capture, playback and sharing actions, usage time, app version, device and OS information, an app-specific identifier and approximate region. Region is inferred from the IP address used for the connection; GPS is not used. Photos, recordings, captions, speech-bubble text and file names are not sent.

Purchase events (such as product name, price and currency) and SDK diagnostic information may also be measured. Payment card details, store account credentials and purchase tokens are not sent to Analytics.

Google receives this data, and the developer views usage reports in Google Analytics. Analytics advertising-identifier collection and ad personalization are disabled. We do not use this data for advertising tracking by combining it with other companies’ data. Advertising SDK data is described in §2-1 through §2-6.

In iOS version 1.0.0 build 13 and later, analytics is off by default. To enable it, open Settings → Usage statistics and turn on the switch after reading the explanation. Choices from older iOS builds are not carried forward. Build 10 offered an optional analytics switch in Settings. Android and iOS version 1.0.0 (9) offer a choice during initial setup or under Settings → Help improve Pashaberi. You can turn this off in Settings at any time.

Turning it off stops new analytics collection and resets locally stored analytics data and identifiers. It does not immediately delete all data already sent. User- and event-level retention is set to two months; aggregate reports that do not identify individuals may remain longer. Contact us using §9 for questions.

See Google’s Privacy Policy and Firebase Privacy and Security for details.

3. Purchase information

All purchase processing for Pro is handled by Apple (App Store) or Google (Google Play).

The developer never receives your credit card number, name, address, or email address.
The app communicates with Apple's / Google's libraries to process the purchase, and the purchase information it receives (transaction records, purchase tokens, and so on) is processed entirely on the device. Determining whether you own Pro happens on the device; nothing is sent to a developer server (there is none).
In versions that include analytics, with your consent, purchase events such as product name, price and currency may be sent to Google Analytics (§2-7).
Purchase history is tied to your Apple / Google account and managed by those companies.
What the developer can see in each store's console is transaction records such as sales and refunds. Your photos, audio, and typed text are not included there.

For how each company handles your information, see their policies.

4. Permissions the app requests, and what they are for

Permission	What it is used for	If you decline
Camera	To take photos	You cannot take photos. This is the app's core feature, so we ask for permission
Microphone	To record voices with photos	You cannot record voices. Taking, saving, and viewing photos still work
Add to Photos (iOS) / storage for saving photos (Android 8–9)	To save the photos and videos you create to your device's Photos app (used both for the automatic saving in §1-1 and for the manual "Save to Photos")	Taking photos, saving and viewing in the app, and sharing still work. Only saving to the Photos app is unavailable

The app never requests location, contacts, calendar, or notification permissions.
Permissions are requested at the moment they are needed, not all at once at first launch. The iOS "Add to Photos" permission is requested only once, the first time a save to the Photos app runs.
You can revoke any permission at any time from your device settings.

5. Sharing with third parties

We never provide your photos, audio, or typed text to third parties.
For ad delivery, the information described in §2 is sent to Google.
For purchase processing, Apple / Google process information within their own systems.
In versions that include analytics, with your consent, the usage information described in §2-7 is sent to Google Analytics.

Beyond the above, the developer provides no information to third parties, except where disclosure is required by law (and since the developer does not hold your photos or audio in the first place, there is nothing to hand over).

Transfers outside Japan

Google and Apple operate servers outside Japan, so the information in §2 and §3 may be processed outside Japan. Each company's handling follows its own policies.

6. How long data is kept, and how to delete it

Data on your device

There is no retention limit. Data stays on your device until you delete it.
Deleting a photo inside the app deletes that photo, its audio, and its caption and speech bubble text. A 4-frame story that used the photo remains as a work, with that frame left empty (deleting the whole story would destroy the edits for the other three photos as well).
Images and videos you have already exported are not deleted by deleting inside the app. Delete copies left in the Photos app or at share destinations in those places.
Deleting the app removes the data the app stored from your device. The developer retains no photos, recordings or text you entered. See §2-7 for usage analytics already sent. However, whatever was included in an OS backup remains inside that backup.

Advertising-related information

You can reset or delete the advertising ID from your device settings (Android). On iOS, tracking permission is never requested, so the tracking advertising identifier (IDFA) is never obtained in the first place.
If you purchase Pro, information is no longer collected for advertising (conditions in §2-6).
The developer has no authority to delete information Google already holds. Records tied to your Google account can be reviewed and deleted at My Activity. However, the developer has not been able to confirm whether every record AdMob keeps for ad delivery can be deleted through that channel. For questions, please contact Google.

Backups and switching devices (important)

This app has no data-migration feature for switching devices (as of version 1.0.0). Whether data is included in OS backups is determined by the app's implementation as follows. We have not run migration tests on real devices, so we do not guarantee that a migration will succeed.

Path	How the app's implementation treats it
iOS: iCloud backup / device-to-device transfer with Quick Start	Photos, audio, typed text, and settings are all left inside the backup scope (we checked the app's code and confirmed there is not a single exclusion flag). If iCloud Backup is on and there is enough space, they are included
Android: direct device-to-device transfer	Photos, audio and text are included; analytics consent is excluded. However, if the source device runs Android 11 or earlier, photos and audio may not transfer (the developer has not been able to verify this)
Android: automatic cloud backup to your Google account	Photos and audio are excluded. Cloud backup has a per-app size limit that photos and audio are expected to exceed. Captions, speech bubbles, 4-frame story arrangements, and ordinary app settings are included. Analytics consent and locally stored analytics data are excluded. Note that if "Also save to Photos" is on, the photos you take (as videos when they have a voice) are also in your Photos app and remain according to your own cloud settings such as Google Photos (1-1)
Switching between iPhone and Android	Cannot be carried over because the operating systems differ
If you delete the app	The data inside the app is deleted. The developer cannot restore it (if an OS backup remains, you can restore from it yourself)

If you leave "Also save to Photos" on (the default), the photos you take (as videos when they have a voice) also remain in your Photos app (1-1). In addition, we recommend exporting important photos with the share feature and saving them separately to your own cloud or elsewhere.

7. Target age and use by minors

Pashaberi is for people aged 13 and over who want to keep voices with photos of outings with friends and everyday family moments. It is not directed at children under 13 or offered in the App Store Kids category.

The Google Play target age groups are 13–15, 16–17, and 18 and over. Target age groups and content ratings are separate declarations. Content ratings are displayed by each store.
If you are under 18, obtain the consent of a parent or legal guardian before purchasing Pashaberi Pro.
Respect the privacy of people pictured or recorded when sharing photos and voices.

The app has no fields for registering personally identifying information such as name, date of birth, or email address, for any age. How we handle email you send us is described in §9.

8. Changes to this policy

We may change this policy to follow changes in law or new app features.

When we make a change, we update this page and record the revision date and the changes at the end of the page.
For important changes, such as new categories of collected information, we announce the change inside the app before the revised policy takes effect.
Past revisions remain listed at the end of this page.

9. Contact

For questions about this policy or how data is handled, please contact:

[email protected]

The app is developed and run by an individual, so replies may take a few days.

When you send an email, the developer receives your email address and the message body. This is not something the app collects; it reaches the developer because you send the email. It is handled as follows.

Item	Details
Purpose of use	Only to reply to your inquiry and to investigate and fix problems
Provision to third parties	None
Retention	Deleted once a reply is complete and it is no longer needed
A request	There is no need to attach photos or recordings. To identify a cause, the steps you took and any message shown on screen are enough

Revision history

Date	Changes
September 6, 2026	Established
September 9, 2026	Updated the target audience to ages 13 and over and clarified use by minors.
September 13, 2026	Added optional usage analysis, collected information, consent controls, retention and deletion, and backup handling.
October 1, 2026	Restored optional app-only analytics in iOS build 13, off by default, with no advertising use or cross-company tracking.
September 18, 2026	Documented the removal of Google Analytics in iOS version 1.0.0 builds 11 and 12 and the treatment of earlier versions.
September 15, 2026	Updated iOS analytics to default off and be selected in Settings, and clarified the differences from earlier versions.