Support

How do I get help with Aurora?

Email hello@auroraisyours.com: it is the only channel, read by Leandro Piccione, who maintains Aurora, with no live chat, phone line or promised response time. What to send depends on what you need. For a bug, say what you were doing, on which iPhone, and what happened instead, or use the app's report form (as of October 2026 its session-details switch starts on). To delete your waitlist address, write from it or use your entry page; your recordings are on your device, and we hold no copy. For a wrong sentence on this site, quote it.

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.

The short version. Write to hello@auroraisyours.com. It reaches Leandro Piccione, who maintains Aurora and is the controller named in the Privacy Notice; there is nobody else for it to be routed to.

We do not publish a target response time, because we have never measured one, and a number invented for a support page is a promise nobody made.

Your recordings, transcripts and summaries are in the app on your device, and we hold no copy of them to delete. What this site holds is the email address you gave it, if you joined the waitlist, and we delete that when you ask.

The one address
Who reads it, and what we do not promise
What makes a beta report useful
What the beta cannot do yet
Deletion and privacy requests
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, tell us roughly when you sent it (the date, and the time as near as you remember it) and which version of Aurora you were running. The app does not show a ticket identifier after sending, and for the reason the Privacy Notice gives under Diagnostic reports, a report carries no account identifier to look you up by, so a time and a version are all we have to find it with. Even with both, we may not be able to tell your report apart from others sent around then.

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: the description you type is always sent, with the technical logs and diagnostics. A switch, Include session details in report, governs whether the report also carries that session's title, transcript, summary and Ask Aurora chat, a screenshot of Aurora's own window and any images you add, and that switch starts on. The recording has a switch of its own, which starts off. Look at both before you send. Turning session details 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 two everywhere here, Available in beta and 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. The recording itself is deleted from the phone after seven days (later, if it is still being refined), and the transcript 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 report starts with session details attached. The report form's session-details switch opens on, so the decision in front of you is whether to leave your transcript attached rather than whether to add it. The recording is the exception: its own switch opens off. Turn session details off before sending if the conversation should not travel.
Conversation sync is yours to turn on. With Sync conversations with iCloud on, the text of your conversations (transcripts, notes, summaries, chats and folders) syncs through your own private iCloud to your other devices where it is also on. It starts off on each device. The audio does not sync: it stays on the device that recorded it. Your settings follow your iCloud account either way, with no switch.
Languages other than English. They are available in beta. On a transcription bug, name the language in your report; it is the most useful line in it.
The second pass that refines a finished transcript. It runs after a recording ends. 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 works from the session you have open, and its grounded answers, which cite the moment in the transcript they came from, are in development too. To ask about an older conversation, open that one and ask there.
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. If you turned on conversation sync, the text is also in your own private iCloud, which we cannot read: deleting a conversation while sync is on removes it there too, and turning sync off leaves what is already in iCloud where it is.
What this site holds is an email address. If you joined the waitlist here, that address sits with our mail provider, along with when you joined, your place in line, the version of the consent you gave, and whether you asked for the newsletter. Write to us from that address, or use your entry page, 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 roughly when you sent it and the app version. Diagnostic reports says what we can and cannot remove.

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

See, change or delete your entry. The link in the email that says you're in, or in the note we send when you join again with an address already on the list, opens your entry page: your entry, and buttons to leave the waitlist, stop the newsletter or delete everything. A link works for 180 days.
Forget this browser. Once you have joined, the waitlist form shows your request instead of an empty form, from one note this site keeps on your device. "Not you? Start over" on that form clears it, and the note expires on its own after 180 days.
Unsubscribe. Every email we send carries an unsubscribe link, and using it stops every email from us straight away, your invite included. To stop only the newsletter or only the waitlist, use your entry page.

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 waitlist form refusing, the email saying you're in 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.

Join the waitlist

Not a tester yet? The beta is private and free while it lasts; how invites work explains the waitlist.