Every fact on this page is how Humainum already works today, on every plan — not a roadmap or a compliance claim we can’t back up yet.
How your data is handled, how AI services are involved and what we have not published yet are explained in plain language on the Trust & Privacy page.
Every project gets its own PostgreSQL schema with scoped access. Database, GitHub and API-key access are protected per project, not shared workspace-wide.
Every plan gets a real GitHub repository from day one. Clone it, run it on your own servers, or bring in another team whenever you want.
Connect your own LLM provider credentials and control exactly which model your project’s work runs on.
Credentials and integration tokens are encrypted at rest. Transport encryption protects data moving between you, Humainum and connected services.
Access controls, transport encryption, monitoring and data-minimization safeguards, as described in our Privacy Policy.
Request access, correction, export or deletion of your information at any time. Disconnecting a connected account (like Instagram) removes its stored authorization token immediately.
The complete, legally binding version of all of this lives in our Privacy Policy and Terms of Service — this page is a plain-language summary, not a replacement for them. Privacy Policy and Terms of Service.
Technical controls
Only controls we have verified are listed. Anything we cannot yet document is left out rather than implied.
You can sign in with an email address and password, or with a Google or GitHub account.
Account passwords are handled by the platform's identity framework and are not stored in readable form.
Sessions use signed tokens that expire.
Access to a project is checked against the permissions of the signed-in account.
Credentials and integration tokens are encrypted at rest, and transport encryption protects data moving between you, Humainum and connected services.
Each project has its own database schema with scoped access. Database, GitHub and API-key access are protected per project, not shared across the whole workspace.
When an expert helps with your project, they work inside the same Humainum project environment, and you review their work before it goes live.
Humainum sends only the context required for a requested AI operation to the configured AI provider.
Provider keys you save are stored encrypted and are never sent back to your browser.
Not yet published Where an AI request is processed depends on the provider that handles it. We do not yet publish processing locations provider by provider.
Depending on your location, you may request access, correction, export, restriction, objection or deletion of your personal information.
Project and conversation data is kept while it is needed to provide the service, or for the retention period selected in your settings. It is then deleted or anonymized, unless a longer period is legally required.
To raise a security question or concern, contact the team through our contact page.
A security review, a data-processing agreement, a custom contract — tell us and we’ll work through it directly.
Talk to us
