Productivity and rewriting workflows
HumanizeAI Privacy Notice
A practical overview of text, account, and subscription data.
Data used to provide the service
Submitted text, account identifiers, usage records, and subscription status may be processed to operate HumanizeAI. Payment-card information is handled by Stripe, not stored in the website code.
Operational purposes
Data supports rewriting, account access, word-limit enforcement, history where configured, fraud prevention, support, and subscription management.
Review before adoption
This notice is a template for owner review, not legal advice. Confirm production retention, processors, security practices, contact details, and applicable privacy rights before relying on it.
Retention and access
Retention periods and staff access should be limited to what is necessary for service delivery, security, support, and legal obligations. The owner must document the production settings actually used. Users should avoid submitting secrets or sensitive information unless the owner has expressly approved that processing.
Your choices and requests
Depending on location, users may have rights to request access, correction, deletion, restriction, or information about data handling. A production notice should identify the correct contact method and explain how identity is verified. Subscription cancellation is handled separately through Manage billing or support.
Service providers and changes
Authentication, payment, hosting, database, analytics, and rewriting providers may process limited information to perform their services. The final notice should name or categorize current providers as required, explain material updates, and state an effective date only when the owner can maintain it accurately.
Ready to revise a draft?
Return to HumanizeAI for one free humanization of up to 150 words without signing up.
Humanize AI text