Stitch Audio: Join & Chapters — Privacy Policy
Last updated: 2026-10-08
This privacy policy applies to the mobile app "Stitch Audio: Join & Chapters" for Android:
- Google Play: package com.simonj.audiojoiner, developer "Global Utility App Maker"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Stitch Audio does not require an account, and we do not sell personal information. You import audio files, arrange them as clips on a timeline (or mix them with a background track), and export the result as an M4A or WAV file together with a chapter list. Audio is decoded, previewed, and rendered by the app on your device. Your projects and the app's copies of your audio are kept in the app's storage on your device. The app also uses Google services and an advertising mediation partner for analytics, crash reporting, remote configuration, and advertising.
AUDIO FILES, EXPORTS, AND SHARING
Importing: when you tap "Import audio" or "Add second lane" (a background track in mix mode), the Android file picker opens and only the audio files you choose are given to the app; no storage permission is needed. The picker places temporary copies in the app's cache, and the app keeps its own copy of each file in its audio folder. These temporary picker copies are not removed by the app and may remain in the cache. "Try a sample project" creates tones generated by the app; it does not use the microphone.
Exporting: an export is rendered into a folder in the app's cache. On the finished screen, "Share audio" passes the file to the Android share sheet and the app or person you choose receives it, and "Save audio file" opens the Android save dialog so you can choose where a copy is written. Leaving the finished screen asks you to discard the rendered file, which then deletes it; files left in the export folder (including preview files) are normally deleted the next time the app starts. Previews are rendered into the same folder and are normally deleted when playback stops.
Chapter lists contain your clip names and their start times. "Copy chapter list" puts this text on the Android clipboard. "Share chapter list" and "Save chapter list" write a temporary text file to the app's cache, pass it to the share sheet or save dialog, and delete it afterwards; any such file left over is normally deleted the next time the app starts.
The app does not request or use the microphone, camera, location, contacts, or your photos.
INFORMATION STORED ON YOUR DEVICE
For each project the app keeps its name, output sample rate and channels, join or mix mode, the clips in order (name, trim points, volume, fade-in and fade-out), the joints between clips (cut, gap, or crossfade and its length), the background track with its offset and volume, and, for each audio file used, the app's copy of the file, its original file name, size, duration and format details, waveform peaks, and a SHA-256 fingerprint used to check the file. While an export runs, the app keeps a temporary copy of the project so it can tell you if an export was interrupted, and it keeps internal bookkeeping files that list which audio files each project uses. The app also keeps the IDs of deleted projects so that restoring a backup does not bring them back; this list is kept without a limit. There is no fixed limit on the number of projects or clips. Decoded audio used for previews and exports is kept in the app's cache and is normally deleted when the app starts.
The app may also store basic operating information such as cached advertising settings and a cached More Apps list.
The developer does not run a server that receives your projects or audio. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not write to Firestore or upload your projects, clip names, chapter lists, or audio. When you open the developer's other apps in the menu, app icons are loaded from the web addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as automatically collected app opens and sessions, whether a review request from the Settings screen or the exit dialog was attempted, unavailable, or failed, ad revenue events (ad format, value, currency, and precision), app version, device type, and app-instance identifiers. These events do not include project or clip names, file names, chapter lists, or audio.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
When ads are requested (see below), the app shows ads through Google AdMob: a banner on the Projects screen, a native ad that may appear in the exit dialog, an app-open ad that may appear when you return to the app, and an interstitial ad that may appear after an export finishes (not after the first export each time the app is started). The app does not start a full-screen ad while a project is open, while audio is being rendered or previewed, or while the Settings screen or the exit dialog is open. AdMob may also request ads from the InMobi mediation network. Google and InMobi may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location even though the app has no location permission.
PERMISSIONS AND ADVERTISING CHOICES
The app requests no feature permissions such as microphone, camera, location, contacts, photos and media, notifications, or storage access. It uses internet access and the Android advertising ID permission for the services above, and vibration, which Android grants without asking, for short haptic feedback when you tap a button and when an action such as a save or export completes. While audio is rendering for an export or a preview, the app keeps the screen on.
When the app starts, Google's consent message (UMP) is checked and shown where required (for example in the EEA and UK). When Google reports that ads can be requested, the app then requests ads; they are personalized only if consent is not required or your choice allows personalized advertising, and non-personalized otherwise. If Google reports that ads cannot be requested, the app does not request ads during that session. If the consent check fails, the app still requests non-personalized ads. Where Google requires it, the Settings screen (opened with "Menu") shows "Privacy choices", which reopens the consent message so you can change your advertising choice. After you change it there, if Google reports that ads can be requested, the app requests ads, which are personalized only if your new choice allows it (if your new choice cannot be read, they are non-personalized); if the message cannot be opened, the app stops requesting ads until it is started again. The app works whatever you choose.
STORAGE AND YOUR CONTROL
On the Projects screen, Delete removes a project from the list and offers Undo. The project is removed for good when you tap Done, when you delete another project, or the next time the app starts. At that point the app deletes the project's saved data and the audio files that no other project uses; if some saved data cannot be read, the app keeps audio files rather than risk deleting files another project still uses. In a project, "Remove clip" takes a clip off the timeline; after you save, or if you discard unsaved changes, audio that no saved project uses is normally removed from the app's audio folder in the same way.
"Create backup" writes a set of files to the app's storage: a manifest, your readable projects (including clip names and the original names of their audio files), the IDs of deleted and unreadable projects, and the audio files those projects use. "Share file" sends one file of the set through the Android share sheet; where you send or save it is your choice, and the app does not delete copies kept elsewhere. "Restore backup" reads the backup files you pick; the app keeps verified copies of them in its storage so that missing files can be added in a later restore, copies restored audio into its audio folder, and merges projects so that the newer version of each project is kept and deleted projects stay deleted. The file picker also places temporary copies of the picked files in the app's cache, which the app does not remove. The app has no button to delete backup sets or these kept restore copies, and it sets no limit on their number. When a project is removed for good, the app also removes it, and audio used only by it, from these stored sets at that time or at the next start: a set whose projects have all been removed is deleted, and other sets are rewritten without them. A set that is incomplete or cannot be read is left unchanged.
You can also clear the app's storage in Android Settings or uninstall the app, which removes the app's storage on the device; files you saved or shared elsewhere are not removed. Local data, including backup files, may be included in a Google or device backup depending on your backup settings (the app allows Android system backup); uninstalling normally removes the active copy but may not remove an older backup.
Because we do not receive your projects or audio, we cannot delete them for you; the controls above remove them from the app. For questions about data processed by Google or InMobi, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
SECURITY
Your projects, audio copies, and backup files are kept in the app's private storage, which the operating system protects from other apps; they are not separately encrypted by the app, so protect your device with a screen lock. Backup files are not encrypted, so anyone who receives a shared backup file can read its contents and play its audio. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services and the ad mediation partner uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app handles to what is described in this policy.
IMPORTANT NOTICE
Only import, join, and share audio you have the right to use. Exports can be stopped if the app is closed or Android ends it, so keep the app open while exporting and keep your original files until you have checked the result. Keep the volume at a safe level, especially with headphones.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com