Transparency
We say what we know, mark what we have not published yet, and keep this page in step with how Humainum actually works.
Trust & Privacy
Trust starts with transparency.
Understand how Humainum handles project data, works with AI services, and helps you stay in control of what you build.
This page is a plain-language summary, not a legal document. Where something is not yet published, we say so.
- Solid line: verified
- Dashed coral line: not yet published
01Our approach
Principles we build by
These describe how we work and what we hold ourselves to. They are not certifications.
User control
Your code, your connected accounts and your projects stay in your hands, with clear ways to export, disconnect or remove them.
Responsible data handling
AI providers should receive only the context an operation needs, and data should be kept only as long as it is needed.
Security by design
Separation between projects and encrypted credentials are part of how the platform is built, not an add-on.
Portability
Generated code lives in a real repository, so taking your work somewhere else stays possible.
Clear provider information
You should know which services touch your data. Where a list is not published yet, we tell you.
02Ownership
Your project, your control.
What you can rely on today, and where the limits are.
Portable generated code is not the same as self-hosting the Humainum platform.
Source code and repository
Every project is kept in a real GitHub repository from day one. You can clone the code and take it with you.
Deployment portability
The code Humainum generates for your project is portable. You can deploy it on infrastructure you choose or hand it to another developer.
Project isolation
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.
Access controls
Access to a project is checked against the permissions of the signed-in account.
Expert access
When an expert helps with your project, they work inside the same Humainum project environment, and you review their work before it goes live.
What stays hosted
The Humainum platform itself, meaning the AI agents, modules and expert network, runs as a hosted service. Only the code generated for your project is portable.
03Data
Where is your data processed?
A category-by-category view of what we process and why. Where we have not published a detail yet, such as the region, we say so instead of guessing.
Your project
Region not yet publishedAccount information
Verified- Purpose
- Signing in, account security, plan and billing contact
- Service / processor
- Humainum platform; Google or GitHub if you use them to sign in
- Retention
- See Privacy Policy
- Storage or processing region
- Not yet published
Select a category on the map to see how it is handled.
- Solid line: verified
- Dashed coral line: not yet published
View as tableHide table
| Data category | Purpose | Service / processor | Storage or processing region | Retention | Verification |
|---|---|---|---|---|---|
| Account information | Signing in, account security, plan and billing contact | Humainum platform; Google or GitHub if you use them to sign in | Not yet published | See Privacy Policy | Verified |
| Project content | Providing the features you use, such as chat history, business profile, CRM and bookings | Humainum platform | Not yet published | See Privacy Policy | Verified |
| AI requests | Running the AI operation you asked for | The AI provider handling the request (platform-managed or your own key) | Not yet published | Depends on the provider; not yet published | Verified |
| Source code | Building, previewing and syncing your project | Humainum platform; your project repository on GitHub | Not yet published | See Privacy Policy | Verified |
| Uploaded assets | Storing files you add to a project | Humainum platform | Not yet published | See Privacy Policy | Verified |
| Support communications | Answering your questions | Support tools | Not yet published | Not yet published | Not yet published |
| Payment-related information | Subscriptions and credit purchases | Stripe | Not yet published | Held by Stripe under its own terms | Verified |
| Logs and diagnostics | Operating and securing the service | Humainum platform | Not yet published | Not yet published | Verified |
"Verified" means the purpose and service wording in that row is confirmed. Any cell that says "Not yet published" is exactly that. Retention follows the Privacy Policy.
We do not yet publish the regions where data is stored or processed. We will publish a region only once we can verify it for every place the data is handled.
04AI
Understand how AI works with your data.
Two things can power an AI request: the platform, or a provider account you connect yourself. They are handled differently.
Platform-managed AI
You
Humainum
AI providerProcessing location not yet published
Platform-managed AI
With platform-managed AI, Humainum makes the AI requests itself, using the platform's own provider credentials and your plan's credits.
Your own provider key
You
Humainum
Your provider accountKey stored encrypted, never sent back to your browser
Your own provider key
With your own provider key, you save a key in Settings → AI Providers. Supported tasks then run on your provider account, under that provider's own terms. The providers you can connect are listed in Settings and may change.
Provider keys you save are stored encrypted and are never sent back to your browser.
What we send, and what to check
Humainum sends only the context required for a requested AI operation to the configured AI provider.
AI output can be inaccurate. Review it before you rely on it for important decisions.
Still being documented
Where AI requests are processed
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.
Provider retention and training
Not yet published We have not yet published a dedicated statement on how AI providers retain data or whether they use it to train models. Until we do, contact us for a written answer about your case.
Which providers
Not yet published A published list of the AI providers used for each feature is planned. Until then, you can ask us for the current list.
05Security
Security practices we can describe today.
A summary of the controls we have verified. The Security page goes into the technical detail.
Encryption
Credentials and integration tokens are encrypted at rest, and transport encryption protects data moving between you, Humainum and connected services.
Project isolation
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.
Authentication
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 controls
Access to a project is checked against the permissions of the signed-in account.
Safeguards in our policy
Our Privacy Policy describes the access controls, transport encryption, monitoring and data-minimization safeguards we use.
Security questions
To raise a security question or concern, contact the team through our contact page.
Backup protection
Not yet documented
Incident handling
Not yet documented
We list only controls we have verified. Topics such as backup protection and incident handling are not described here until we can document them.
Read the full security page06Third parties
Services that may be involved.
The services below are the ones we can confirm today. They process data only for the function shown.
Payments
Stripe
Takes payment for subscriptions and credits
VerifiedCode
GitHub
Hosts your project repository
VerifiedAuthentication
Google, GitHub
Optional sign-in methods
VerifiedConnected services
Instagram, Facebook, TikTok, YouTube, Google
Only if you connect them
VerifiedInfrastructure
Cloud hosting and DNS providers
Runs the platform and our domains
VerifiedAI services
Varies by feature and by your own key
Processes AI requests
Not yet published
Humainum runs on cloud infrastructure and uses DNS and publishing providers for its domains. The Privacy Policy names the providers that process data on our behalf.
If you sign in with Google or GitHub, that provider authenticates you under its own privacy terms.
Services you choose to connect, such as Instagram, Facebook, TikTok, YouTube or Google, process data under the permissions you grant and under their own privacy terms.
Not yet published A complete list of subprocessors is not yet published.
07Lifecycle
Retention, export and deletion.
What you can do with your data, and what we have not published yet.
- 01
Your rights
Depending on your location, you may request access, correction, export, restriction, objection or deletion of your personal information.
- 02
Export your code
Every project is kept in a real GitHub repository from day one. You can clone the code and take it with you.
- 03
Remove projects and data
Workspace owners can remove knowledge sources, conversations, connected accounts and projects from Humainum.
- 04
Disconnect services
Disconnecting Google or Instagram removes the stored authorization token and stops future access through that connection.
- 05
Retention
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.
- 06
Backups
Not yet published Backup retention periods are not yet published.
08Documents
Where to find the details.
The Privacy Policy and Terms of Service are the binding documents. Nothing on this page replaces them.
Privacy Policy
How Humainum processes personal information.
Terms of Service
The terms for using Humainum.
Security
Technical controls and safeguards.
Data processing agreement
Need a data-processing agreement or a security review? Tell us and we'll work through it directly.
Subprocessors
A complete list of subprocessors is not yet published.
Not yet published
Privacy inquiries
For privacy or deletion requests, contact the team through our contact page and include the Humainum account or workspace concerned.
The Privacy Policy and Terms of Service are the binding documents. This page is a plain-language summary.
09Questions
Common privacy questions
Have questions about your data?
Our team can help you understand Humainum's privacy and security practices.
Talk to usContent last reviewed by the Humainum team on October 9, 2026. This is an internal review, not legal approval.