Support

Aurora is a free beta with one maintainer, and this page is the whole of its support: one email address, an honest list of what does not work yet, and the procedure we follow when something we published turns out to be wrong. There is no ticket system, no chat widget and no phone number — you write, and a person reads it.

Contents

1. The one address
2. Who reads it, and what we do not promise
3. What makes a beta report useful
4. What the beta cannot do yet
5. Deletion and privacy requests
6. If something here is wrong

The one address

Bug reports, questions, deletion requests, corrections to this website and anything else about the beta go to one place: hello@auroraisyours.com. It is an address on this domain, routed by Cloudflare Email Routing to the maintainer's own mailbox, so a message to it lands in an inbox rather than in a queue.

There is no support portal to sign into, no live chat and no phone line. A beta with a single maintainer has a single inbox, and saying so is more useful than a form that answers with a ticket number.

If your message is about a diagnostic report you already sent from the app, include the ticket identifier Aurora showed you after the upload. That identifier is the only reliable way to find one report among others, for the reason the Privacy Notice gives under Diagnostic reports: a report carries no account identifier to look you up by.

Who reads it, and what we do not promise

Aurora has one maintainer, Leandro Piccione, and he reads the mail. Nothing is triaged by a robot and nothing is auto-acknowledged, so an answer you get was typed by the person who can change the code — and a quiet inbox is one person being busy, not a queue ignoring you.

We publish no service level and no response time. There is no measured history of replies here to derive one from, and an invented one would be the first promise on this site to break. Expect a human answer rather than a fast one.

What makes a beta report useful

Three things, and they are the three the beta page asks for:

• What you were doing. Recording a meeting, reading the live transcript, asking Aurora a question, exporting a transcript — the step you were on when it went wrong.
• Which iPhone. The model and the iOS version. The on-device work is the whole product, so the hardware it ran on is half of any report about speed or heat.
• What happened instead. What you expected, and what the app did. A screenshot of the wrong output says more than a paragraph describing it.

For a crash, or anything you can reproduce, the app's own report form carries more than an email can: it attaches the technical diagnostics with it. One switch governs whether the report also carries that session's transcript, its Ask Aurora chat, its recording and a screenshot — and when you open the form from inside a session, that switch starts on. Look at it before you send. Turning it off still leaves the diagnostics that explain most failures, and it keeps the conversation on your phone; Diagnostic reports lists exactly what each state attaches.

What the beta cannot do yet

These are the limits testers actually run into, each with the status label this site uses for it and what to do in the meantime. The labels are the same three everywhere here — Available in beta, Experimental in beta, In development — and the full list is on the beta page.

Available in beta, with an edge worth knowing

• Export is plain text. A transcript leaves the app as plain text, and that is the only format it writes today. Export the text to wherever you need it and leave the session in the app, which is where the recording stays.
• Timestamps are labels, not controls. Every speaker turn carries its own time, but tapping one does nothing: the app has no audio playback, so there is no tap-to-seek and nothing to seek through. Read the time as context on the transcript. It is not on the In development list below either, so read it as a description and not as a plan.
• A session report starts with the session attached. The report form's one content switch opens on when you report a problem from inside a session, so the decision in front of you is whether to leave your transcript attached rather than whether to add it. Turn it off before sending if the conversation should not travel.

Experimental in beta

• Languages other than English. The speech models cover many languages, and we have published no per-language accuracy measurement — so quality varies and we cannot tell you by how much. Name the language in your report; on a transcription bug it is the most useful line in it.
• Sessions much longer than an hour. Our own first-party evidence runs to about an hour of continuous recording, and past that there is no measurement to stand on. For something long and important, record it in parts, and tell us the iPhone and the duration if it struggles.
• The second pass that refines a finished transcript. It runs after a recording ends, and how it is scheduled and accepted is still being consolidated. If a refined transcript reads worse than the live one did, that is worth a report and a screenshot of both.

