Communications Policy

1. Overview

This Communications Policy explains how Dudes That Code uses email, SMS, push notifications, and other communication channels to interact with you. We are committed to transparent, compliant, and respectful communication practices in accordance with applicable laws and the policies of our service providers, including SendGrid, Twilio, Firebase Cloud Messaging (FCM), and Stripe.

2. Types of Communications

2.1 Transactional Communications

These are essential messages related to your use of our services and cannot be opted out of:

• Account creation and verification emails
• Password reset and security notifications
• Two-factor authentication (2FA) codes
• Payment confirmations and invoices (via Stripe and SendGrid)
• Receipt of payments and payout confirmations
• Project status updates and milestone notifications
• Support ticket responses and updates
• Legal notices and policy updates
• Service disruption or maintenance alerts
• Security breach notifications

2.2 Operational Communications

Messages related to platform operations and your projects:

• New project assignments and updates
• Team collaboration requests and invitations
• Pod membership invitations and updates
• Document and file sharing alerts
• Payment reminders and due date notifications
• Equity and revenue distribution updates
• Contract and agreement notifications
• Tax document availability (1099 forms)

2.3 Marketing Communications (Optional)

Promotional messages you can opt in or out of at any time:

• New features and platform updates
• Educational content and best practices
• Special offers and promotions
• Newsletter and blog updates
• Event invitations and webinars
• Survey and feedback requests

3. Email Communications (SendGrid)

3.1 Email Service Provider

We use SendGrid (a Twilio service) to deliver all email communications. SendGrid provides enterprise-grade email delivery with high deliverability rates and security features.

3.2 Email Delivery Standards

• All emails are sent from verified domains with SPF, DKIM, and DMARC authentication
• Marketing emails include one-click unsubscribe options (CAN-SPAM compliant)
• We honor unsubscribe requests within 10 business days
• Physical mailing address included in all marketing emails
• We never share your email address with third parties for their marketing purposes
• Email delivery is monitored for bounce rates and spam complaints

3.3 Email Types & Frequency

• Transactional: Sent as needed based on account activity (cannot opt out)
• Operational: Based on project activity and notification settings (can customize frequency)
• Marketing: Maximum 2 emails per week if opted in (can unsubscribe anytime)
• Digest Emails: Daily or weekly summaries of platform activity (configurable)

3.4 Email Content Security

• We never request passwords, credit card numbers, or SSN via email
• All links in emails are tracked for security (detecting phishing attempts)
• Suspicious emails should be reported to admin@dudesthatcode.com

4. SMS/Text Message Communications (Twilio)

4.1 SMS Service Provider

Our SMS communications are powered by Twilio, a trusted communications platform. By opting in to SMS notifications, you agree to receive text messages in accordance with Twilio's Acceptable Use Policy and Messaging Policy.

Note: SMS notifications are currently planned for future implementation. This section will apply when the feature is activated.

4.2 Consent & Opt-In (TCPA Compliance)

• SMS notifications are opt-in only - we will never send texts without explicit prior consent
• You can opt in by providing your phone number and checking the SMS notification preference in settings
• Consent is not required to use our platform services
• You can opt out at any time by texting STOP to any message from us
• By opting in, you consent to receive automated SMS messages
• Message frequency depends on your activity and notification settings

4.3 Message Types & Frequency

If you opt in to SMS, you may receive:

• Critical Security Alerts: Two-factor authentication codes, password changes, unusual login activity
• Urgent Project Updates: Critical milestones, deadline reminders, client requests
• Payment Notifications: Payment received, payout processed, invoice due
• Team Communications: Urgent messages from team members or clients
• Estimated Frequency: 1-10 messages per month (varies by activity level)

4.4 SMS Commands

• STOP: Opt out of all SMS messages (you can also opt out in account settings)
• HELP: Get information about SMS notifications and support contact
• START: Re-subscribe to messages after previously opting out

After texting STOP, you will receive one final confirmation message, then no further messages unless you opt back in.

4.5 SMS Costs & Rates

• Message and data rates may apply depending on your mobile carrier and plan
• We do not charge for sending or receiving SMS messages
• Your carrier may charge standard messaging rates
• Contact your carrier for details on your specific plan
• Text message delivery may be delayed or fail due to carrier or network issues

4.6 Supported Carriers

Our SMS service supports major U.S. and international carriers including:

• AT&T, Verizon, T-Mobile, Sprint
• U.S. Cellular, Cricket, MetroPCS, Boost Mobile
• Major international carriers (varies by region)

If you experience delivery issues, please contact support@dudesthatcode.com.

5. Push Notifications (Firebase Cloud Messaging)

5.1 Browser & In-App Notifications

We use Firebase Cloud Messaging (FCM) to deliver real-time notifications:

• Browser Push: Notifications delivered to your browser even when not on the site
• In-Platform: Notifications within the platform interface
• Notification Center: Central hub for all notifications with filtering and search

5.2 Notification Types

• Project updates and milestone completions
• New messages and team communications
• Support ticket responses
• Payment and payout confirmations
• Security alerts and account changes
• Collaboration requests and invitations

5.3 Managing Push Notifications

• Account Settings: Customize which notifications you receive in your profile
• Browser Settings: Control push notification permissions in your browser
• Quiet Hours: Set times when notifications are silenced
• Notification Frequency: Choose immediate, hourly, daily, or weekly digest
• Category Controls: Enable/disable by category (projects, billing, system, pods)

