Support

For 1m: Private Prompt Composer version 1.1 guidance · Last updated 5 October 2026

What 1m does

Point your iPhone at the logs, the code or the error in front of you. 1m: Private Prompt Composer captures it, reads the text out of it, looks for what should not leave your phone and covers what it finds for you to review, builds a well-formed prompt around it, and hands the whole package to an AI app you already have — in one share or sequentially, depending on the share mode you choose.

There is no API key to buy, no subscription to us for tokens, and no account to create. The app prepares the request; you send it, from an app you already use on your device, and the answer comes back there.

What changes in version 1.1

The changes below apply to version 1.1. If you are using an earlier version, some features will behave differently. You can check your installed version in Settings.

• Hindi joins English, Ukrainian, German and Russian. Choose your app language in Settings → Appearance → Language.
• PDFs with both text and pictures are read more thoroughly. The app keeps the native text and also recognises text in images on the page. Scanned pages are read too; the limit remains the first 20 pages.
• Name detection and text masking are improved. Detection can still miss sensitive information, so review every request before sharing it.
• Redaction changes made during preparation are included before Share becomes ready. The prepared request and the saved History copy use those final choices.
• Newly prepared History entries keep their saved prompt and files. Changing your settings or templates later does not change those entries. Older entries have some limits.
• Custom prompt templates save more reliably. If a save fails, your edits stay in the editor so you can try again.
• Sensitive-data checks are faster for repeated text lines. Video text recognition can still take time.

Requirements

• iPhoneiPad is not supported in this version.
• iOS 18.0 or laterRequired for the built-in translation feature.
• Portrait orientationThe app is designed for portrait only.
• A destination appAny app that accepts shared text, images, videos and files.

How a request works

1. Attach. Take a photo or video, choose from your library, or attach a file. You can also just type or dictate.
2. Describe. Write your prompt, with a formatting panel, dictation and translation to hand. Pick a system prompt pattern, or none at all.
3. Prepare. The app opens and weighs the attachments, reads the text out of them, finds and covers what looks sensitive, composes the prompt and packs the payload — showing you each pass as it runs.
4. Review, then share. Check what was found in Sensitive data, read the whole assembled payload in Preview → See the full payload, then press Share and pick your destination.

Access: what is free, what is paid

There is one app, one optional purchase and no subscription. Nothing renews, nothing is charged automatically, and there is nothing to cancel. Your access status is the Access row in the Settings tab; everything below is reached from there or from the screen it opens.

Without a trial or a purchase

The app works, with a reduced set of features. You can type or dictate a prompt, prepare it, and share it, and everything already saved in History stays available to re-share. What a limited request does not get: attachments, system prompt patterns, the choice of share mode (it uses One shot), and the two passes that read the text out of attachments and cover what looks sensitive.

The free three-day trial — you start it yourself

Nothing starts a trial on its own. Opening the app does not start one, and neither does looking at the purchase screen and closing it. The trial is a free item you activate with the App Store: tap Try free for 3 days in Settings and then Start 3-day trial — Free, and confirm with Apple the way you would confirm a purchase — except that it is free, nothing is charged when it ends, and there is nothing to cancel.

It gives you every feature for 72 hours from the moment Apple records the activation. That is wall-clock time: closing the app does not pause it. Activating needs a working connection to the App Store; once activated, the rest of the trial works offline. Because Apple holds the record rather than the app, reinstalling or setting the app up on another device keeps the same deadline instead of starting a fresh trial. Family Sharing does not pass a trial on — it applies to Full Access, below.

Full Access — the one-time unlock

A single purchase, made once. It is not a subscription: there is nothing to renew and nothing to cancel. We do not quote a price here — the App Store shows you the current price for your country and currency before you confirm, and that is the only number that counts. You can buy it at any time without starting a trial first.

Full Access belongs to your Apple Account rather than to one iPhone, so it works on any device you sign into, it comes back after a reinstall, and it can be shared with your family if you have Family Sharing turned on.

Restore purchases

In Settings, under your access status. It asks the App Store again what your Apple Account owns and applies the answer. Use it after reinstalling, on a new device, or if the app has the wrong idea about your access. It is the only control that forces a fresh check, it needs a connection, and Apple may ask you to authenticate.

Offer codes

If you were given an Apple offer code, press and hold your access status in Settings and choose Redeem offer code. Apple's own redemption screen opens; Apple checks the code and grants the access if it qualifies. The app does not validate codes itself. If you hold an older access code from us that predates this, the Access row will say so and ask you to request a replacement.

Refunds

Requested from Apple, not from us. Once you have a purchase of your own, a Request a refund button appears under your status and opens Apple's own sheet. Apple decides; we have no role in approving or refusing one. If a refund is granted, the app stops seeing the purchase and returns to the reduced set of features.

