Privacy Policy
zip4lookup is operated by InfoTilt, Inc.. This policy describes what we collect, why, how long we keep it, and who else sees it. We have written it against what our systems actually do rather than against a template, so the retention periods below are the real ones.
1. Who we are
InfoTilt, Inc. is the controller of the information described here. Contact us at legal@zip4lookup.com for any privacy question, request, or complaint.
2. What we collect
Addresses you submit
When you use the lookup tool, the API, a bulk upload, or the EDDM planner, you send us postal addresses. We treat these as the operating data of the service. We use them to return a result, and we cache the result. We do not use them to build profiles of the people who live at those addresses, we do not append them to any marketing database, and we do not sell them.
An address is often personal information about someone who is not you. If you are submitting a list of other people's addresses, you are responsible for having the right to do so — see the Terms.
Account information
If you create an account: your email address, a password (stored only as a one-way hash, never in readable form), and optionally a company name. API keys are stored only as a SHA-256 hash — we cannot recover a key for you, which is why the plaintext is shown exactly once at creation.
If you sign in with Google: Google tells us your name, email address and a Google account number, and confirms the address is yours. We never see your Google password. The button is loaded from Google on the sign-in page, and Google's own privacy policy covers what Google collects.
Usage and technical information
- Usage counters. Per-day totals of how many lookups each account and key made, by endpoint. Counts only — no addresses.
- Rate-limiting records. IP addresses with timestamps, used solely to enforce request limits. Purged after 2 hours.
- Server logs. Standard web server logs including IP address, timestamp, URL, and user agent. Retained about 30 days.
- Security events. A record of significant account events with the originating IP. Retained 90 days.
Payment information
We do not receive, process, or store card numbers. Payment is handled entirely by Stripe. We store a Stripe customer identifier and a subscription identifier so we know which plan you are on.
What we do not collect
We do not use tracking pixels, session recording, or cross-site advertising trackers of our own. We do not ask for your date of birth, government identifiers, or financial account details. We have no mobile application collecting device data.
3. How long we keep things
Retention is enforced automatically by scheduled jobs, not by anyone remembering to run a cleanup.
| What | How long | Why |
|---|---|---|
| Cached lookup results | 30 days | So repeat lookups of the same address are instant and are not billed to anyone. |
| Uploaded files and their results | 7 days | Long enough to download your results, short enough that we are not holding your customer lists. |
| Rate-limiting records (IP) | 2 hours | Only useful within the limiting window. |
| Server logs | ~30 days | Debugging and abuse investigation. |
| Security event records | 90 days | Investigating account compromise and billing disputes. |
| Flood zone results | 365 days | Cached by coordinate. FEMA revises maps on a multi-year cycle. |
| EDDM plans (no account) | 30 days | Enough to come back to a plan you were working on. |
| Usage counters | While your account exists | Billing history and dispute resolution. Counts only, no addresses. |
| Account records | Until you delete, then 30 days | A grace period against accidental deletion. Billing records may be kept longer where tax law requires. |
One honest note about the lookup cache: it stores the standardized address and its result, keyed by a hash of what you submitted. It is a cache of postal facts, not a record of who asked. It is not linked to your account or to any individual, and any account benefits from a result any other account previously caused to be cached.
4. Who else receives information
We use a small number of processors. Each receives only what it needs.
| Who | What they receive | Why |
|---|---|---|
| Geocodio (address data provider) | The address being looked up | To return the ZIP+4 and delivery point data. This is the core function of the service. |
| Stripe | Email, payment details you enter on their form | Payment processing. We never see the card number. |
| Bluehost | Everything, as our hosting provider | Running the servers and databases. |
| FEMA | Coordinates only, if you request flood enrichment | Flood zone determination from the public National Flood Hazard Layer. |
| Google (AdSense) | Standard advertising signals from ad-supported pages | Advertising on the free tools and reference pages. |
| Google (Fonts) | Your IP address, when loading webfonts | Typography. We intend to self-host these, which will remove this transfer. |
We do not sell personal information, and we do not share it for cross-context behavioural advertising as those terms are defined under California law. We may disclose information if legally compelled, or to protect against fraud or abuse. If we are ever acquired, information may transfer as part of that transaction, and this policy would continue to apply until you were given notice of any change.
5. Cookies and advertising
We set one cookie of our own: z4sess, which keeps you signed in. It is marked HttpOnly, Secure, and SameSite, expires when you close your browser, and contains no personal information — only a session identifier. There is no way to use an account without it.
Ad-supported pages load Google AdSense, which sets its own cookies and may use them to personalise advertising. You can control this at Google My Ad Center and opt out of personalised advertising from participating vendors at optout.aboutads.info. Ads do not appear on the dashboard, the API, or any authenticated page.
We use Google Analytics to understand how the site is used. It sets its own cookies and receives the pages you view, approximate location and device type — not the addresses you look up or upload. You can opt out with Google's browser add-on at tools.google.com/dlpage/gaoptout.
We honour Global Privacy Control signals as an opt-out of sale or sharing where applicable law gives them that effect.
6. Your rights
Wherever you live, you may ask us to show you what we hold about you, correct it, delete it, or send you a copy. Write to legal@zip4lookup.com. We respond within 30 days and we do not charge for it. We will not treat you differently for asking.
California
Residents of California have the rights to know, delete, correct, and opt out of sale or sharing, and to limit use of sensitive personal information. We do not sell or share personal information, and we do not collect sensitive personal information as that term is defined. You may use an authorised agent; we will ask for proof of authorisation.
Other US states
Comparable rights apply under the privacy laws of Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana, and other states with comprehensive privacy statutes. We extend the same process to everyone rather than gating rights by residency, because operating one process is both simpler and fairer.
Europe and the United Kingdom
If the GDPR or UK GDPR applies to you, our lawful bases are: performance of a contract, for account and paid service data; legitimate interests, for security, abuse prevention, and service improvement; and consent, where we ask for it. You have rights of access, rectification, erasure, restriction, portability, and objection, and you may complain to your supervisory authority. Our servers are in the United States, so using the service involves transferring data there.
7. Addresses belonging to other people
Most of what passes through this service is other people's addresses. That shapes how we handle it.
- We act as a processor for the lists you upload. We use them to perform the task you asked for, and for nothing else.
- We do not resell, license, or share your uploaded lists.
- We do not use your lists to train models or to build any derived product.
- If a person contacts us about an address that reached us through your list, we will refer them to you, because you hold the relationship and the context. We will help you respond.
- If you need a data processing agreement for your own compliance obligations, write to us.
8. Security
- Everything is served over HTTPS with HSTS.
- Passwords are stored as one-way hashes. API keys likewise — we cannot read your key, only verify it.
- Session cookies are HttpOnly, Secure, and SameSite, and the session is regenerated on sign-in.
- Uploaded files are stored outside the web root and are not reachable by URL.
- All database access uses parameterised queries.
- Mutating dashboard requests require a CSRF token.
- Sign-in and sign-up have automated bot checks and attempt limits (these may include Cloudflare Turnstile).
No system is perfectly secure. If you find a vulnerability, tell us at legal@zip4lookup.com and we will not pursue legal action against good-faith research that avoids privacy violations, service disruption, and data destruction.
9. Children
This is a business tool and it is not directed to children. We do not knowingly collect personal information from anyone under 13. If you believe a child has provided us information, write to us and we will delete it.
10. Changes
We will post any change here with a new "last updated" date. If a change is material — a new category of collection, a new purpose, a materially longer retention period — we will email account holders at least 14 days before it takes effect, so that you can close your account first if you disagree.
Questions
Write to legal@zip4lookup.com. We answer privacy requests within 30 days.