1. Scope and sender roles
This Policy applies to email, web and mobile push, in-product notices, and any future SMS or messaging sent through OTT Platform. It is a development draft pending counsel review, sender-domain approval, consent design, and production provider testing.
The platform operator sends shared account, security, payment-facilitation, policy, and service messages. A channel owner may separately send programming, membership, offer, sponsor, event, and support messages and is responsible as an independent sender for its audience, content, lawful basis, consent, and suppression lists.
2. Transactional and relationship messages
Necessary messages may include identity verification, login and MFA, invitations, receipts, subscription and cancellation confirmations, refund or dispute status, security alerts, rights or policy notices, service changes, incident information, and requested support.
A user generally cannot opt out of messages necessary to provide, secure, or administer an active account or transaction, but the sender must not disguise marketing as transactional content. Closing an account may be required to stop account-essential messages.
3. Marketing email
- Use accurate From, To, Reply-To, routing, sender, domain, and subject information.
- Clearly identify commercial messages as advertising where required and do not use deceptive subject lines or preview text.
- Include the responsible sender's valid physical postal address and a clear unsubscribe method.
- Keep the opt-out method available for the required period and honor requests promptly, no later than 10 business days where CAN-SPAM applies.
- Do not charge, require login, demand information beyond what is reasonably necessary, or force more than a simple reply or single-page process to unsubscribe.
- Maintain suppression lists and do not sell or transfer an opted-out address except to a provider helping honor the request.
4. Consent and list integrity
Do not use purchased, scraped, guessed, shared, or unrelated lists. Channel owners must document how each recipient joined, what they were told, which sender and message types they accepted, and when consent was obtained where consent is required.
Consent must be specific, informed, affirmative, unbundled where required, and as easy to withdraw as to give. An account, purchase, event registration, or organization membership does not automatically authorize every form of marketing.
5. Push notifications
Push requires device or browser permission and should be preceded by a clear explanation of its value and categories. Do not repeatedly prompt after refusal, obscure the system choice, or condition unrelated core service on optional push permission.
Users should be able to manage reminders, live-event alerts, comments, marketing, and other categories separately where practicable. The platform must remove invalid or revoked subscriptions and stop optional delivery after preference withdrawal. OneSignal or another provider processes device subscription identifiers under approved terms.
6. SMS and automated calls
Marketing SMS, automated calls, and prerecorded or artificial-voice communications are outside the intended launch scope. They must not be enabled until counsel approves TCPA and state-law consent language, sender identification, one-to-one consent where applicable, quiet hours, frequency disclosures, STOP/HELP handling, number reassignment controls, vendor contracts, and consent evidence.
Consent to SMS or calls may not be a condition of purchasing an unrelated service where prohibited. Transactional texting also requires purpose-specific review.
7. Preferences and frequency
Honor account, channel, topic, and device preferences across delivery systems. A user who unsubscribes from one channel's marketing may still receive another channel's messages only if that other sender has an independent lawful basis and the user was clearly informed.
Avoid excessive frequency, misleading urgency, repetitive reminders, and notifications at unreasonable local hours. Security and urgent operational messages should be narrowly limited to their stated purpose.
8. Communication content and safety
- Do not send unlawful, harassing, hateful, exploitative, fraudulent, infringing, or malicious content.
- Clearly disclose sponsors, affiliate relationships, price, renewal, eligibility, and material offer restrictions.
- Do not place sensitive viewing titles or private community content in a lock-screen notification or subject line unless the user knowingly selected that level of detail.
- Do not expose recipient lists, authentication links, invitation tokens, signed media URLs, or credentials.
- Use authenticated sending domains and maintain SPF, DKIM, DMARC, bounce, complaint, and suppression controls.
9. Providers, delivery, and records
Resend, OneSignal, carriers, inbox providers, browsers, device platforms, and app stores may delay, filter, modify, or block delivery. We do not guarantee receipt, timing, placement, or engagement.
The responsible sender must retain appropriate consent, notice version, source, preference, delivery, bounce, complaint, and unsubscribe evidence without retaining message content or personal information longer than necessary. Provider use does not transfer the sender's legal responsibility.
10. Enforcement and contact
We may throttle, pause, suppress, or disable a sender, campaign, template, integration, or channel for complaints, bounces, provider rules, security, consent failures, legal concerns, or policy violations. The channel owner remains responsible for honoring requests received outside the platform.
Communication questions or abuse reports may be sent to dave@badburrito.com. Marketing recipients should also use the unsubscribe or preference control in the message.