Support
Something didn't work: a transcript that won't fetch, a document that won't extract, an export that failed, or a sign-in problem. Tell us the page, what you did, and the time it happened.
Contact us
GistCite is built and supported by a small team, and your message reaches a person, not a queue. Sign in and send it from here — no mail app needed — and we'll reply to your account email.
Send a message from your account
We reply within one business day
Monday to Friday; urgent outages are looked at the same day. Messages are tied to your account so we can reply to the right address. Locked out and can't sign in? Email support@transcriptfetch.ai from the address on your account.
What can we help with?
Billing
Questions about Pro, API, or annual billing, an invoice, a charge you don't recognise, or a refund request. Include the email on the account; never send card details.
Feedback & ideas
A tool you wish existed, a format we should support, or something that felt clumsy. Early users shape what gets built next.
Privacy & data
Export and deletion are self-service on the Account page. Write for anything the tools don't cover, or to ask what we hold about you.
Security
Found a vulnerability? Please report it privately before publishing. Describe the issue and steps to reproduce; we acknowledge reports and keep you informed until it's resolved.
Partnerships & press
Integrations, education or team licensing, and media enquiries. A sentence about who you are and what you have in mind is plenty to start.
Faster than email
Most questions are answered on these pages already.
User Guide →
Two minutes per tool, plus the FAQ on quotas, plans, devices, and file limits.
Pricing →
Free vs Pro vs API, monthly or annual, and what each unit buys.
Account →
Usage, billing portal, API keys, data export, and account deletion.
Security & Compliance →
What we do to protect your data and how it maps to GDPR, SOC 2, and the rest.
What to include so we can fix it first time
- The email address on your account, if you have one.
- The tool and page you were using, and roughly when it happened.
- The link, file type, or size involved — but never the file itself if it's confidential.
- The exact error message you saw. Our error pages show one whenever there is something useful to say.
Please don't send passwords, card numbers, or API keys; we will never ask for them.