Privacy Policy

Effective 5 October 2026 · Last updated 5 October 2026 · Applies to 1m: Private Prompt Composer for iPhone (com.mobileproblemsolver.app), version 1.0 onward.

1m captures logs, code or an error on your screen, prepares a prompt around it, and hands the whole package to an app you already have through the iOS share sheet. This policy explains exactly what happens to that material at every step.

1. Who this policy is from

1m: Private Prompt Composer — 1m for short — is developed and published by Oleksandr Miahkyi, an independent developer. Throughout this policy, “we” means that developer and “the app” means 1m for iPhone. You can reach us at asoft.general.support@gmail.com.

2. What we collect

Nothing automatically. The app does not collect, transmit, store or process any personal data on our behalf. This is a technical fact about how it is built rather than a promise about how we behave:

• There is no server belonging to this app, and no backend of any kind.
• The app has no networking code of its own — no HTTP client, no web views, and no connection it opens to us or to any third party. It does contain three addresses, and all three are there for you to open deliberately from Settings: this privacy page, the support page, and a mailto: draft. Opening one hands it to Safari or to your mail app — 1m itself still makes no connection, and section 12 covers what a browser loading these pages involves. Everything else on the network is iOS acting on the app's behalf, and only ever to Apple — described in sections 5 and 6.
• There are no accounts. You never register or sign in, and the app never asks you for an email address.
• There is no analytics, telemetry, crash reporting or advertising, and no third-party software development kits are linked into the app at all.
• There is no tracking as the App Store defines it. The app does not use the Advertising Identifier, does not present the App Tracking Transparency prompt, and does not link anything about you to data from other companies.

The app ships with an Apple privacy manifest (PrivacyInfo.xcprivacy) that declares no tracking and no collected data types. Its App Store privacy label reads Data Not Collected. A support message you choose to write is not part of that label: Apple's own guidance leaves out contact details a person voluntarily sends for customer service, and an email composed in your mail app is not something this app collects. Those declarations and this page are intended to say the same thing; if you ever find that they do not, please tell us and we will correct it.

If you write to us

Settings has a Report a problem row, available while you have full access or an active trial. It opens your own mail app on a prepared draft addressed to our support address, with the app version in the subject, one sentence asking you to describe the problem, and four technical lines: app version, iOS version, device model identifier (something like iPhone17,1) and the language the app is set to. There is no account name, no identifier of yours, no logs, no attachments and nothing from any request in it.

The app sends nothing. The draft sits in your Drafts until you press send, and every line of it can be read, edited or deleted first — which is exactly why those four lines are in the body rather than attached. If no mail app will take the draft, the address is copied to your clipboard instead and the app tells you so. The support page is open to anyone, whether or not the app is unlocked.

If you do send a message, we receive what you wrote and the address you sent it from, as with any email. It arrives in a personal mailbox read by the developer and is used only to answer you and follow the problem up. It is not shared, not used for marketing, and not fed into anything else. Kept only for as long as answering and following up requires; ask us and we will delete the thread.

3. What is stored on your device

Everything the app keeps stays inside its own sandboxed container on your iPhone, where no other app can read it. There is no synchronisation of any kind — nothing is copied to a server of ours, because there is none. What can leave the container is a backup you make yourself, described below.

The 500 MB counts the attachments themselves. The small index beside them, the text read out of them and the recovery copy described below sit outside that sum, so it bounds what History keeps rather than everything the app has on disk.

History stores the prepared request, including the redactions you chose. Anything you chose to hide is already covered in the saved copy — painted out of the image, the PDF page or the video frame, and replaced with <sensitive> in your typed text. An attachment where you hid nothing is kept as you attached it. A request reaches History when preparation finishes, even if you have not shared it. An attempt you cancelled or that failed does not create a completed History entry.

In version 1.1, new History entries also retain the complete prepared prompt and the system prompt used. Later changes to settings or templates do not rewrite those saved entries. Changes to a prepared request's redactions are saved as a separate revision. When upgrading older entries, the app preserves the content it can recover and labels the resulting prompt as reconstructed; a custom prompt deleted before the upgrade cannot be recovered. These saved prompts and attachment copies remain on your device and in any backups you make, under the same retention and deletion rules described here.

If History's index cannot be read — a truncated write, a damaged restore — the app does not treat that as an empty History and start writing over it. It stops, shows you a recovery screen, leaves every file exactly where it is, and refuses to write anything until the matter is settled. A small copy of the previous index is kept beside the current one, and the app rebuilds from it automatically at launch whenever that copy and the files it names are intact — so the recovery screen is what you see when even that did not work. That copy never holds a request you deleted, and Clear History removes it along with everything else.

Your own backups are the ordinary way this material leaves the phone. History lives in Application Support, which iOS includes in an iCloud backup and in an encrypted backup to your computer, and the app deliberately does not exclude it: a History lost with a broken phone is worse than a History riding along in a backup you already trust. Those backups are between you and Apple. We cannot see them and there is nothing in them for us to see. If you would rather History were not in them, clear History before you back up, or switch the app off in the iCloud backup list in iOS Settings.

