Privacy policy

What we collect

• Account: your email address. We do not store passwords. We use passwordless sign-in: when you sign up or log in, we email you a one-time sign-in link that expires after 15 minutes and can be used only once.
• Sign-in tokens (authentication): to make that work, we store a cryptographic hash (SHA-256) of each sign-in token we issue, plus when it was issued, when it expires, and whether it has been used. The token itself is never stored: only its hash: and a used or expired token cannot be reused. Expired tokens are deleted automatically.
• Sessions: when you're signed in, your browser holds a single signed session cookie (Secure, HttpOnly, SameSite). It lasts until you close your browser or sign out; it identifies your account to our server and nothing else. If you start the onboarding questionnaire but don't finish, your answers are kept only in that same signed browser cookie (for up to 30 days) so you can pick up where you left off. They are never sent to our database. No other cookies.
• Saved searches: when you save a search, we store its criteria: name, maximum rent, minimum bedrooms, boroughs, household size, income range, and alert frequency: so we can match new listings against it and send you alerts. Deleting a search deletes its criteria; deleting your account deletes all of them.
• Matching: household size and income range, which you give us so we can compare your profile against each listing's published income limits.
• Stale-listing reports: if you report a listing as stale or incorrect, we store the listing reference, your note, and when you submitted it, so we can investigate and fix our data.
• IP addresses (rate limiting): we log the IP address of sign-in attempts and a few other sensitive actions, solely to enforce rate limits (for example, 3 sign-in emails per 15 minutes per address). These logs are not used for tracking and are not linked to your account beyond abuse prevention.
• Bot-check data: our sign-up and sign-in forms use Cloudflare Turnstile, an invisible check that tells humans apart from bots. When you submit one of those forms, Cloudflare briefly processes basic interaction data (such as your IP address and browser signals) to make that call. We do this to stop automated abuse of our email sign-up, and we do not use it for tracking.
• Usage measurement: we count page visits, questionnaire answers, and clicks on links in our own alert emails, on our own servers. No third-party trackers, no advertising pixels, no cross-site tracking.

Legal basis

We process your personal data on these bases: contract (providing the alert service you signed up for), consent (optional features, which you can withdraw at any time), and legitimate interest (rate limiting and abuse prevention, and keeping delivery records to prove we sent only what you asked for). Where we rely on consent, withdrawing it stops the processing but does not affect what was already done.

What we never do

• We never sell your data, including your income information, to anyone.
• We never see or store your card details. Premium subscriptions are processed by our payments provider (Stripe); card data stays with them, never with us.
• Email is transactional only: account emails and the alerts you asked for. No marketing email, ever.
• No advertising trackers. We don't run ads and don't share data with ad networks.

Alerts and unsubscribing

Every alert email includes a one-click unsubscribe link that works without logging in.

Email records we keep

To document your consent for the emails we send, we record when you created your account, which version of these terms you accepted, when you created each saved search, and when you unsubscribed (if you do). We also keep standard delivery records (what was sent, when) so we can prove a send happened or didn't. If an address hard-bounces or generates a spam complaint, we stop sending to it and keep a short suppression record (the address and the reason) so we don't email it again. We send only transactional emails: never marketing. Delivery is handled by our email delivery provider, whose privacy policy governs their handling of delivery data.

Deletion

You can delete your account and your data anytime from your Account page.

Retention

We keep your data only as long as your account exists.

Security safeguards

• No passwords to steal: because we don't store passwords, a database breach cannot expose anyone's password, and our accounts can't be attacked by password reuse (credential stuffing).
• Token hygiene: sign-in tokens are hashed (SHA-256), single-use, expire after 15 minutes, and expired tokens are purged automatically.
• Session hygiene: session cookies are signed, Secure, HttpOnly, and SameSite; they expire when you close your browser, and sign-in actions rotate anti-forgery tokens.
• Server hygiene: our database lives on a hardened server (firewall, automatic security updates), backups are kept off-server, and only the owner has server access. We keep no advertising trackers and share data with no ad networks.

Processors we use

• Email delivery: sign-in links and alert emails are sent through our email delivery provider.
• Hosting: our application and database run on servers managed by our hosting provider, with backups stored off-server.
• DNS: our domain's DNS is managed by our DNS provider.
• Payments: Premium subscriptions are processed by Stripe. Link (Stripe) is the seller of record: it calculates, collects, files, and remits sales tax by customer location. We never see or store your card details; receipts come from Link.

Cookies

We use a single session cookie to keep you logged in. Nothing else.

Children's privacy

ReRentalAlert is not directed at children under 13, and we do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact [email protected] and we will delete it.

Where your data lives

Our servers are in the United States, and backups are stored off-server. Our email delivery and DNS providers may process data in the US as described in their own privacy policies.

Changes to this policy

If we make material changes to this policy, we will post the updated version here with a new effective date and, where appropriate, notify you by email before the changes take effect.