Limits

What the app can read, and what it cannot

Covering a secret depends on first reading it. Anything the app could not read cannot be covered — and it is still included in what you share, exactly as it was. These are the edges worth knowing before you send something:

• Images are read whole, on your device.
• PDFs: the first 20 pages. In version 1.1, the app reads a page's text layer directly and also recognises text in images on that page; scanned pages use text recognition too. Recognition can still miss text. In version 1.0, a page with a usable text layer was read from that layer alone, so text inside pictures on the same page could be missed. Pages past the twentieth are not read at all, and they still go over with the file.
• Videos: reading text in videos is off by default (Settings → Read text in videos), because it is slow. Even switched on, the app examines at most 3,600 frames, so a long, low-bitrate clip may not be covered to its end. The sound is not examined at all — a password spoken in the audio track is shared as recorded.
• Text files are read and scanned up to 512,000 bytes. A larger one is reported as not checked rather than partly checked, and is shared in full.
• Anything the app cannot open is reported to you as not checked — never as clean.
• Covering something yourself by selecting it only reaches text the app actually recognised. Where nothing was recognised there is nothing to select.
• File names and embedded metadata are not a redaction surface. A file called prod-db-password.png is shared under that name. The one time a name changes is when covering something forced the picture into a different format — the copy you share is then renamed to match what it really is, so screenshot.png may arrive as screenshot.jpeg.

The safest habit is the one the app is built around: open Preview → See the full payload and read what is actually going out before you press Share.

Known issues

If 1m becomes unresponsive after sharing

This was reported before version 1.1: after handing a prepared request to another app through the share sheet, returning to 1m could leave it unresponsive. The cause is not established, and a fix has not been verified for version 1.1. The recovery advice below remains available if you encounter it.

The recovery we have observed: close 1m from the app switcher — swipe up from the bottom of the screen, hold, then flick the 1m card away — and open it again.

Requests that finished preparing are saved in History, so a prepared request is normally still there when you come back. A preparation that had not finished is not necessarily saved; if you do not find it, prepare it again. If this happens to you, telling us your 1m and iOS versions, which app you shared into, and the types and sizes of attachments is exactly the report that would let us pin it down.

Questions people ask

Do I need an API key, or to pay for tokens?

No. 1m never calls an AI service itself. It prepares your request and hands it to an app on your phone through the standard iOS share sheet; that app answers using whatever plan you already have with it.

Where does my material actually go?

Nowhere, until you share it. Capture, text recognition and redaction all run on your device, and there is no server of ours, no backend, no analytics and no third-party SDK anywhere in the app. The only network activity is iOS talking to Apple on the app's behalf — the App Store for your purchase or trial, dictation where your language has no on-device model, and downloading translation assets — plus the two links and the mail draft in Settings, which open your browser or your mail app and only when you tap them. When you press Share and pick a destination, your content goes to that app, and its privacy policy applies from there. The privacy policy sets this out in full.

Is the secret removal guaranteed?

No, and the app says so on two screens. Text can be missed on a blurry or angled picture, a secret in an unusual shape may not be recognised, and something harmless can be covered instead. Redaction can only cover what the app could read; anything it could not open is reported as not checked rather than as clean, and unread content is shared as it is. See what the app can read, and what it cannot above, and always review before you share.

Why does the app want the camera and microphone?

The camera photographs or records what you want explained. The microphone records sound while you are filming, and powers the dictation button beside your prompt. Both are optional — you can attach files and type instead — and you can withdraw either in iOS Settings at any time. The app never asks for photo library access; choosing from your library uses Apple's own picker, which shows the app only what you select.

Text was not read out of my video

Reading text in videos is off by default, because it is much slower than reading a still. Turn on Read text in videos in Settings. Two things to expect once you have: a long hand-held clip can take minutes to process, since almost every frame is different and each one is read; and the app examines at most 3,600 frames of a clip, so a long, low-bitrate recording may stop short of the end. Whatever was not read is not scanned either — but the video itself is still shared in full.

My purchase or trial is not recognised on this iPhone

Open Settings and press Restore purchases under your access status. That is the one control that asks the App Store again; it needs a connection, and Apple may ask you to authenticate. If the status reads Limited · Not verified, the App Store could not answer at all — connect to the internet and use Check again. If a trial you activated appears to have ended early, remember that the 72 hours run as wall-clock time from Apple's record of the activation, whether or not the app was open.

Can the answer come back in my language?

Yes. Reply in the app's language in Settings is on by default. When the app is set to anything other than English, an extra instruction is added asking for the response in your language — while explicitly asking that code, identifiers, class and method names, error names, log lines, commands and paths are left exactly as they are, so the answer stays searchable and pasteable.

