Security and Privacy

The scope is the thread#

Vela participates in coordination on the threads it is explicitly CC'd on. Adding it to a thread is the act of granting it access to that conversation, and leaving it off a thread keeps that conversation outside its scope entirely.

This is a deliberate design choice: the permission model is the one your team already understands from working with a human coordinator. If you would not CC an assistant on it, do not CC Vela.

Calendar access#

Vela connects to your work calendar to read availability and to create and update invites. That access is what makes it possible to propose slots that are genuinely free rather than asking you to confirm each one.

Candidate and client data#

Interview coordination necessarily involves personal information — names, contact details, resumes attached to invites. Vela handles that material as part of the coordination it was asked to perform, and only for the threads it was added to.

For a formal review, Vela's privacy policy and terms of use are the authoritative documents, and the team will walk security and procurement teams through specifics on request.

Questions worth asking us directly#

Every organization has its own requirements — data residency, retention, SSO, DPAs, subprocessor lists. Those are conversations rather than documentation, and the fastest path is to raise them with the team during a walkthrough.