Cloud History Sync Banner

Introducing Cloud History Sync: End-to-End Encrypted History Across All Your Devices

TL;DR: CleanTextLab now syncs your tool history across all devices using end-to-end encryption. Your data is encrypted in your browser before upload - we literally cannot read it. Works seamlessly, costs pennies, respects your privacy.

Try it now: Sign in at cleantextlab.com/settings and enable Cloud History Sync ☁️

The Problem We're Solving

You're on your laptop. You clean up a huge customer list using CleanTextLab's duplicate remover. Perfect!

Two hours later, you're on your phone. You need to reference that cleaned list. But... it's not there. It's on your laptop. 😤

Sound familiar?

Until today, CleanTextLab stored your history locally in your browser. Privacy-first? Yes. Convenient across devices? Not so much.

We heard your feedback. You want both.

Introducing: Cloud History Sync ☁️

Starting today, registered users can enable Cloud History Sync - a seamless way to access your tool history from any device.

🔒 Here's What Makes It Special

Unlike most "cloud sync" features that upload your data in plain text to their servers, we built something different:

Your history is encrypted in your browser BEFORE it leaves your device.

That means:

✅ We cannot read your history (client-side encryption)
✅ Even if hackers breach our servers, your data is useless to them
✅ No government subpoena can force us to hand over readable data
✅ Your sensitive data stays YOUR sensitive data

This is the same encryption technology banks use. Military-grade AES-256-GCM encryption with PBKDF2 key derivation.

How It Works (Technical Deep Dive)

For the nerds (like us!) who want to understand exactly how secure this is:

1. Key Derivation

When you enable cloud sync, we derive an encryption key from your Clerk user ID using PBKDF2 with 100,000 iterations. This key never leaves your device.

2. Client-Side Encryption

Every history entry is encrypted in your browser using AES-256-GCM (Galois/Counter Mode) with a unique IV (initialization vector) per entry.

3. Upload Encrypted Blob

We upload the encrypted data to Upstash Redis. All the server sees is gibberish:

kF8nP3mQ9vL2xJ7tR1wZ4aH6bC0sD5eN8gY...

4. Cross-Device Sync

The server never sees your plaintext data. Ever.

Free vs Pro: What You Get

We believe privacy is a right, not a luxury. Cloud sync is available to ALL registered users, free or Pro.

Free Users (Registered)

✅ Cloud history sync
✅ 25 entries per tool
✅ 30-day auto-deletion (reduces liability)
✅ End-to-end encrypted
✅ $0/month

Pro Users ($5/mo)

✅ Everything free users get, PLUS:
✅ 100 entries per tool (4x more storage)
✅ 90-day retention (3x longer)
✅ Priority support
✅ API access
✅ File uploads (up to 10MB)

Upgrade here: cleantextlab.com/pricing

Privacy First: What We DON'T Store

Let's be crystal clear about what we can and cannot see:

❌ What We CANNOT See:

Your actual text/data inputs
Your tool outputs
Your metadata (beyond tool name)
Anything that could identify what you're working on

✅ What We CAN See:

Encrypted blobs (useless without your key)
Timestamps (for sorting)
Character counts (approximate, for UI display)
Tool names (e.g., "remove-duplicate-lines")

We built this system so that even WE can't snoop on your data. That's privacy done right.

How to Enable Cloud Sync (30 Seconds)

