Security

Your work stays yours. Founders give AdvisorI, reAlIze and prepAIr their business ideas, financials and deal documents. Here is how we protect them, in plain terms.

Every connection is encrypted

All traffic between your browser and Buildari runs over HTTPS, and so does every connection between our servers and the services we use.

Stored data is encrypted

Our database provider, Supabase, encrypts stored data at rest with AES-256.

Sign-in is handled by a dedicated identity provider

We use Clerk for accounts and sign-in. We never see or store your password.

Your data is locked to our servers

Each product keeps its data in a separate, access-controlled database area. The keys a web browser uses cannot read those tables, and an automated check blocks any release that would open them.

Errors never expose our internals

If something fails, you see a short message and a way to try again. The technical detail goes to our logs, not your screen. An automated check blocks any release that would show a customer raw error text.

We don't hold your card

Payments run through Stripe, and on mobile through Apple. We never store your full card number.

Changes to our systems leave a record

Every change to pricing, plan limits or which AI model serves a feature is logged with who made it, when and why. Every access to a voice transcript is logged too.

AI processing

Your content goes to Anthropic's Claude models only to produce the result you asked for. We don't sell your content, and it isn't used to train other companies' models beyond what the service requires. If we ever send your content to a different AI provider, we'll say so on this page first.

Who's responsible

Matt Newman, Buildari's founder, is our lead security and intrusion expert. He reviews how our products handle data and leads the response if anything goes wrong.

Report a concern

If you think you've found a security problem, email matt@buildari.ai. We'll respond directly.