Flare

Trust

Your organization’s memory stays yours.

You’re putting how the company actually works into Flare. That deserves a page that isn’t buried in a PDF.

01

Tenant isolation

Workspace data is isolated with row-level security. One organization cannot read another’s graph.

02

MCP permissions

Tokens are hashed, scoped, and rate-limited. Read vs write is explicit. Nothing is open “for convenience.”

03

Agent writes are reviewed

Publishing a plan, executing proposed changes — designed to require a human. Arlo is eager. Arlo is not unsupervised chaos.

04

Audit logs

Ticket changes, plan publication, agent task execution. Admins can see who changed what.

05

Meeting recordings

Calendar connect is optional. Recording is a separate, explicit action. We log the consent event.

06

Customer data

If you embed Kiro, you are the controller. Evidence uses time-limited signed URLs.

07

AI processing

Gemini under an agreement that prohibits training Google’s general-purpose models on your data.

08

Retention

Tied to plan. Deletes leave active systems promptly. Encryption in transit.

Questions

hello@flares.in

Privacy →