6. Payment-Related Communications (Stripe)

6.1 Stripe Communications

Payment processing is handled by Stripe. You may receive communications from both Dudes That Code and Stripe regarding:

• Payment Confirmations: Instant receipts for successful payments
• Payment Failures: Notifications of failed transactions with resolution steps
• Invoices: Automated invoice delivery via email (PDF attached)
• Refunds: Confirmation of processed refunds
• Disputes: Chargeback and dispute notifications
• Payouts: Contractor payout confirmations and deposit notifications
• Tax Documentation: 1099 forms and tax reports (for contractors earning $600+)
• Identity Verification: Requests for additional verification (KYC compliance)

6.2 Stripe Direct Communications

Stripe may contact you directly regarding:

• Payment method updates and expiration notices
• Security alerts and fraud prevention
• Compliance and verification requirements
• Stripe account management (if you have a Stripe Connect account)

Stripe's communications are governed by their policies. View at stripe.com/privacy

7. Managing Your Communication Preferences

7.1 Preference Controls

You can control your communication preferences through:

• Account Settings: Manage all email, SMS, and push notification preferences
• Notification Center: Configure real-time notification settings
• Unsubscribe Links: One-click unsubscribe in any marketing email footer
• SMS Commands: Text STOP to opt out of SMS notifications
• Browser Settings: Control push notification permissions
• Support Request: Contact support@dudesthatcode.com for assistance

7.2 Quiet Hours

Set quiet hours in your notification settings to prevent non-urgent notifications during specific times (e.g., 10 PM - 8 AM). Critical security alerts will still be delivered.

7.3 Digest Options

Instead of individual notifications, choose to receive periodic digests:

• Hourly: Summary of last hour's activity
• Daily: Morning or evening digest of the day's notifications
• Weekly: Sunday recap of the week's activity

7.4 Important Notes

You cannot opt out of essential transactional and security-related communications while maintaining an active account. These are necessary for platform functionality and account security.

8. Communication Data & Privacy

8.1 Information We Collect

Through communications, we collect:

• Email addresses and phone numbers
• Message delivery status and timestamps
• Open rates and click-through rates (for email analytics)
• Device tokens for push notifications (FCM)
• Browser and device information
• Notification preferences and quiet hour settings

8.2 How We Use Communication Data

• Deliver and improve communication services
• Analyze engagement rates to optimize message content
• Detect and prevent spam and abuse
• Ensure deliverability and troubleshoot issues
• Comply with legal requirements and subpoenas

8.3 Data Protection

All communication data is protected according to our Privacy Policy. Communications are encrypted in transit (TLS/SSL) and we never sell your contact information to third parties.

9. Legal Compliance

9.1 CAN-SPAM Act (Email)

Our email communications comply with the CAN-SPAM Act:

• Accurate "From," "To," and routing information
• Clear identification of messages as advertisements (when applicable)
• Valid physical postal address in all commercial emails
• Clear and conspicuous unsubscribe mechanism
• Honor opt-out requests within 10 business days
• Monitor third-party email senders on our behalf

9.2 TCPA (SMS/Phone)

Our SMS communications comply with the Telephone Consumer Protection Act:

• Obtain prior express written consent before sending marketing texts
• Provide clear disclosure of message frequency and data rates
• Honor STOP requests immediately (within 1 message cycle)
• Maintain opt-out lists and honor preferences
• No calls or texts using automatic dialing systems without consent

9.3 GDPR (European Users)

For EU/EEA residents:

• Marketing communications require affirmative opt-in consent
• Right to withdraw consent at any time
• Clear purpose and legal basis for each communication type
• Data minimization - we only collect necessary information

9.4 CCPA (California Residents)

California residents can opt out of marketing communications and request deletion of communication data, subject to legal retention requirements.

9.5 Third-Party Service Compliance

• SendGrid/Twilio: All communications comply with Twilio's Acceptable Use Policy and Messaging Policy
• Stripe: Payment communications follow Stripe's terms and requirements
• Firebase: Push notifications comply with Google's Firebase Cloud Messaging policies

10. Communication Security

10.1 Encryption & Security

• All emails sent over encrypted connections (TLS 1.2+)
• SMS messages transmitted securely through Twilio's infrastructure
• Push notifications encrypted via Firebase Cloud Messaging
• Email authentication using SPF, DKIM, and DMARC

10.2 What We Never Ask For

We will never request via email, SMS, or push notification:

• Your password or login credentials
• Full credit card numbers or CVV codes
• Social Security Number (SSN) or Tax ID (we use secure forms for tax documents)
• Bank account passwords or PINs

10.3 Reporting Suspicious Communications

If you receive suspicious emails, texts, or notifications claiming to be from Dudes That Code, please forward them to admin@dudesthatcode.com immediately.

11. Third-Party Communications

We do not sell or share your contact information with third parties for their marketing purposes. Service providers (SendGrid, Twilio, Stripe, Firebase) process your information solely to deliver services on our behalf and are contractually obligated to protect your data.

You may receive communications directly from:

• Stripe: For payment-related matters (governed by Stripe's policies)
• Firebase/Google: For critical service notifications
• These are not controlled by this policy - refer to each provider's policies

12. Changes to This Policy

We may update this Communications Policy periodically. Significant changes will be communicated via email or platform notification. Your continued use of communication features after changes constitutes acceptance of the updated policy.

13. Contact & Support

For questions about our communication practices or to update your preferences: