Privacy policy.
Version 2026-11-09.1 · Effective .
The Contact form is the temporary support and privacy-request channel. These pages are general information, not legal advice.
Who is responsible
Big Noggin Marketing LLC operates Deals 4 Hoosiers. Business correspondence: Big Noggin Marketing LLC, 8500 E 116th Street, P.O. Box 268, Fishers, IN 46038. This is a mailing address, not a public storefront or customer-visit location. The existing Contact form is the temporary channel for support and privacy requests. Messages are saved for administrator review, not sent by email; no response time is promised. Do not send passwords or full payment-card details.
Information we handle
Clerk, our authentication provider, handles account sign-in and associated account information. The application uses an account identifier to associate owners and customers with their records. Business records can include the business name, description, category, city, address or service area, phone number, website, hours, social links, uploaded photos, videos and other business content, organization and location ownership, coupons, and membership information. Customer records can include saved coupons, redemption tickets, and preferences. Contact inquiries include the submitted name, email address, subject, message, submission time, and review status. Only information relevant to the features you use is collected through those features.
Saved coupons and tickets
If you sign in, your account identifier is stored with the coupons you save and any redemption tickets you create, so they persist across visits. Owners see only aggregate counts and the coupon confirmed, not your identity.
Optional Email My Coupon
When available, signed-in consumers can request an email link to a usable coupon they have saved or claimed. We obtain the consumer’s verified primary email address from Clerk and send only to that address through the configured email provider. The email links to My Deals, where the consumer must sign in with the account that saved or claimed the coupon; it does not contain a private redemption code. Requesting the email does not redeem the coupon or subscribe the consumer to marketing emails. Delivery may remain disabled until email configuration is complete.
Coupon-email delivery records
To limit abuse and duplicate sends, the application stores an account identifier, coupon identifier, attempt identifier, a hash derived from the recipient email address, an attempt time, and a sending, provider-accepted, or unconfirmed status. These are account-linked records, not anonymous data. The coupon-email tracking record does not store the full email address, message body, private redemption code, or provider message identifier. A later permitted request can replace the prior attempt record for that account and coupon. There is no fixed automatic deletion deadline for these records; applicable manual retention review and lawful retention needs still apply. The email provider receives the recipient address and message needed for delivery and may retain its own records. Provider acceptance does not confirm inbox delivery. Unconfirmed delivery does not remove saved coupons or tickets, and no automatic retry is promised.
Cookies and engagement records
Sign-in uses authentication cookies. Our first-party engagement cookie can last up to 180 days and recognizes a browser so interactions can be deduplicated. The app stores a hashed browsing identifier with interaction type, business or coupon reference, and time. Business owners receive aggregate totals, not these browsing identifiers. Engagement cookies are not used for advertising. Security controls also use request information, including network addresses, to limit abuse.
Weekly email
If you subscribe, we store your email address and chosen cities and categories. We use double opt-in: you are subscribed only after clicking the confirmation link, and each email has an unsubscribe link.
Optional owner reminders
Owners may separately opt into coupon-expiration reminder emails in their portal. We store the consent and delivery records needed to manage reminders and avoid duplicate delivery. Newsletter consent and owner-reminder consent are separate. Disable reminders in the portal to stop future reminders; sending depends on email delivery being configured.
Payments and membership history
Stripe processes membership checkout and recurring billing. Card details are entered into Stripe’s payment forms; the app does not receive or store full card numbers. The application stores membership status, plan, paid-through dates, Stripe customer and subscription references, and payment-related records received from Stripe. These records can include Checkout, invoice, subscription, amount, currency, status, date, and billing-contact information. Checkout metadata records the accepted terms version, acceptance time, and account identifier. Webhook-processing records associate Stripe events with membership outcomes and help prevent duplicate processing. Stripe also processes payment and fraud-prevention information under its own privacy policy. Cancelling renewal does not erase billing or membership history.
Founder pricing records
Business identifiers, ownership associations, Founder assignment records, and membership and payment references are retained as needed to document membership history and assess Founder pricing eligibility. The grandfathered $300 per-location annual rate requires continuous membership and is forfeited once cancellation takes effect and membership expires, or the subscription actually terminates after unsuccessful payment recovery. Reversing scheduled cancellation before period-end preserves the rate if continuous renewal is successfully restored. Cancelling renewal does not erase historical records; retaining those records does not restore the grandfathered rate for a returning business. Access continues through the already-paid membership period. A request to delete a business or account requires separate review of applicable legal, payment, audit, and record-retention needs. The application does not automatically restore deleted Founder records or recreate eligibility after deletion.
Owner coupon reminders and retention
If you opt in to coupon-expiry reminders, we save your verified primary account email with your preference and use a recipient snapshot for delivery attempts. On the next reminder-worker run after 30 days have elapsed since an attempt reaches a final status (sent, cancelled, exhausted, or uncertain with no further automatic retries), we remove the full snapshot, including the email, owner account identifier, business name, and coupon title, and clear the email-provider message reference. Unfinished attempts keep their snapshots until retries are safely finished. We retain the coupon/date key, idempotency key, status, attempt counts, timestamps, and fixed failure codes while the coupon exists to prevent duplicate reminders across restarts or preference changes. Redacted entries no longer appear in owner reminder history. Turning reminders off removes the email from your active reminder preference but does not delete these duplicate-prevention records. This policy covers our reminder database; it does not delete mail already accepted by an email provider or delivered to an inbox. The site owner should review this policy and confirm provider retention practices before launch.
How it is used
Information is used to operate the directory, display business listings, and review contact messages. The contact form does not send email.
Public information
Business details, photos, and coupons that owners publish are visible to everyone.
Optional interviews and publication permissions
Meet the Owner interviews are optional. Recording and distribution require appropriate separate permissions; membership purchase is not consent. Authorized interviews may become publicly accessible on the separately approved Deals 4 Hoosiers website, YouTube or Facebook channels. YouTube and Facebook may process published recordings under their own privacy practices. Participants may use the Contact form to request withdrawal of future use, subject to appropriate identity or authority verification. Requests are reviewed manually. We cannot guarantee removal from independently controlled third-party copies. Necessary records and backup copies may remain subject to the retention limitations described in this policy.
Service providers and disclosure
Clerk handles authentication, Stripe handles payments, and Replit provides application hosting, database, and file-storage services. A configured email-delivery provider processes recipient information needed to deliver opted-in emails. Providers receive information needed for those services. Information may also be disclosed when legally required or needed to protect the service and its users.
Access, correction, and deletion requests
You can manage saved deals, edit business information and coupons, and remove individual coupons through the available site controls. Newsletter unsubscribe links and owner-reminder preferences, where available, are separate controls. To request access to, correction of, or deletion of other information, use the Contact form and identify the account or business concerned. Do not send passwords, authentication codes, full payment-card details, or unnecessary identity documents. Requests require administrator review and appropriate identity or ownership verification before information is disclosed or changed. Submitting the form does not verify identity, provide a data export, or perform deletion. There is no self-service whole-account deletion tool. Cancelling renewal does not delete account or business records, and submitting a deletion request does not itself cancel renewal.
Privacy requests through the Contact form
The Contact form is the temporary support and privacy-request channel for Big Noggin Marketing LLC. It saves the information you submit in the application database for authenticated administrator review. Under the manual process, administrators review each request and verify the requester’s identity and, where relevant, authority over the account or business before disclosing or modifying private records. Access, correction, and deletion requests are fulfilled through authorized manual handling where applicable and feasible, subject to applicable law and legitimate record-retention needs. The form itself only records the inquiry and allows administrators to update its review status; it does not verify identity, send an email, automatically notify you of progress, export data, or delete records. Saving a message or changing its review status is not confirmation that the requested privacy action has been completed. This policy does not promise automatic fulfillment, immediate deletion, or a specific response deadline, and it does not limit deadlines or rights required by applicable law.
Retention and legally required records
Under the manual retention process, only records reasonably necessary for legal obligations, tax and payment records, security, disputes, membership history, and established Founder pricing rights are retained. Administrators assess those needs when reviewing a request, including what information can be corrected or deleted and what must remain. Some records may remain after cancellation or account closure for those purposes. The application does not automatically perform this assessment or apply a single deletion schedule to all records. Removing information from the public directory is not the same as erasing it from the database or from service-provider systems. This policy does not establish a fixed retention period or promise immediate erasure.
Backups and recovery copies
Third-party service providers may retain their own records and database recovery copies under their retention processes and applicable legal obligations. Separately configured backup exports, if created, may also contain application records. This policy does not state that automatic production Backblaze backups are operating or that uploaded images are included in a database-only backup. Removing a record from the live application does not necessarily remove it immediately from third-party systems, recovery copies, or backup archives. Where a backup has retention protection, individual records may not be removable during that protection period. Requests affecting those copies require review of the provider’s processes, applicable retention restrictions, and legal obligations. A restore does not automatically reapply an earlier deletion request; restored records require administrator review. This policy does not promise immediate deletion from every copy.