Support
There is no ticket queue and no chat widget. Write to info@readyaudit.dev and you get a reply from the same person who wrote the code the report came out of.
If you already have the app, Contact in the sidebar sends to the same inbox and attaches the app version and your device id for you. Both roads end in the same place; the form just saves you the details. If sending fails, it hands you the address rather than losing what you wrote.
Four things turn a message into an answer instead of a round trip: the audit id from the app, the rule id if your question is about a specific finding, the App Store transaction receipt if it is about a purchase, and what you expected to happen. Screenshots are welcome. Do not send credentials in an e-mail — a test login belongs in the audit submission form and nowhere else.
The target is 48 hours from the moment an audit is submitted to the moment the report is in the app. If a run fails, the build is held for a 72-hour retry window and then deleted — you are told which happened. The credit was spent when the audit was accepted and a failed run does not return it; what it still buys is up to two more builds against that same audit, inside that window.
Inside the app, on the audit. If you gave a notification address, we send a short message telling you it is ready — that message is a pointer, not the delivery. The report itself is never attached to an e-mail, and the address is erased on the send attempt whether it succeeded or not. Our mail relay adds its own unsubscribe link and an open-tracking pixel to that message and we cannot switch either off; using the link stops these notices without touching your reports, and the cookies page explains it in full.
Write to info@readyaudit.dev with the App Store transaction receipt Apple e-mailed you. A credit is granted only after the receipt is verified server-side, so a purchase that never granted one is a failure we can see and correct. Refund terms are on the refunds page below — read section 1 first, because what a credit buys decides what a refund covers.
Every finding carries the evidence it was derived from, so disputes are concrete rather than a matter of opinion. Send the audit id and the rule id and say what you believe the correct verdict is. If a finding is wrong we say so plainly and correct it; if it is right we show you which piece of evidence settles it.
Send the audit id from info@readyaudit.dev. The build, the recordings, the original screenshots and any credentials are already destroyed when the audit completes — what survives is the finding record, and that is what an erasure request removes. The privacy policy sets out the rest of your rights and who to complain to if we get it wrong.
Tell us at info@readyaudit.dev — the page, what you were using, and what stopped you. We publish an accessibility statement that says exactly what has been assessed and what has not, and a barrier you report goes on that page whether or not it is fixed the same week.
This goes to the same inbox as the address above. Nothing is stored — the message is relayed and forgotten, including the address you type.
Everything above is the short version of something written down. Refunds covers what a credit buys and when money comes back. Terms is the agreement itself. Privacy covers what we hold and your rights over it. Security covers what happens to your build. Accessibility states what has been assessed on this site and what has not.
ReadyAudit is a trading name of Buğra Günay, Türkiye. Technical readiness assessment — not legal advice.