Cookie Policy
Cookie Policy
Effective Date: November 20, 2025
Version: 1.0
Plain English Summary
Cookies are small text files stored on your device that help websites remember your preferences and understand how you use the site. LocalBeat uses cookies to keep you logged in, remember your settings, analyze how our platform is used, and improve your experience. We use essential cookies (required for the site to work), functional cookies (remember your preferences), and analytics cookies (help us understand usage patterns). You can control cookies through your browser settings, but disabling some cookies may affect site functionality. This policy explains what cookies we use, why we use them, and how to manage your cookie preferences.
1. What Are Cookies?
1.1 Definition
Cookies are small text files that are placed on your computer, smartphone, or other device when you visit a website. Cookies allow the website to recognize your device and remember information about your visit, such as your preferences and login state.
1.2 How Cookies Work
When you visit a website that uses cookies:
- The website sends a cookie to your browser
- Your browser stores the cookie on your device
- On future visits, your browser sends the cookie back to the website
- The website reads the cookie and uses the information to provide features or personalization
1.3 Cookie Categories
Cookies can be categorized in several ways:
- Session vs. Persistent: Session cookies expire when you close your browser; persistent cookies remain until deleted or expired
- First-Party vs. Third-Party: First-party cookies are set by the website you're visiting; third-party cookies are set by other domains
- Purpose: Cookies can be essential, functional, analytics, or advertising-related
1.4 Similar Technologies
This policy also covers similar technologies including:
- Local Storage: Browser storage mechanisms that persist data locally
- Session Storage: Temporary storage cleared when the session ends
- Web Beacons: Small transparent images used to track activity
- Pixels: Tiny images used for tracking and analytics
2. Why We Use Cookies
2.1 Essential Functionality
Cookies are necessary for LocalBeat to function properly. Without cookies, we cannot:
- Keep you logged in as you navigate between pages
- Remember your session and prevent repeated logins
- Maintain security and prevent fraud
- Provide basic platform features
2.2 User Experience
Cookies enhance your experience by:
- Remembering your preferences and settings
- Personalizing content and features
- Saving your progress when creating content
- Providing language and region customization
2.3 Performance and Analytics
Cookies help us understand how you use our platform so we can:
- Analyze usage patterns and identify popular features
- Measure performance and load times
- Identify and fix bugs and issues
- Improve the platform based on user behavior
2.4 Security
Cookies help protect your account by:
- Detecting suspicious activity and unauthorized access
- Preventing cross-site request forgery (CSRF) attacks
- Verifying your identity during sensitive operations
- Maintaining audit logs for security monitoring
3. Types of Cookies We Use
3.1 Essential Cookies
Purpose: Required for the platform to function. Cannot be disabled.
What They Do:
- Maintain your login session
- Remember your authentication state
- Enable core platform features
- Provide security protections
- Load balance traffic across servers
Legal Basis: Necessary for contract performance (providing the service you requested)
3.2 Functional Cookies
Purpose: Remember your preferences and enhance functionality.
What They Do:
- Remember your dashboard layout preferences
- Save your language and region settings
- Store your theme preference (light/dark mode)
- Remember your cookie consent choices
- Maintain your "remember me" login state
Legal Basis: Legitimate interest in providing a personalized experience
3.3 Analytics Cookies
Purpose: Understand how users interact with our platform.
What They Do:
- Track page views and navigation patterns
- Measure feature usage and engagement
- Identify performance bottlenecks
- Generate usage statistics and reports
- Help us improve the platform
Legal Basis: Legitimate interest in improving our service (or consent where required by law)
3.4 Advertising Cookies
Current Status: We do not currently use advertising cookies.
If we introduce advertising cookies in the future, we will update this policy and obtain your consent as required by law.
4. Specific Cookies
4.1 Authentication Cookies (Clerk)
| Cookie Name | Purpose | Type | Duration |
|---|---|---|---|
| __session | Maintains your login session | Essential | 7 days |
| __clerk_db_jwt | Stores authentication token | Essential | Session |
| __client_uat | User authentication timestamp | Essential | Session |
4.2 Session Management Cookies
| Cookie Name | Purpose | Type | Duration |
|---|---|---|---|
| next-auth.session-token | Next.js session management | Essential | 30 days |
| next-auth.csrf-token | CSRF protection | Essential | Session |
4.3 Preference Cookies
| Cookie Name | Purpose | Type | Duration |
|---|---|---|---|
| theme | Remembers light/dark mode preference | Functional | 1 year |
| locale | Stores language preference | Functional | 1 year |
| cookie-consent | Remembers your cookie consent choices | Functional | 1 year |
4.4 Analytics Cookies (Vercel Analytics)
| Cookie Name | Purpose | Type | Duration |
|---|---|---|---|
| _va | Tracks page views and events | Analytics | 2 years |
| _vercel_no_cache | Performance tracking | Analytics | Session |
4.5 Security Cookies
| Cookie Name | Purpose | Type | Duration |
|---|---|---|---|
| __cf_bm | Cloudflare bot management | Essential | 30 minutes |
| cf_clearance | Cloudflare security clearance | Essential | 1 year |
5. Third-Party Cookies
5.1 Authentication (Clerk)
We use Clerk for authentication services. Clerk may set cookies to:
- Manage your login session
- Provide single sign-on functionality
- Remember your authentication preferences
For more information, see Clerk's Privacy Policy.
5.2 Analytics (Vercel)
We use Vercel Analytics to understand platform usage. Vercel may set cookies to:
- Track page views and user journeys
- Measure performance metrics
- Identify popular features and content
Vercel Analytics is privacy-focused and does not track users across sites. For more information, see Vercel's Analytics Privacy Policy.
5.3 CDN and Security (Cloudflare)
We use Cloudflare for content delivery and DDoS protection. Cloudflare may set cookies to:
- Protect against malicious traffic and bots
- Optimize content delivery
- Provide security clearance for verified traffic
For more information, see Cloudflare's Privacy Policy.
5.4 Payment Processing (Stripe)
When you make a payment, Stripe may set cookies to:
- Process your payment securely
- Prevent fraud and abuse
- Remember your payment preferences
For more information, see Stripe's Privacy Policy.
5.5 User Control
While we choose third-party services carefully, we do not control their cookie practices. Please review each service's privacy policy for details about their use of cookies.
6. Managing Cookie Preferences
6.1 Browser Settings
You can control cookies through your browser settings. Most browsers allow you to:
- View and delete existing cookies
- Block all cookies
- Block third-party cookies only
- Receive alerts before cookies are set
- Delete cookies when you close your browser
6.2 Browser-Specific Instructions
Google Chrome
- Click the three-dot menu > Settings > Privacy and security
- Click "Cookies and other site data"
- Choose your preferred cookie settings
Mozilla Firefox
- Click the menu button > Settings > Privacy & Security
- Under "Cookies and Site Data", click "Manage Data" or adjust settings
Safari
- Go to Preferences > Privacy
- Adjust "Cookies and website data" settings
Microsoft Edge
- Click the three-dot menu > Settings > Cookies and site permissions
- Click "Manage and delete cookies and site data"
6.3 Impact of Blocking Cookies
If you disable cookies:
- Essential Cookies Blocked: You will not be able to log in or use the platform
- Functional Cookies Blocked: Preferences will not be saved, and features may not work as expected
- Analytics Cookies Blocked: No impact on functionality; we simply won't collect usage data
6.4 Cookie Consent Manager
If applicable in your jurisdiction, we provide a cookie consent manager that allows you to:
- Accept or reject non-essential cookies
- Choose specific cookie categories
- Change your preferences at any time
- View detailed information about each cookie
6.5 Do Not Track
Some browsers offer a "Do Not Track" (DNT) setting. Because there is no industry standard for DNT signals, we do not currently respond to DNT browser settings. However, you can control cookies through the methods described above.
7. Cookie Consent
7.1 Consent Requirements
Depending on your location, we may require your consent before setting non-essential cookies:
- EEA, UK, Switzerland: Consent required for all non-essential cookies under ePrivacy Directive and GDPR
- California: Notice and opt-out rights under CCPA
- Other Jurisdictions: Compliance with local laws as applicable
7.2 How We Obtain Consent
Where required, we obtain consent through:
- Cookie banner displayed on first visit
- Clear information about cookie types and purposes
- Granular controls for different cookie categories
- Easy-to-use accept/reject options
7.3 Withdrawing Consent
You can withdraw consent at any time by:
- Accessing the cookie preference center in your dashboard
- Deleting cookies through your browser settings
- Contacting privacy@mylocalbeat.com
Withdrawing consent does not affect the lawfulness of Processing based on consent before withdrawal.
7.4 Consent Records
We maintain records of your cookie consent choices, including:
- Date and time of consent
- Cookie categories accepted or rejected
- Consent banner version
- Method of consent (accept all, reject all, custom settings)
8. Cookie Retention
8.1 Session Cookies
Session cookies are temporary and are deleted when you:
- Close your browser
- Log out of your account
- End your browsing session
8.2 Persistent Cookies
Persistent cookies remain on your device until:
- They reach their expiration date (see cookie table in Section 4)
- You manually delete them
- You clear your browser's cookies and data
8.3 Maximum Retention
Our cookies have maximum retention periods as follows:
- Session cookies: Deleted when session ends
- Authentication cookies: 7-30 days
- Preference cookies: 1 year
- Analytics cookies: 2 years
8.4 Cookie Refresh
Some cookies may be refreshed (expiration date extended) when you actively use the platform. This ensures your session remains active and your preferences are preserved.
9. Updates to This Policy
9.1 Policy Changes
We may update this Cookie Policy to reflect:
- Changes in our use of cookies
- New cookies or technologies
- Changes in applicable laws or regulations
- Feedback and best practices
9.2 Notification
When we make material changes to this policy, we will:
- Update the "Last Updated" date at the top
- Display a notice on our website or dashboard
- Request renewed consent if required by law
9.3 Review
We recommend reviewing this policy periodically to stay informed about how we use cookies.
10. Contact Information
For questions about this Cookie Policy or to manage your cookie preferences, please contact:
Privacy TeamLocalBeat
Email: privacy@mylocalbeat.com
Cookie Questions: cookies@mylocalbeat.com
General Support: support@mylocalbeat.com
Website: https://mylocalbeat.com
Last Updated: November 20, 2025
Version: 1.0
This Cookie Policy explains how LocalBeat uses cookies and similar technologies. You can manage your
cookie preferences through your browser settings or our cookie consent manager. For more information about
how we process personal data, see our Privacy Policy.
If you have questions about this document, please contact us at legal@mylocalbeat.com