Privacy and Data Handling

HumanLike is designed to keep processing boundaries clear: input handling, output generation, and plan-gated history behavior.

Operational metadata and usage limits are tracked to enforce quotas and product functionality.

This page explains what is stored for product operation and what should be treated as sensitive by default.

Processing boundaries

Text submitted for rewriting or detection is processed to return requested output and related scoring metadata.

Operational logs may include request metadata needed for reliability and abuse prevention.

History and usage records depend on account status and plan features. Free plans may have reduced history visibility.

Teams should avoid submitting secrets, credentials, or regulated data unless their policy explicitly allows it.

Use account controls and billing ownership checks to reduce unauthorized subscription changes.

Treat all generated output as user-content requiring final review before publishing or compliance use.

Should sensitive secrets be submitted to rewriting tools?

No. Avoid sending credentials, API keys, or confidential records unless policy explicitly permits it.

Is usage data tracked?

Yes. Usage counters are needed for plan enforcement and quota management.