Deleting the app removes its container — and two things sit outside it. iOS deletes everything in the table above along with the app: your requests, their attachments, the prompts you wrote and your settings.

• One item in the iOS Keychain. Once you have activated a trial, the app keeps a single date there — the latest moment it has seen — which is what makes setting your device clock backwards ineffective. One date: no personal data, nothing that identifies you, never transmitted to us or to anyone else, and not synced through iCloud Keychain — though, like other Keychain items, it can travel in an encrypted backup you make yourself. If you never activate a trial, the app writes nothing to the Keychain at all. Earlier versions kept a few similar items; this version no longer writes them, and reads one of them only to tell you that a code you redeemed before now needs an Apple offer code to replace it.
• What Apple remembers. Your purchase, and the fact that you activated the trial, belong to your Apple Account and live in Apple's own records rather than in this app's container. That is why Restore purchases can bring a purchase back, and why reinstalling does not hand you a fresh trial. What Apple holds is between you and Apple; it is not ours to remove, and we are not shown it.

A backup you made earlier can also still hold History after the app itself is gone. And Clear History, in the app's Settings, deletes saved requests, their attachments and that recovery copy — it does not touch your settings or the system prompts you wrote, which go when you delete them or when you delete the app.

4. What happens when you share — read this one

The whole purpose of 1m is to hand your prepared request to another app. This is the only route by which anything leaves your device, and it never happens on its own:

• Nothing is shared until you press Share and then pick a destination in the standard iOS share sheet.
• The app cannot send anything automatically, silently, or in the background. It has no ability to choose a destination for you.
• Once you pick a destination, that app receives your content and its own privacy policy and terms govern what happens next. If the destination is a chat assistant, your material may be transmitted to and processed on that company's servers, and may be retained or used according to their policy and your settings with them.

We have no visibility into, control over, or relationship with whatever app you choose. We are not affiliated with the makers of any destination app. Please read the privacy policy of the app you are sharing into — that is where your content actually goes.

If the app becomes unresponsive after sharing, see the support page's recovery advice and version-specific status.

5. Purchases, the free trial and offer codes

1m works in a reduced form with no payment at all. Two things open the rest of it: an optional free three-day trial you start yourself, and a one-time purchase. Apple handles both, so it is worth being exact about what that involves.

The free trial does not start on its own. It is a free item in the App Store, and it begins only when you tap Start 3-day trial — Free and Apple returns a completed, verified transaction. Opening the app does not start it. Dismissing the paywall does not start it. Activating needs a working connection to the App Store twice over — once to fetch the item, once to complete it — and nothing is charged, so there is nothing to cancel and no subscription to end.

It then runs for 72 hours from the moment of that transaction, and the clock does not pause while the app is closed. Because the deadline belongs to the transaction, deleting the app and installing it again does not give you a second trial: what the app reads is Apple's record of what your Apple Account owns, not anything it kept for itself. A trial shared with you through Family Sharing is ignored — only your own activation counts. When the trial ends the app keeps working with a reduced set of features, and nothing you have already prepared is removed or made unreadable.

• Apple processes any purchase — we do not. Payment is handled entirely by the App Store under your Apple Account. We never see, receive or store your payment method, billing address, Apple Account email, or any other identifier. Apple does not give them to us.
• The app asks the App Store what this Apple Account owns. That question is asked by StoreKit, Apple's own framework, and answered by Apple. It tells Apple nothing Apple does not already know, and the answer goes nowhere but your device.
• Ownership is re-read, not settled at first launch. The app checks what you own each time it launches and each time it returns to the foreground, and it listens while it runs for changes Apple sends — a purchase made on another device, an Ask to Buy approval, a refund. Those checks are answered from the copy of your transactions iOS already holds on the device, so an app you own keeps working offline. Starting a trial, buying, redeeming a code and Restore purchases each need a connection, and Restore may ask you to authenticate with the App Store.
• The unlock is a single purchase, tied to your Apple Account. It is not a subscription: there is nothing to renew, nothing to cancel and no automatic charge. Because it belongs to your Apple Account rather than to this iPhone, it works on any device you sign in to, Restore purchases in Settings brings it back after reinstalling, and — if you turn on Family Sharing — your family members can use it. The app learns of a shared purchase in exactly the same way it learns of your own: by asking the App Store what this Apple Account is entitled to. It is never told who else is in your family, or anything about them. The price you see is the one Apple reports for your storefront; it is never written into the app.
• Refunds are requested from Apple, not from us. The button in Settings opens Apple's own refund sheet; the request goes to Apple, who decide. We have no role in approving or refusing one, and we are not told the reason you gave. If a refund is granted, the app simply stops seeing the purchase and returns to its reduced set of features.
• Offer codes are redeemed with Apple, not with us. The app does not check codes itself — it opens Apple's own redemption sheet. You type the code there, Apple decides whether it is valid, and access follows from the ownership Apple then reports. We never see the code you typed and the app stores nothing about it. If you redeemed a code in an earlier version, which did check codes on the device, the app reads that old yes/no flag once — only to tell you that it no longer grants access on its own and that you should ask for an Apple offer code to replace it. It never writes that flag again, and the flag itself was never the code: the code you typed was hashed and discarded even then.

