Support

Send ordinary support requests to aidengrails@gmail.com. Use the in-product report action for a specific region when available. Privacy requests should go to aidengrails@gmail.com; copyright complaints should go to aidengrails@gmail.com and follow the Copyright & IP Policy.

Include your account email, the relevant region coordinates or identifier, transaction or listing identifier, date and time, what you expected, what occurred, and a screenshot or exact error message if useful. For payment questions, include only the Stripe Checkout or transaction identifier and the card brand plus last four digits if already shown to you.

Never send passwords, authentication links, a full card or bank number, card security codes, secret API keys, private keys, seed phrases, government identity documents, or other unnecessary sensitive data. We will not ask for those items by ordinary email.

Review the Purchase & Refund Policy. All sales are final after verified delivery except for its narrow mandatory exceptions. State whether the issue is duplicate billing, unauthorized payment, missing delivery, incorrect region, invoice access, or another concern. Do not file repeated requests for the same transaction.

For seller questions, include the listing and connected-account status shown in the dashboard. Identity, bank, capability, or payout-schedule issues may need to be completed directly in Stripe. A pending payout is not proof that funds have reached the bank. Refunds and disputes may create a hold or transfer reversal.

Signed-in users can download account data, submit a correction request, or delete a non-administrator account from the Account & Privacy dashboard. For an emailed request, identify the right you want to exercise and the jurisdiction that applies. We will use proportionate verification. Some transaction, tax, fraud, moderation, backup, or legal records cannot be deleted immediately. Account deletion and privacy requests must be tracked to completion by the operator.

Use the report tool for prohibited content. For a credible imminent threat or emergency, contact local emergency services first; this service is not an emergency provider. For a suspected vulnerability, describe the issue without accessing other users’ data, disrupting the service, or publicly disclosing an exploitable detail before we can investigate.

We do not promise a fixed response time. Payment delivery failures, active compromise, credible threats, child-safety reports, malware, and binding legal deadlines receive priority. Complex Stripe, bank, privacy, or legal matters may require additional time and verification.

If an issue remains unresolved, reply in the same thread with the original reference number and explain what remains outstanding. We retain support records as described in the Privacy Notice and may share limited details with Stripe, Supabase, hosting providers, advisers, or authorities when necessary to resolve the issue or comply with law.