EnemoAi

Security at EnemoAi

EnemoAi is a business adviser, so it holds things businesses care about: their questions, their documents and their money. This page says plainly how we protect them, and how to tell us if you find a problem.

Only verified people, only verified businesses

Your business's data stays your business's

In transit

The site and the API are served only over HTTPS (TLS). Sign-in cookies are HttpOnly and Secure, and every request that changes something must carry a header that only EnemoAi's own pages can send, so other websites can't act on your behalf. Sign-in with WorkPair uses OpenID Connect with PKCE and pushed authorization requests, and EnemoAi checks WorkPair's signatures on every sign-in.

Spending you can predict

Every question is priced before any work starts. Questions above the standard price run only after you approve the quote (or within an automatic-approval limit you set yourself), and nothing ever runs without wallet funds. Each question is priced so its estimated AI model cost is no more than 10.78% of its price, and its AI usage is metered against that budget; if a run goes slightly over, EnemoAi pays the difference.

A security log you can read

EnemoAi keeps an append-only security log for each business: sign-ins and sign-outs, invitations, role and spending-limit changes, removals, ownership handovers, access ended by WorkPair and account closure. The database refuses to edit or delete its entries. The owner and admins can read it in Account; it shows who did what and when, with a shortened network address, and never the content of anyone's questions.

Abuse

Requests are rate-limited per person and per business. Anyone can report a teammate or an answer to EnemoAi staff from inside the app; only EnemoAi staff see who reported whom. A ban applies to the WorkPair identity, so a banned person can't come back under a new EnemoAi account.

Report a vulnerability

Email hello@enemo.ai with what you found, how to reproduce it, and how we can reach you. We read every report, reply as soon as we can, and tell you when it's fixed.

While testing, please use only your own account and business, don't access or change other people's data, don't degrade the service for others, and give us reasonable time to fix a problem before you share it. Our machine-readable contact is at /.well-known/security.txt.