Privacy-first by design: why contact state stays in Resend

We're building a warmup engine that's useful to serious sending teams, and that starts with a privacy posture you don't have to think about.

What we avoid by default

• No contact exports
• No inbox scraping
• No unnecessary retention

Where warmup state lives

Contact-level warmup state lives in Resend. Rewarmly focuses on configuration, pacing logic, and high-level progress so you can stay in control without creating another place for sensitive data to accumulate.

Why this matters

If your warmup tool depends on storing more than it needs, you end up paying a privacy and security tax forever. We'd rather build the constraints in now.