In development

• Recognizing the same speaker in a later conversation. A name Aurora reads out of one conversation is stored with that session, not learned as a voiceprint, so the next recording starts from unnamed lanes again. If nobody says a name aloud in it, the lanes stay Speaker 1 and Speaker 2 — there is no control for typing one in.
• Search and answers across conversations. Ask Aurora answers from the session you have open. To ask about an older conversation, open that one and ask there.
• Conversations syncing between devices. The library belongs to the iPhone that recorded it, and a second device will not see it. Export the text if the words have to be somewhere else.
• The Mac app. Mac is in development and not released: there is no build to install and no TestFlight for it. Record on the iPhone.

Deletion and privacy requests

Two different things sit in two different places, and only one of them is in our hands.

• What the app holds is on your device. Audio, transcripts, summaries, notes and Ask Aurora chats live in the app's library on the iPhone that recorded them. We do not operate a server that receives them, so we hold no copy to delete for you: removing them is something you do in the app.
• What this site holds is an email address. If you asked here for TestFlight access, that address sits with our mail provider, along with the time of the request, whether you asked for build notes, and any questionnaire answers you picked. Write to us from that address and we delete the contact, and everything stored against it goes with it; Deleting your data and unsubscribing is the procedure and the timescale we work to.
• A diagnostic report you sent is the exception. An encrypted report stays with us until it is closed and deleted, so that one you do have to ask about — with its ticket identifier. Diagnostic reports says what we can and cannot remove.

Three things you can do yourself, without writing to anyone:

• Forget this browser. The access sheet carries a start-over control, and it clears the one note this site keeps on your device — the address you last asked with, so that the sheet can show your link again. The note expires on its own after 180 days.
• Clear the tester questionnaire. Clear my answers, on the last page of the access flow, empties every answer you picked and touches neither your place on the beta list nor the build-notes opt-in.
• Unsubscribe. Every email we send carries an unsubscribe link, and using it stops that kind of mail straight away.

Your rights under the GDPR — access, correction, erasure, restriction, objection, portability, and withdrawing a consent you gave — are set out once, in the Privacy Notice under Your rights. They are stated in one place on purpose: two wordings of the same right are one wording too many to keep correct.

If something here is wrong

Every capability, availability, privacy and performance claim this website makes is a row in a public claim register kept in the site's own repository, with the page it appears on, the evidence behind it and a review state. A test reads that register on every build and fails when a page stops saying what the register claims for it, so the copy and the register cannot drift apart quietly.

So if a sentence here is wrong — it contradicts what the app does, or it promises something the product cannot keep — write to us and quote it. What happens next is fixed: the sentence and its register row are corrected in the same change, the change is reviewed, and it ships in an ordinary release. If a wrong claim is already live and cannot wait for that, the change that introduced it is reverted, or the deployment is rolled back to the last good one, and the proper correction follows.

If this website or the mail it sends is what is broken — a page failing, the access form refusing, the backup mail never arriving — the same address is how to tell us. There is no service status page here to check, and that is deliberate rather than missing: recording, transcription, speaker separation and summaries run on your iPhone and do not wait on a server of ours, so an outage of this site does not stop the app you already installed.

Get the TestFlight link

Not a tester yet? The beta is free while it lasts and the link is public — the beta page prints it as an ordinary link, with no email and no JavaScript needed.

See also

1. Privacy Notice — what the app keeps on the device, the named network paths that exist, and how to have your data deleted.
2. Terms of Use — beta software as-is, and Apple's TestFlight terms for the app itself.
3. Recording & Consent — recording other people, and your responsibility to them.
4. Try the free beta — the public TestFlight link, what an iPhone needs, and how to install it.
5. Engineering notes — first-party measurements of what the app does and what it costs.

Updated 2026-09-21, against the Aurora app source reviewed on 18 September 2026. If something on this page is out of date, that is a bug in the page, and the address above is where to report it.