What languages does the app support?

Version 1.1 supports English, Ukrainian, German, Russian and Hindi (हिन्दी). Choose in Settings → Appearance → Language, independently of your iPhone's language. Version 1.0 supports the first four. Permission dialogs are drawn by iOS itself and follow your phone's language rather than the language selected inside 1m.

Dictation is not working

Hold the microphone button down — it records for as long as your finger is on it and stops when you lift it. It is not a tap-to-toggle button. Also check that microphone and speech recognition permissions are granted in iOS Settings.

How do I see the introduction again?

Open the ⓘ on the New request title line on the Main tab and tap Show the interactive introduction at the bottom.

Which version of the app am I on?

Open the Settings tab and look near the bottom of the page, below the support and privacy links. A small grey line there reads something like Version 1.1 (5) — the first number is the release and the number in brackets is the build. Please include the whole line when you report a bug; two builds can share a release number and behave differently.

Does changing a template change my saved requests?

For requests prepared in version 1.1, no. History keeps the prepared prompt and attachment copies as they were when saved. Changing your language, settings or custom templates later does not rewrite those entries. If you change redactions after a request has been prepared, the updated request is saved separately.

Requests saved by older versions did not retain the complete original prompt. On upgrade, 1m preserves what it can recover and labels these entries as reconstructed. A custom prompt deleted before the upgrade cannot be recovered. Check the preview before re-sharing an older request.

History says it needs attention

That screen appears when the small file listing your saved requests cannot be read. Nothing has been deleted — your saved requests and their attachments are left exactly as they were, and the app refuses to write anything more to History until the matter is settled. Preparing and sharing carry on working. The app keeps a small copy of the previous listing beside the current one and rebuilds from it automatically when it can, so reaching this screen means that did not work either. Try again re-reads from scratch, which is worth one press — a read can fail because the device was busy rather than because anything is wrong. Remove everything History has kept is the destructive way out and is behind a confirmation; it does not touch your settings or the system prompts you wrote.

What does the app remove, and when?

Four different things, and they are not removed by the same action:

• Clear History (in Settings) removes your saved requests and the copies of their attachments, including the small retained copy of the previous listing. It does not remove your settings, and it does not remove the system prompts you wrote yourself.
• Deleting the app removes the app's own container: History, your own system prompts, your settings, and anything still in temporary storage.
• What is not in that container. What you own with Apple — Full Access, and a trial once you have activated one — is held by Apple against your Apple Account, so deleting and reinstalling the app does not give you a fresh trial. One small item can also remain in the iOS Keychain: a clock marker with no personal data in it, written only once a trial has actually been activated. If you never activate a trial, the app writes nothing there at all.
• Your own backups. History lives in Application Support, which ordinary iCloud and encrypted local backups include. Nothing goes to us, but a copy can exist in your own backup after you have cleared History on the phone, and restoring that backup brings it back. If you would rather it did not, clear History before a backup runs, or turn this app off in your iCloud backup settings.

Reporting a bug

Two ways, and they reach the same mailbox.

From inside the app: Settings → Report a problem opens a new message in your own mail app, addressed to us, with the subject carrying the app version, one sentence asking what happened, and four technical lines — app version, iOS version, device model identifier (something like iPhone17,1) and the language the app is set to. The app sends nothing. The message sits in your Drafts until you press send, and you can read, edit or delete any line of it first — which is precisely why those facts are written in the body rather than attached. No logs, no attachments and nothing you typed into the app are included. If no mail app answers, the address is copied to your clipboard instead. That row is part of the full feature set, so it is available during a trial or with Full Access; this page and the address on it are open to everybody.

Or email us directly at asoft.general.support@gmail.com and include, as far as you can:

• The version line near the bottom of the Settings tab
• Your iPhone model and iOS version
• What you did, what you expected, and what happened instead
• A screenshot, if it is something you can see

Please do not send us your logs, screenshots of production systems, keys or customer data to illustrate a problem. If a bug involves a specific attachment, describe its kind and size rather than sending it. We would rather reproduce it ourselves than receive material you would not want to share.

What we receive when you write in

Writing to us is entirely voluntary, and nothing is sent until you press send. When you do, our mailbox receives what any email gives its recipient: the address you sent from, your subject and your message, and whichever of those four diagnostic lines you chose to leave in. Nothing else travels with it — the app has no analytics, no crash reporter and no identifier to attach.

It is a personal mailbox, read by the developer. What you send is used to answer you and to fix what you reported, and for nothing else: it is not sold, not shared and not used for marketing. Messages are kept only for as long as answering you and following the problem up requires; ask us and we will delete the thread.