What Naturalyx's Privacy Policy Really Says

gavin

We paste drafts and confidential work into AI writing tools without asking where the text goes. Naturalyx's privacy policy (

your original and rewritten text are never stored in its database.

That sounds like marketing. After reading it closely, I found a disciplined logic underneath. Here's what it means for real users—and where you still need to be careful.

Naturalyx states plainly that it does not keep your original or rewritten text. Job history stores metadata only—word counts, options, status, timestamps.

Most tools retain your input by default for "service improvement." Naturalyx keeps only the trace of the operation, not the content itself. If you handle sensitive material—legal drafts, internal memos, unpublished writing—this meaningfully lowers the risk of your content being reused or exposed. Even in a breach, an attacker gets "a user rewrote 500 words," not the 500 words.

Section 4 is honest: your text is sent over encrypted connections to a third-party rewrite provider. Naturalyx doesn't retain the body text, but the provider may process it, governed by its own terms and the vendor agreement.

"We don't store it" does not mean "no one stores it."

 Naturalyx can pick vendors and encrypt transmission, but it can't promise zero retention on the provider's behalf.

The tool may save a local draft in your browser so you can keep editing. Useful when you close a tab by accident. But on a shared computer, that draft may be visible to the next person.

Naturalyx says it directly: don't paste secrets or credentials into the tool. That's honest—it acknowledges the tool's limits rather than shifting blame.

The policy lists account data (email, name, avatar), usage metadata (word counts, options, status, latency, errors), billing data (plan, subscription status, payment references), and technical logs for security and abuse prevention.

—Naturalyx does not sell personal data or use rewrite content for advertising, a deliberate choice to forgo revenue. Second, 

; the payment provider handles them. By data-minimization standards, this list is sound—nothing hoarded "just in case."

Account and billing records are kept while your account is active and as legally required. Job metadata supports quota history and abuse prevention. Rewrite body text is not retained after the session completes.

The first two lack exact timeframes—common, but it means you can't know precisely how long metadata lives. The third is explicit and matters most. If you want account data deleted, the policy provides a contact channel, and EU or California residents can invoke GDPR/CCPA rights.

It suits users who rewrite text often but don't want originals on a server, who understand online-tool risks, and who value a model that doesn't sell data or run ads.

It does not suit those who want a guarantee that nothing will ever leak—no online service can offer that—or who are handling top-secret information that shouldn't enter any online tool.

Conclusion: A Policy That Reads Like a Product Manual

Most privacy policies are written for lawyers. This one reads like it was written for users. It doesn't say "we take your privacy seriously." It tells you what isn't stored, what is, why, for how long, and who else can see it.

That's a form of respect. It lays out the trade-offs and lets you decide.

If "content not retained long-term" is a core filter for you, a few minutes with this policy is worth it. It won't answer every privacy question, but it tells you clearly what kind of system you're dealing with.

0 comments