We receive no report of who bought the app, who is in a trial, or who redeemed a code. Apple gives us the same aggregated sales figures it gives every developer; that is Apple's reporting to us, not data this app collects from you.

6. Apple services the app uses on your behalf

The app is built entirely on Apple frameworks. Three of them can reach Apple's servers on your behalf, and none of them sends anything to us:

Dictation (Speech framework)

Used only while you hold the microphone button to dictate. The app requests on-device recognition whenever your language supports it, specifically so that what you dictate — often a production incident — does not leave your phone if it does not have to. Where your language has no on-device model available, iOS falls back to server-based recognition, exactly as the system keyboard's own dictation does, and the audio is processed by Apple. This is covered by Apple's Privacy Policy. The app requests microphone and speech recognition permission before this can happen.

Translating your prompt (Translation framework)

Used only when you tap Translate on your own typed text. iOS may download language assets from Apple to make a language pair available. The translation itself is performed by the system. Your text is not sent to us at any point.

Checking your purchase or trial (StoreKit)

Described in section 5 above. The app reads what this Apple Account owns at every launch and every return to the foreground, and those reads are served from the transactions iOS keeps on the device, so they work with no connection. Fetching the trial or the unlock from the store, activating, buying, redeeming a code and restoring all go to Apple over the network. Apple is told nothing about you that it does not already know, and we are told nothing at all.

The app uses no other network-capable service of its own. Text recognition, sensitive-data detection, redaction and everything else run entirely on your device.

7. On-device processing

These features never transmit anything anywhere:

• Reading textPDF text layers are read directly on the device. Apple's Vision framework recognises text in images and scanned PDF pages, and — if you switch it on in Settings — video frames. Version 1.1 also recognises text in images on PDF pages that carry a text layer.
• Finding sensitive dataPattern rules and Apple's NaturalLanguage framework look for secrets, emails, hosts, IP addresses, paths, card numbers and names.
• RedactionAnything you leave switched on is painted into the image, PDF or video, and replaced with a marker in your text, before the file is shared.

8. What redaction can and cannot promise

The app tries to find sensitive material and cover it before you share. It is not exact, and it is not a guarantee. In the app's own words:

Redaction can only cover what the app was able to read, and there are places where the reading stops:

• A PDF is read for its first 20 pages. Anything after page 20 is never read, so nothing on it can be found or covered.
• In version 1.1, PDF text layers and images on the page are both read. Native text is read directly; text in images and scanned pages is recognised on the device and can still be missed or read incorrectly. In version 1.0, a page with a usable text layer was read from that layer alone, so words inside images on the same page could be missed.
• Video frames are read only if you turn that on in Settings, and the walk through a clip stops after 3,600 frames, so a long recording may not be read to the end. Sound is never examined: a password spoken aloud in a recording is shared exactly as recorded.
• A text file is scanned only if it is under 512,000 bytes. A larger one is not partly scanned — it is reported to you as not checked, and shared exactly as it is.
• Marking something yourself works on the text the app managed to read. What was never read cannot be selected, and so cannot be covered.
• File names and whatever metadata a file carries are not examined and not changed. The one exception is deliberate: when covering something forces the app to re-encode a picture, the copy it shares is renamed to match what it now is — screenshot.png becomes screenshot.jpeg — so the file the other app receives is never mislabelled.

In every one of those cases the attachment is still shared in full. Unread is not the same as removed. Anything the app could not open or read at all is reported to you as not checked rather than as clean, and archives are refused as attachments outright, because nothing in the app can read inside one. You remain responsible for what you choose to send.

9. Permissions the app asks for

Each is requested by iOS the first time you use the feature, and you can withdraw any of them in the iOS Settings app at any time. The app does not request photo library access at all — choosing from your library uses Apple's out-of-process picker, which hands over only the items you select and shows the app nothing else.

10. Children

1m is a developer tool. It is not directed at children, and the app collects nothing from anyone of any age. The only thing that ever reaches us is a support message somebody chose to write.

11. Your rights

Regulations such as the GDPR and the CCPA give you rights of access, correction, deletion and portability over personal data a company holds about you. We hold none of it unless you have written to us, in which case we hold that message and the address it came from; reply and ask, and we will delete the thread. There is no account to close and no profile to request, because nothing reaches us on its own. Data held on your own device is under your control: clear History in the app's Settings, or delete the app to remove its container all at once — remembering that a backup you already made may still contain it, and that what Apple records about your purchase or trial is held by Apple rather than by us.

For material you have already shared into another app, those rights are exercised with that app's provider.

12. About this website

These pages are hosted on GitHub Pages. They load no fonts, scripts, images or trackers from anywhere. GitHub logs visitor IP addresses for the security of its service, as described in the GitHub Privacy Statement. We do not receive, access or retain those logs, and we place no cookies.

13. Changes to this policy

If this policy changes, the effective date above changes with it and the previous wording remains in the public page history. A change that materially affects what happens to your material will also be described in the app's release notes.

14. Contact

Questions about this policy, or about anything the app does with your material: asoft.general.support@gmail.com. See the support page for everything else.