Boardesa AI
Contact Open workspace
Product, privacy, and partnership contact

Bring the context.
Keep it useful.

Boardesa AI is in product preview. A focused first message helps route feedback without collecting information through a separate web form.

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.

Write an email

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 · EDUCATION

Teacher or student workflow

Include the level, subject, available material, desired output, and any school or academic-integrity constraints.

Open email ↗ 03 · PRIVACY

Privacy request

Explain the request and identify the relevant email interaction. Do not attach extra identity or student information unless needed.

Open email ↗ 04 · ACCESSIBILITY

Accessibility issue

Name the page, device, browser, assistive technology if relevant, and the exact action that could not be completed.

Open email ↗ 05 · SECURITY

Responsible security report

Share a reproducible description without accessing other people’s data, disrupting the service, or publishing an unverified exploit.

Open email ↗ 06 · PARTNERSHIP

Partnership idea

Explain the audience, mutual value, expected responsibilities, data implications, region, and whether technical integration is required.

Open email ↗ 07 · RESPONSIBLE AI

AI 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 ↗

Security researchers can also review the machine-readable security.txt reporting policy.

A useful first message

Five lines can save five replies.

Good context does not mean sharing more personal information. It means explaining the problem precisely.

  1. WhoStudent, teacher, tutor, school, or partner—without unnecessary personal details.
  2. GoalThe learning or preparation outcome you are trying to reach.
  3. Current frictionWhat takes too long, fails, confuses users, or produces weak results.
  4. EnvironmentRelevant device, browser, subject, level, or workflow constraints.
  5. Expected next stepWhether you want an answer, product consideration, correction, or discussion.
Current support boundaries

What the preview can—and cannot—handle.

AVAILABLE

Product and site enquiries

Feedback, content corrections, privacy questions, accessibility reports, education workflows, and partnership ideas can be sent by email.

NOT ACTIVE

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.

USE APPROPRIATE SERVICES

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 detail

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.