Trust

How Leap handles your documents.

Leap holding a padlock beside a small safe full of documents

No training on your documents

Not by us, and not by the AI model providers we use.

You approve before anything renders

Each scene sits beside its source line. Nothing renders until you say so.

Deleted when you ask

The source, the storyboard and the videos go together.

Processors, by category

Hosting, storage, AI models, narration and email. The five categories.

Report a vulnerability

Email sid@askleap.ai. The person who built it answers.

How your documents are handled

You send a document so Leap can turn it into a visual learning experience. Leap uses it to write the lesson and check every claim against it. Nothing else. We do not sell it, publish it, or reuse it for anyone else.

In transit
TLS, everywhere.
Where it runs
United States.
Export
Videos, transcripts and evidence reports, any time.

Who processes data

Leap runs on outside services in these categories:

  • Cloud hosting and delivery
  • Database and file storage
  • AI model providers, used under terms that prohibit training on customer data
  • Speech synthesis, for narration
  • Transactional email

Each one handles data only to provide its service to us. We share the named list on request, under NDA or in a data processing agreement. This site counts visits with cookieless, privacy-friendly page analytics; see Cookies.

Model training

None. We do not train models on your documents, and the AI model providers we use work under terms that prohibit training on customer data.

Retention and deletion

Your document is yours until you delete it. Ask us to delete a project and the source, the storyboard and the videos go with it. Write to sid@askleap.ai.

Access

Leap is one person during the private beta. Sid Abhinav, the founder, builds your first lesson with you and is the only person at Leap who sees your documents.

Reporting a vulnerability

Email sid@askleap.ai. You get an answer from the person who built it. Our contact details are also in security.txt.

Accuracy

Every claim in a Leap lesson is tied to the line of the source it came from, and you approve the storyboard before anything renders. See an example.