My Photo Copy
Privacy Policy
The short version.
- My Photo Copy copies your photos and videos from your iPhone to a drive or folder you choose. Photo copying does not upload your originals to Technabit or to our analytics or diagnostic services. A cloud destination you choose uses that provider's service.
- There is no app account or sign-in. The app uses persistent installation and purchase identifiers, described below.
- The app sends limited usage events to TelemetryDeck, diagnostic reports to Sentry when configured, purchase information to RevenueCat, and app-update checks to Expo.
- Usage events exclude individual photo identifiers, filenames, folder paths and destination bookmarks. Diagnostic filtering is best effort; support files you deliberately share can contain more detail.
- RevenueCat also handles Apple Ads attribution. Installation-level usage and billing information can be associated to help us understand obstacles and improve the app.
1. Who is responsible
My Photo Copy is made and published by:
Technabit e.U.
Riedelstrasse 1
6330 Kufstein, Austria
support@technabit.com
Technabit e.U. is the controller for the data described in this policy. If you have a question about it, write to the address above. Support correspondence is separate from the usage, diagnostic and purchase information described below.
2. What the app does with your photos and videos
My Photo Copy exists to make one honest copy of your photo library on storage you own. To do that it needs Full Access to your photo library, because iOS Limited Access hands an app a rendered preview rather than the original file, and a preview is not a backup.
- What it reads. The original file behind each photo and video you select, together with the information iOS keeps about it (creation date, file name, file size, media type, whether it is a Live Photo, and whether the original is stored in iCloud rather than on the phone).
- What it does with it. It writes that original, byte for byte, into the folder you chose with Apple's Files picker — a USB stick, an SSD, an SD card, iCloud Drive, or a folder in "On My iPhone". With verification enabled, it reads the written file back and compares its hash and size with the source data.
- Where it goes. Copying writes to the destination you choose. A cloud destination uses that provider's service. If you deliberately share a saved photo or video, iOS passes it to the recipient or service you choose. The app does not send photo or video originals to our usage-measurement or diagnostic services.
- What is written next to the copies. A manifest file (in a hidden
.myphotocopyfolder) and a plain HTML report listing what was copied and when. Both live on your drive, under your control, and are readable by you on any computer. - Nothing is analysed. There is no face recognition, no scene classification, no content scanning, no machine-learning model applied to your pictures, and no index of what they show.
iCloud originals. If "Optimise iPhone Storage" has left only a small version of a photo on your phone, the app asks iOS to fetch the full original before copying it. That download happens between your iPhone and Apple, over your own Apple Account, exactly as it does in the Photos app. We are not a party to it and we see nothing of it. Over mobile data it can be expensive, which is why the app tells you to start a large backup on Wi‑Fi.
3. Local storage on your iPhone
- An index of your photo library (a local SQLite database) and thumbnail caches, so the app can show what you are about to copy and saved previews of backups. Saved previews can remain after you delete an original from your photo library, and can be shown while a destination is unavailable. You can clear caches in Settings → Storage.
- Your settings: folder layout, file naming, conflict handling, reminder cadence, theme, language.
- A bookmark to the destination folder you last chose, so the app can find it again.
- A record of your backup runs and their results, including the names of any files that could not be copied.
- A counter of how many items you have backed up on the free tier, stored in the iOS Keychain.
- A diagnostics log written by the backup engine. It stays in memory and on the device. It is shown only in the app, and it is only ever shared if you choose to share it with us through the iOS share sheet when we are helping you with a problem.
App-container data is normally removed when you delete the app. The Keychain-backed free-tier counter can survive reinstalling. Clearing local data or deleting the app does not delete files on your chosen destination, purchase history or data already transmitted to the services below. Usage measurement sends selected counts and states, not the library index, thumbnail contents or destination bookmarks.
4. What leaves your iPhone, exactly
Network requests support usage measurement, error diagnosis, purchase verification, installation attribution and app updates. Apple's frameworks also handle payments and downloads of your own iCloud originals. Photo copying writes to the location you choose.
| Who | What is sent | Why | Where |
|---|---|---|---|
| RevenueCat (purchase infrastructure) |
Purchase and entitlement information and RevenueCat's app customer identifier. The app supplies its TelemetryDeck installation and app identifiers, plus limited attributes such as destination kind, a free-limit encounter, first-backup count and paywall source/time. RevenueCat collects Apple's AdServices attribution token. The app does not supply a name, email, individual photo identifier, filename or destination bookmark in these attributes. | To check and restore Pro access, attribute Apple Ads installs and purchases, and compare observed app behavior with billing. One RevenueCat customer can relate to multiple installations or restored access. | RevenueCat, Inc., United States. Their privacy policy. |
| TelemetryDeck (usage measurement) |
Usage event names, counts and buckets; permission, selection and destination states; backup outcomes; free-limit and paywall choices; product, price/currency and trial-eligibility facts; served configuration; browsing, playback, share-sheet and reminder milestones; app/build/environment, iOS version, device model, language/region; persistent installation and session identifiers. Individual photo identifiers, contents, filenames, paths, bookmarks and arbitrary error text are excluded by the event allowlist. The service salts and hashes the submitted client identity before storage. | To find obstacles, measure useful backups and repeat use, and evaluate product and commercial changes. These are installation-level observations, not named app accounts. | TelemetryDeck GmbH, Germany. Their privacy policy. |
| Sentry (diagnostics) |
Exceptions, stack traces, breadcrumbs and app/device diagnostic context. The app disables default personal-information collection, screenshots, view hierarchy attachment and automatic performance tracing. It attempts to remove filenames and local paths from diagnostic text; this is a best-effort filter, not a guarantee that arbitrary diagnostics can never contain identifying details. | To diagnose errors and reliability problems. | Sentry, operated by Functional Software, Inc. Our organization's configured data storage region is the United States. Their privacy policy. |
| Expo / EAS Update (app updates) |
A request for an update manifest carrying an installation identifier, the platform and the app's runtime version. | To deliver small fixes between App Store releases. | Expo (650 Industries, Inc.), United States. Their privacy policy. |
| Apple | The purchase itself (App Store / StoreKit) and, if applicable, the download of iCloud-stored originals. | To take payment and to fetch your own photos from your own iCloud account. | Apple. Governed by Apple's privacy policy. |
Two further things happen only when you deliberately start them: opening a link (this policy, the terms, the support email, Photo Trim's App Store page) hands the address to iOS, and sharing a saved photo/video original, result card or diagnostics log hands a file to the iOS share sheet, where you choose the recipient. These shared files can contain photo contents or other identifying information.
5. What we do not do
- We do not upload your photo library for usage measurement or diagnostics. We use the limited usage, diagnostic and billing services in section 4.
- The app does not request the advertising identifier IDFA or use data brokers. Apple Ads attribution through AdServices is described above.
- We do not use cookies. These pages set none and load nothing from a third party.
- We do not sell or rent personal data. The services in section 4 receive information for the purposes described there.
- We do not send push notifications. Backup reminders are scheduled locally on your device by iOS; no push token is ever requested and no notification passes through a server.
- We do not require, offer or store an account, a password or an email address.
6. Legal bases (GDPR Article 6)
Usage measurement, diagnostics and attribution serve the purposes described in section 4: understanding how the app is used, finding obstacles and reliability problems, and evaluating product and marketing effectiveness. You can contact us to object to this processing or exercise the rights in section 9. The grounds for the app's other processing are set out below.
- Purchases and entitlement checks — Article 6(1)(b), performance of the contract you enter when you buy My Photo Copy Pro. Without the receipt check we cannot unlock what you paid for or restore it on a second device.
- Update checks — Article 6(1)(f), our legitimate interest in shipping fixes to installed apps. The data includes an installation identifier and app version.
- Photo library access — your explicit permission through iOS, which you grant in the system prompt and can withdraw at any time in iOS Settings → Privacy & Security → Photos. Photo data is processed only on your device and only to carry out the copy you asked for.
- Notifications — your consent, given in the iOS prompt, withdrawable in iOS Settings.
- Support email — Article 6(1)(b) and 6(1)(f): we read and answer what you send us.
7. How long anything is kept
- On your device: app-container records remain until cleared or the app is deleted. The free-tier Keychain counter can survive reinstalling; saved previews remain until cleared or evicted from the bounded cache.
- On your drive: your copies and their manifest are yours; nothing deletes them but you.
- RevenueCat: purchase records are retained for the life of the entitlement and afterwards as required by RevenueCat's own retention policy, so that a restore still works years later.
- Sentry diagnostics: the standard error-event retention for our current Developer plan is 30 days. Issue summaries and aggregate counts can remain after individual events expire. Changing the plan or service settings can change retention.
- Usage and other service records: clearing app data does not erase records already received by TelemetryDeck or other providers. Service retention and deletion follow the configured account settings and applicable provider terms. Contact us about a request; identifying the relevant installation may require additional information.
- Support email: kept while the conversation is useful and then deleted, and in any case no longer than three years, except where Austrian bookkeeping law requires an invoice-related message to be retained for longer.
8. International transfers
Our providers can process data in different jurisdictions, including the European Economic Area and the United States. The recipients and their policies are listed in section 4. Applicable contractual safeguards depend on the provider and account configuration; an installation identifier is not a reason to assume that no transfer rules apply.
9. Your rights
Under the GDPR you have the right to access, rectify, erase, restrict and port your personal data, and to object to processing based on legitimate interests. To exercise any of them, write to support@technabit.com.
The app has no named account. We may need additional information to identify the relevant installation or purchase record; an email address alone may not identify it. Deleting the app does not erase service-side usage, diagnostic or billing records. We will assess requests using the information available and explain any limits, including records that must be retained and any effect on restoring a purchase.
You may complain to a supervisory authority. Ours is the Austrian Data Protection Authority (Österreichische Datenschutzbehörde, Barichgasse 40–42, 1030 Vienna, dsb.gv.at). You may also complain to the authority where you live.
10. Children
My Photo Copy is not directed at children and is not a Kids Category app. The usage, diagnostic and purchase practices described in this policy apply when the app is used; an age rating does not mean the app collects no data.
11. Security
Photo copies and local indexes stay on your device or chosen storage. The free-tier counter is held in the iOS Keychain. Requests to the listed services use HTTPS. We limit usage-event fields and apply diagnostic filtering, but no security or filtering measure is absolute.
One thing this app deliberately does not do is encrypt what it writes: your copies land on the drive as ordinary HEIC, JPEG, RAW and MOV files in dated folders, so that any computer can read them without this app or any other. That is a feature, and it means the physical security of the drive is yours to manage.
12. Changes to this policy
If the app starts doing something this page does not describe, this page changes first, with a new effective date at the top. Material changes will also be described in the App Store release notes for the version that introduces them.
13. Contact
Technabit e.U., Riedelstrasse 1, 6330 Kufstein, Austria — support@technabit.com