Use this page for app access, payment fulfilment, recovery, refund, consumer-rights, privacy, accessibility, and abuse reports through CrowBot’s private ticket route.
CrowBot is operated by an Australian individual. For an enabled purchase, Stripe Checkout and the Stripe receipt identify the merchant for that payment.
Private ticket access
This form creates a private CrowBot support ticket. It does not ask for an email address. Your browser keeps only the ticket ID and a private access token so it can retrieve and reply to that ticket. Losing or forgetting that token can make the ticket unrecoverable from this browser.
Do not enter passwords, API keys, recovery codes, payment-card data, private brain exports, or personal information that is not needed to handle the request. No attachment or HTML upload is accepted.
Tickets and messages are retained for 2 years after the ticket’s last activity, then removed by bounded cleanup. Ticket creation is limited to 3 per hour per source and customer replies are limited to 20 per day per ticket. These controls do not promise a particular response time.
Create a support ticket
Interested in a physical CrowBot body? Tell Crow which country you are in and what you’d want from it. This creates a private ticket; no email needed.
No request has been sent.
Your saved support ticket
This ticket is available only while this browser retains its private access token. Forgetting it here removes only the local ticket ID/token; it does not delete the server-side support record.
Show the private ticket access token
Anyone with this token can read and reply to this support ticket. Store it like a password and never place it in a public issue, prompt, screenshot, or URL.
What to include in a request
Access or recovery
Do not clear browser data before exporting the readable brain if it is still available.
Keep the private recovery code outside the browser. Do not paste it into a general message.
Note the browser/device installation and whether the account panel shows an installation-slot or offline-authorization error.
Payment or fulfilment
Keep the Stripe receipt, Checkout Session reference, and CrowBot purchase reference.
If checkout returned but access is pending, use “Check access again” before trying anything else.
Do not make a duplicate purchase for the same missing fulfilment.
Technical issue
Record the exact route, device, browser version, time and time zone, online/offline state, and visible error.
Use the smallest screenshot or log excerpt that proves the problem.
Remove tokens, API keys, private prompts, brain data, and personal information not needed for diagnosis.
Refunds and Australian consumer rights
A change-of-mind refund is not promised. This does not limit consumer guarantees or remedies that apply to a faulty, unsafe, unavailable, or misdescribed supply. Depending on the type and seriousness of a failure, remedies may include repair or rectification, replacement, cancellation, a full or partial refund, and compensation for reasonably foreseeable loss or damage.
Use the private ticket form for access, correction, deletion, or privacy complaints. CrowBot may verify account and purchase ownership first. The sanitized text brain syncs to the account; local photos, folders, credentials, and exports stay under browser/file controls. Tickets and messages are retained for 2 years after last activity. Read the Privacy notice before clearing anything.
Security reports
Read the Security and responsible-disclosure page before testing or reporting a vulnerability. Submit only the smallest sanitized plain-text evidence needed to explain the issue; attachments and HTML are not accepted.
Owner support console
This console appears only when the current CrowBot access session is confirmed as an active owner session.