Humanit is built privacy-first. Guest work is temporary by default, signed-in uploads use private processing access, and account content is saved only through documented features or an explicit Save action. Data is encrypted in transit and operational logging is designed to minimise content exposure. Platform-level file and backup retention is disclosed where Humanit cannot independently verify physical deletion. We monitor for abuse and welcome responsible disclosure of security concerns.
Privacy is not a feature of Humanit - it is the foundation. Every design and engineering decision starts with the question: "How do we minimise the data we hold and maximise user control?"
Our core principles are:
• Data minimisation: We collect and process only what is necessary to provide the service.
• Temporary guest processing: Guest content is processed for the requested task and is not added to account Saved Work.
• Private signed-in uploads: Signed-in files use private storage with short-lived processing access.
• Deliberate saving: Saved Work, reports and other account records persist only through documented save features and remain subject to user deletion and retention controls.
• Transparency: Our privacy practices are documented openly in this commitment and our Privacy Policy.
Humanit distinguishes temporary working data from account records that are intentionally saved.
Guest processing does not create Saved Work records. Signed-in uploads are placed in private storage and accessed for processing through short-lived signed links.
Generated content, reports and extracted text may be saved when a feature explicitly provides persistence or when you choose Save.
Clearing a browser workflow removes the visible working state, but it does not automatically delete separate saved account records or prove physical deletion of an underlying platform file.
When you submit a document for processing, it is handled as follows:
• Upload: Signed-in files use private Base44 storage. Guest files use a smaller transient request path and are not added to Saved Work.
• Processing access: Private files are opened through short-lived signed URLs, normally limited to five minutes.
• Processing: Extracted text may be sent to configured AI providers solely to perform the requested task.
• Output: Results are returned for review, download or an explicit Save action.
• Retention: Saved account records and platform file objects are governed separately. Humanit does not describe signed-link expiry as proof of physical file or backup deletion.
Humanit provides Clear, Delete and account privacy controls so users can remove working state and saved records where the feature supports it.
Browser session state may end when a tab or session closes, while local browser preferences can persist until cleared.
Saved Work and account records are separate from temporary working state and follow their documented retention and deletion controls.
Short-lived signed URLs expire automatically, but expiry only ends that URL's access and is not evidence that the underlying platform file or backup was physically erased.
All data transmitted between your browser and Humanit's backend is encrypted using HTTPS/TLS (Transport Layer Security). This protects your data in transit from interception or tampering.
Backend secrets and credentials are managed using industry-standard practices:
• API keys and service credentials are stored as environment variables, not in source code or client-side code.
• Sensitive identifiers, such as API client credentials, are stored as cryptographic hashes - never in plain text.
• Access to backend systems and secrets is restricted to authorised personnel only.
• Backend functions include security guards that validate request origins, file types, payload sizes, and rate limits to prevent abuse.
While we take strong measures to protect data in transit and at rest, no system can guarantee absolute security. We encourage users to exercise caution with highly sensitive documents.
Humanit does not add document results to Saved Work merely because you upload a file.
Signed-in users can deliberately save supported outputs, reports, translations and documents to their account. Those records remain until deleted or another documented retention rule applies.
Uploaded files used for signed-in processing are stored privately and opened through short-lived signed links. Base44 does not currently expose a general physical file-deletion API to this application.
Accordingly, Humanit does not promise that link expiry or removal of a database record has physically erased every platform file copy or backup. Formal deletion requests and platform retention controls apply where physical deletion cannot be independently verified.
Writing Signature is one optional saved profile in Humanit. Other account features can also store Saved Work, reports, translations, preferences and related records when the user chooses those features.
Writing Signature storage is strictly opt-in:
• No Writing Signature data is stored unless you explicitly create and confirm a signature.
• The decision to save is entirely yours - the service works fully without it.
• A saved Writing Signature contains style metrics only (vocabulary, tone, sentence structure, readability) - it does not contain your original documents or their content.
• You can delete your saved Writing Signature at any time.
If you do not opt in, Writing Signature analysis results are processed temporarily and discarded with your session.
Humanit logs operational metadata to maintain security, monitor performance, and troubleshoot issues. This metadata includes:
• Request timestamps and processing durations.
• Request status codes and error indicators.
• Anonymised IP addresses (used for rate limiting and abuse prevention).
• Browser and device type (for compatibility monitoring).
• Function invocation logs (stage, status, timing) - these contain diagnostic labels, not document content.
We do NOT log, store, or retain:
• The text content of your documents.
• The content of generated outputs or reports.
• Personal data from your documents (names, addresses, financial information, etc.).
Operational logs are retained only as long as necessary for security and troubleshooting purposes, and are then automatically purged.
Humanit implements multiple layers of security monitoring and abuse protection:
• Rate limiting: Requests are rate-limited per IP address to prevent automated abuse and denial-of-service attacks.
• Origin validation: Backend functions validate request origins to prevent unauthorised cross-origin access.
• Payload validation: File types, sizes, and content types are validated before processing to prevent malicious uploads.
• SSRF protection: Server-Side Request Forgery protections validate URLs and block requests to private/internal network ranges.
• Input sanitisation: User inputs are validated and sanitised to prevent injection attacks.
• Zip Slip protection: Archive-based file processing (DOCX) validates entry paths to prevent path traversal attacks.
These measures work together to protect both users and the platform from malicious activity.
We take security seriously and welcome responsible disclosure of potential vulnerabilities.
If you believe you have identified a security issue in Humanit, please contact us responsibly:
Email: [Insert security contact email]
Subject line: "Humanit Security Disclosure"
We ask that you:
• Provide sufficient detail to reproduce or understand the issue.
• Allow us reasonable time to investigate and address the issue before public disclosure.
• Do not access, modify, or destroy data that does not belong to you.
We are committed to acknowledging and addressing legitimate security reports in a timely manner.
Effective Date: 1 July 2026
Last Updated: 5 July 2026
Version: 1.0
Version History:
• v1.0 (1 July 2026): Initial publication of the Security & Privacy Commitment.
We will update this commitment as our security practices evolve. Material changes will be reflected in the version history and the Last Updated date.
How can we help?