Product and site enquiries
Feedback, content corrections, privacy questions, accessibility reports, education workflows, and partnership ideas can be sent by email.
Product, privacy, and partnership contactBring the context.
Bring the context.
Keep it useful.
Boardesa AI is in product preview. Use the local brief builder to prepare a focused message, then open it in your own email application.
No website form databaseNo payment support yetDo not send student records
PRIMARY EMAILboardesa.com@gmail.com↗
Use a descriptive subject and include only the context necessary to understand the request. Never send passwords, private student records, payment details, API keys, or identity documents unless a secure process is specifically established.
Your chosen email provider and the recipient email service handle the message. Boardesa does not collect it through a website form.
Route the message
Start with the right subject.
These links open your email application with a suggested subject. You can edit everything before sending.
01 · PRODUCT
Product feedback
Describe the audience, the education task, what currently feels slow or unclear, and what a useful result would look like.
Open email ↗ 02 · EDUCATIONTeacher or student workflow
Include the level, subject, available material, desired output, and any school or academic-integrity constraints.
Open email ↗ 03 · PRIVACYPrivacy request
Explain the request and identify the relevant email interaction. Do not attach extra identity or student information unless needed.
Open email ↗ 04 · ACCESSIBILITYAccessibility issue
Name the page, device, browser, assistive technology if relevant, and the exact action that could not be completed.
Open email ↗ 05 · SECURITYResponsible security report
Share a reproducible description without accessing other people’s data, disrupting the service, or publishing an unverified exploit.
Open email ↗ 06 · PARTNERSHIPPartnership idea
Explain the audience, mutual value, expected responsibilities, data implications, region, and whether technical integration is required.
Open email ↗ 07 · RESPONSIBLE AIAI safety or quality issue
Describe the affected workflow, the expected behaviour, what occurred, and a non-sensitive example. Do not send private student records or exploitable security details.
Open email ↗08 · TECHNICALTechnical or session issue
Share the affected page, exact action, expected result, safe diagnostics report, and a redacted reproduction. Do not attach a full session unless specifically needed.
Open email ↗Review the Security page before sending a vulnerability report. Security researchers can also review the machine-readable security.txt reporting policy. Accessibility support and known limits are documented on the accessibility page. Start with the Help Center for recovery steps and a privacy-safe diagnostics report.
Local message builder
Prepare a useful email
Prepare a useful email
without oversharing.
Complete the fields below to create a clear support brief. Everything stays in this browser until you choose to open your email application or copy the message.
No form submission, account, tracking event, or website database is used for this message.
Current support boundaries
What the preview can—and cannot—handle.
Billing and account recovery
There are no paid subscriptions, credit purchases, user accounts, or cloud histories, so no charge or account-recovery support exists yet.
Emergencies and professional advice
Boardesa contact is not an emergency, safeguarding, legal, medical, or crisis channel. Use the appropriate qualified or local service.
Privacy before detailSend enough context.
Send enough context.
Not every detail.
The safest support request excludes secrets and sensitive education records unless a secure, necessary process has been established.
01Remove student names and identifiers from examples.
02Never send a password, payment number, or API credential.
03Use screenshots only after checking what else they reveal.
04For privacy requests, identify the relevant interaction without oversharing.