Draft, not legal advice. This page hasn’t been reviewed by a lawyer yet.
Nabora Privacy Policy
Nabora ("we," "us") runs naboralocal.com, a local-offers site for independent shops in Denver and the surrounding area. Nabora is a trade name of Zachary T. Miller, a sole proprietor in Colorado: Nabora (Zachary T. Miller, sole proprietor), Colorado. This policy applies to naboralocal.com, the shop portal at naboralocal.com/shop, and email we exchange with you about Nabora. It describes what we actually do today. It is not a promise of compliance with any particular law.
This page explains in plain English what information we collect, why, how long we keep it, who else handles it, and what you can ask us to do. We try to collect as little as we can.
The short version
- No tracking cookies, no ads. We measure visits with Cloudflare Web Analytics, which says it uses no cookies and reports totals only, plus our own anonymous daily view counts.
- We don't sell your information, and we don't share it for advertising.
- Customers never pay Nabora, and we never store card or bank details. After the free pilot, shops pay Nabora by invoice through Square, which handles the payment.
- Claiming a code doesn't identify you. We don't store your name, contact details, or IP address with a code. To stop abuse, we keep a scrambled (hashed) form of your connection's IP address, separately from the code, for 24 hours.
What we collect, and why
1. If you apply for the shop pilot
When you fill out the "Ask about the pilot" form (naboralocal.com/#business), we store:
- What you type in: business name, your name, email, phone (optional), city or area (optional), business category, and your message
- Technical details sent with the form: your IP address, your browser type (user agent), the time you submitted, and the link tag you arrived from, if any (for example,
flyerfrom a flyer's QR code) - Our own notes: whether the notification email about your application was sent (or the error, if not), and an internal status we use to track the application
Why: to review your application and reply to you about the pilot. We use the IP address and browser type only to spot spam and to limit repeated submissions from the same connection. The link tag tells us which flyer, post, or link brought you to us.
Where it goes: your application is stored in our database (Cloudflare D1) and emailed to the Nabora team through the Resend email service (sent from [email protected] to our support inbox, [email protected]). If we reply, we do it from that inbox.
2. If your shop is in the pilot
For each shop in the pilot, we store:
- Shop name, contact name, email, phone, category, and area
- When you agreed to the pilot terms, and which version you agreed to
- A scrambled version (a "hash") of your shop token. We never store the token itself.
- If we send you a one-time sign-in link: a hash of the link's code (never the code itself), when it was created, when it expires (7 days later), and when it was used
- A keyed, scrambled (hashed) version of your shop's 4-digit counter PIN, and when and by whom (you, Nabora, or automatically) it was last set. We never store the PIN itself, so it's shown only right after it's set.
- Whether your shop is a Founding Partner, and when your offer first went live
- Timestamps, such as when your shop's record was created or changed
- Your offer details: the offer and fine print you submit, and how much your deal saves a customer (its value, which sets your price per redeemed code). Nabora reviews them before they go live.
- Your shop profile: street address, and optionally hours, a phone number for customers, and a website or Instagram link. These are shown publicly on your deal on naboralocal.com (and in our public list of live deals) so customers know where to go. Only add a phone number you're happy to publish.
- Your code settings: monthly code limit (if any) and how many days codes stay valid
- Activity for your offer: how many times it was shown, codes claimed, redeemed, expired, and unused, which link tags they came from, and recent redemptions. You can see these in the shop portal.
- Billing records: how many codes your shop redeemed each month, the price that applied to each one when it was redeemed, and the amount due. After the free pilot (which runs through January 21, 2027), we send invoices through Square. Square handles your payment under its own privacy policy; Nabora never stores card or bank details.
How we deliver your shop token: when we set up your shop (or issue a new token), we send the token and sign-in instructions to the email address you gave us, or by text message if you've texted us. Treat that message like a password. We may keep a copy in our own mailbox or phone.
Why: to show your offer on the site, let you redeem codes, show you how your offer is doing, bill you after the pilot, and run the pilot. See the Pilot Terms.
Directions links: each deal has a Directions link that opens Google Maps in a new tab with the shop's address. Nabora doesn't load any map or Google code on its pages; if you tap the link, Google handles your visit under its own privacy policy.
Signing in to the shop portal: shops sign in at naboralocal.com/shop with their private shop token, or with a one-time sign-in link we text or email them. A sign-in link works once and expires after 7 days; making a new link cancels the old one. After you sign in, your browser keeps a session cookie for up to 30 days. The cookie is "HttpOnly," so scripts on the page can't read it. Your shop token is not saved in your browser.
Failed sign-ins: when a sign-in attempt fails (shop portal or admin), we store a hashed form of the IP address, the type of attempt, and the time. We use this only to slow down repeated guessing, and we delete it after 24 hours.
Keep your shop token private. It works like a password. Because we only keep a hash, we can't look it up for you; if you lose it or think someone else has it, contact us and we'll issue a new one.
3. If you claim a code as a customer
When you claim a deal, we create a one-time referral code and store:
- The code
- Which deal it's for (deal ID, business name, and offer text)
- Its status (issued or redeemed)
- When it was claimed, when it expires (14 to 90 days after it was claimed, depending on the offer), and when it was redeemed
- Which shop redeemed it, and how: at the counter (the cashier entered the shop's PIN on your phone) or in the shop portal
- If the shop voided the redemption (for example, because it was recorded by mistake): when, and the reason the shop gave
- The link tag you arrived from, if any. Some of our links and QR codes end in a tag such as
?src=flyer-shopnameor?src=nextdoor. The tag describes the link, not you.
We don't store your name, email, phone number, or IP address with a code.
Wrong counter PINs: when a wrong shop PIN is entered for a code at the counter, we record the code, the time, and a hashed form of the connection's IP address, so we can lock a code after 5 wrong tries and slow down guessing. The hash is made with a secret key. We delete these records after 24 hours.
Claim limits: each browser gets one code per deal, and each internet connection can claim a deal up to 3 times a day. To enforce the daily limit, we store a hashed form of your connection's IP address, the deal, and the time, in a separate table that isn't linked to your code. The hash is made with a secret key, so it can't simply be looked up. We delete these records after 24 hours.
Why: so each code works only once and expires on time, so the shop can redeem it and see how its offer is doing, and so we can see which links and flyers bring customers to local shops.
Checking a code: the "Check a code" box on the home page lets anyone who has a code see whether it's valid, unused, and unexpired, and which offer it's for. It doesn't redeem the code.
4. If you email or text us, or we contact your business
- Messages you send us. If you email [email protected], or use a "Text for support" link on the site, we receive your message and whatever contact details and content you include, and we keep it to answer you and keep a record of the conversation. Email is hosted by Google (Gmail). A text goes through your mobile carrier to the Nabora team's phone.
- Businesses we reach out to. We may email, message, or visit local businesses to tell them about the pilot. We use business contact details that are publicly listed (for example, on a shop's own website or social profile) or that the business gave us. We keep a short record (business name, contact, what we sent, any reply). If you don't want to hear from us, reply "no thanks" or email us, and we'll note it and stop.
- Social media. We have Nabora pages on Instagram, Facebook, Nextdoor and X. If you interact with them, that platform handles your information under its own policy; we see what the platform shows page owners. We don't connect social activity to codes.
5. Visit counts and analytics
- Cloudflare Web Analytics. Our host, Cloudflare, adds a small script to our pages that reports page visits, pages viewed, referring site, and general browser and country information. Cloudflare says it does not use cookies or local storage for this and does not fingerprint visitors. We see only totals.
- Our own anonymous counts. When the home page loads, it tells our code service to add one to a daily count of home page views and of how many times each live deal was shown, grouped by date, deal, and link tag. Nothing about you is sent or stored: no IP address, no cookie, and no identifier.
6. What's stored in your browser
- "My offers": your browser keeps a copy of the codes you claimed on this device in local storage, with each code's expiry date and the shop's address and hours. It stays on your device until you clear your browser's site data. Clearing it removes the list from this device but doesn't cancel the code on our side.
- Link tag: if you arrived through a tagged link, the tag is kept in this browser tab's session storage so it can be saved with a code you claim or a pilot application you send. It's cleared when you close the tab or browser.
- Offline page cache: the site installs a small service worker that caches one offline page so the site can show a friendly message when you have no connection. It stores no personal information.
- Shop portal session cookie (shops only): described above; up to 30 days.
- Nabora team marker (Nabora's own admins only): when a Nabora admin signs in to the admin pages, their browser gets a small cookie (
nabora_internal) so their own visits aren't counted. It contains no identifier, lasts up to 400 days, and is never set for customers or shops.
We don't use tracking or advertising cookies.
7. Logs and technical information
Like any website, when you visit naboralocal.com your browser sends technical information such as your IP address and browser type.
- Nabora's own code doesn't log visitors' IP addresses or browser details, other than where this policy says so (for example, the IP address saved with a pilot application, or the hashed IP used for claim limits). Short technical messages (for example, errors) may be visible to us briefly through Cloudflare's tools.
- Cloudflare, our host, handles these requests under its own policies to deliver and protect the site, and may keep its own logs.
Who handles information for us
| Provider | What they do for Nabora |
|---|---|
| Cloudflare | Hosts the site, handles web requests, stores our database (Cloudflare D1, including any backups it keeps), provides cookie-free Web Analytics, and may hide email addresses on our pages from automated scrapers. |
| Resend | Delivers pilot application notification emails to the Nabora team and keeps its own records of the emails it sends. |
| Square | After the pilot, sends invoices to shops and processes their payments. Only shops' billing details are shared (shop name, contact email, and the amount due). Customers' information is never sent. |
| Google (Gmail, Google Maps) | Hosts our support inbox, [email protected], where application emails and messages you send us are received. Google Maps only sees your visit if you tap a Directions link. |
| Instagram, Facebook, Nextdoor, X | Platforms where Nabora has pages. They handle their own users' information under their own policies. |
These providers have their own privacy policies and may keep information as those policies say. We may also share information if the law requires it, or to protect Nabora, our users, or others from fraud or abuse. If Nabora is ever sold or transferred, shop records may transfer with it, and we'd tell shops by email.
What we don't do
- We don't use tracking or advertising cookies.
- We don't sell personal information, or share it for advertising.
- We never store card or bank details. Customers never pay through the site.
- We don't show third-party ads.
- We don't try to identify customers who claim codes.
How long we keep information
- Pilot applications from shops that don't join: up to 12 months after our last contact with you, then deleted. This includes the copies of application emails, and any replies in the same email thread, in our support inbox.
- Shop records (for shops that join, including their application): while the shop is active, plus 12 months.
- Codes and redemption records: up to 24 months. They contain no customer identity.
- Billing records and invoices for shops: as long as tax and accounting rules require.
- Failed sign-in, wrong-PIN, and claim-limit records: 24 hours (hashed IPs), then deleted automatically.
- Anonymous daily view counts: as long as they're useful. They contain no personal information.
- Other emails and texts you send us, and our outreach records: up to 24 months after our last contact, unless we need them longer to resolve a dispute or meet a legal or tax duty. The exception: messages that are part of a pilot application follow the pilot-application rule above (12 months if the shop doesn't join, or the shop-record rule if it does), not this 24-month rule.
- Shop portal session cookie: up to 30 days. Nabora team marker cookie (admins only): up to 400 days. "My offers" in your browser: until you clear it.
- Records kept by Cloudflare, Resend, Google, Square and social platforms follow their own policies. Deleted data may remain in backups held by Cloudflare for a limited time under its policies.
Your choices: access, correction, and deletion
You can ask us to tell you what information we have about you, correct it, or delete it. Email [email protected], tell us what you're asking for and how we can find your information (for example, the email you applied with, or your shop name). Customers: we don't store who claimed a code, so the code itself is the only way we can find a record. We'll reply as soon as we can, and within 30 days. We may need to confirm it's really you before we act, and we may keep information we're required to keep (for example, billing records).
You can opt out of Nabora outreach emails or messages by replying "no thanks" or emailing us.
Age
You must be 18 or older to claim a code. Nabora isn't meant for children, and we don't knowingly collect personal information from anyone under 18. If you think a child has sent us information, contact us and we'll delete it.
Security
We take reasonable steps to protect the information we keep. For example, we store only a hash of each shop token, sign-in link and counter PIN; we store only keyed hashes of IP addresses for rate limits and delete them after 24 hours; the shop portal cookie can't be read by page scripts; and we rate-limit repeated failed sign-ins. No website is perfectly secure, so we can't promise that information will never be accessed without permission. If we learn that shop information we hold was accessed without permission in a way that affects you, we'll email the shops affected.
Changes to this policy
If we change this policy, we'll post the new version here and update the date at the top. For important changes, we'll also post a note on the home page and email shops in the pilot. Continuing to use the site after a change means you accept the updated policy.
Contact
Nabora (Zachary T. Miller, sole proprietor), Colorado
Email: [email protected]