Sign up (if you haven't already): cleantextlab.com
Go to Settings → History & Privacy
Find the ☁️ Cloud History Sync section
Toggle it ON
Read the privacy notice (we're serious about this!)
Done! ✅

Your history will now sync across all devices where you're logged in.

Security FAQs

Q: What if your servers get hacked?

A: Attackers would get encrypted blobs that are mathematically impossible to decrypt without your encryption key (which we don't have).

Q: What if Clerk (our auth provider) gets hacked?

A: Attackers could derive encryption keys, but they'd also need our Redis data. Compromise requires TWO separate systems.

Q: Can government agencies force you to hand over my data?

A: They can demand our encrypted blobs, but we literally cannot decrypt them for them (or anyone). We don't have the keys.

Q: What if I paste my password into a tool?

A: DON'T DO THAT. While your data is encrypted, if someone compromises BOTH Clerk AND our database, they could theoretically decrypt it. Our privacy warnings explicitly say: "Don't paste passwords, API keys, or sensitive information."

Q: How do I delete my cloud history?

A: Settings → History & Privacy → Delete Cloud History. Instant and permanent.

What It Costs Us (Spoiler: Almost Nothing)

Transparency time: Here's exactly what cloud sync costs us per user:

Storage: ~$0.01/user/year API calls: ~$0.004/user/year Total: ~$0.014/user/year (yes, one penny!)

We use Upstash Redis, which has an incredibly generous free tier and scales efficiently.

This means we can offer free cloud sync to everyone without burning through VC money. Sustainable SaaS ftw!

Real User Feedback (Early Access)

We tested cloud sync with 50 beta users before launch. Here's what they said:

"I switched from my laptop to my phone mid-task and my history was just... there. Magic!" - Sarah K., Product Manager

"The fact that it's end-to-end encrypted makes me actually trust it with my work data." - Mike T., Security Engineer

"Finally! I've been asking for this feature since day one." - James L., Developer

"The privacy notice is refreshing. Most companies hide how their encryption works." - Lisa R., Privacy Advocate

Built for Developers, By Developers

As developers ourselves, we know you care about:

How things work (that's why we explained the encryption)
What data is stored (that's why we listed exactly what we can/can't see)
Open source (coming soon - encryption library will be open sourced!)

We're not some faceless corporation. We're developers who got tired of shitty tools and built something better.

What's Next: The Roadmap

Cloud history sync is just the beginning. Here's what's coming:

Phase 2 (Q1 2025)

📱 PWA support - Install as native app
🔍 Encrypted search - Search across cloud history (still encrypted!)
💾 Export backups - Download encrypted .json backup
⭐ Sync favorites - Star entries, access across devices

Phase 3 (Q2 2025)

👥 Team sharing - Share history with team (encrypted!)
📊 Usage analytics - See which tools you use most
🔄 Workflow sync - Save & sync custom workflows
🎯 Smart suggestions - "You often use X after Y"

Vote on features: cleantextlab.com/roadmap (coming soon)

Try It Today

Enable cloud sync in 30 seconds:

Sign in: cleantextlab.com
Settings → History & Privacy → Toggle ON
Done!

Want more storage and longer retention? Upgrade to Pro: cleantextlab.com/pricing

Thank You to Our Beta Testers

Huge shoutout to the 50 developers who tested cloud sync before launch:

Found bugs (we fixed them!)
Suggested UX improvements (we implemented them!)
Stress-tested encryption (it held up!)

You made this feature better. Thank you! 🙏

Join the Privacy-First Movement

We believe tools should respect your privacy by default, not as an afterthought.

Cloud sync is just one example of how we're building CleanTextLab:

✅ All tools run client-side (no server uploads)
✅ Zero tracking (we use privacy-friendly analytics)
✅ No ads (we'd rather you pay $5/mo than sell your data)
✅ Open about how things work (read our docs!)

If you believe in this vision, support us:

⭐ Star us on Product Hunt
🔗 Share with privacy-conscious friends
💰 Upgrade to Pro if you can afford it

Special Launch Offer 🎉

To celebrate cloud sync launch, we're offering:

50% off Pro for life for the next 100 signups!

Normal: $9/mo
Launch price: $5/mo forever
Use code: CLOUDSYNC50

Get it here: cleantextlab.com/pricing

Developer Corner: Open Source Incoming

We're planning to open source our encryption library so you can:

Audit the code yourself
Use it in your own projects
Contribute improvements
Verify we're not lying about encryption (check our source)

Stay updated: Follow the blog for release notes and security updates.

Final Thoughts

We built cloud sync the way we wish all cloud features worked:

Privacy by default (opt-in, not opt-out)
Transparent about how it works (this entire blog post!)
Affordable for everyone (free tier + cheap Pro)
Client-side encryption (we can't read your data)

If you care about privacy and convenience, give it a try. We think you'll love it.

Enable cloud sync: cleantextlab.com/settings

P.S. If you're a security researcher and want to audit our encryption implementation, email security@cleantextlab.com. We'll give you Pro for free in exchange for a responsible disclosure report.

P.P.S. No VC funding, no exit strategy, just building useful tools. Support indie developers! 💪

CleanTextLab Cloud Sync Architecture

Technical Appendix (For the Nerds)

Encryption Specifications

Algorithm: AES-256-GCM (Galois/Counter Mode)
Key Derivation: PBKDF2-SHA256, 100,000 iterations
IV: Random 96-bit nonce per entry
Key Source: Clerk user ID (deterministic across devices)
Storage Format: Base64(IV + EncryptedData)

Infrastructure

Storage: Upstash Redis (regional deployment)
API: Next.js 15 serverless functions
Auth: Clerk (production keys)
Encryption: Web Crypto API (native browser)

Data Retention

Free: 30 days TTL (auto-delete)
Pro: 90 days TTL (auto-delete)
Manual deletion: Instant and permanent

Compliance

✅ GDPR-compliant (data minimization, right to deletion)
✅ CCPA-compliant (California privacy)
✅ SOC 2 ready (working on certification)

Security Audits

Internal review: Complete ✅
Third-party audit: Scheduled Q1 2025
Bug bounty: Coming soon

Read the full technical docs (public summary): Cloud History Sync Docs