Back
Privacy
Natty Hatty Blog Platform — Account Linking & Authentication Notice
Version: v1.0
Effective Date: November 15, 2025**
The Natty Hatty Blog Platform (“Blog Platform”) at blog.nattyhatty.com allows users to log in using their existing Natty Hatty Customer App account.
This Account Linking & Authentication Notice explains:
How authentication works
What data is accessed or shared
What data is not accessed
How your login session is stored
How minors’ accounts are protected
By logging into the Blog Platform, you agree to this Notice.
Hatty Customer App Account
1. Single Sign-On (SSO) With Your Natty Hatty Customer App Account
The Blog Platform uses Single Sign-On (SSO), meaning:
You do not create a new account
You use your existing Natty Hatty Customer App credentials
The Blog Platform verifies your identity securely
Login tokens are issued by Natty Hatty authentication servers
This keeps access simple and secure.
2. What Information Is Shared With the Blog Platform
When you log in, the Blog Platform receives only the minimum information required to attribute comments to the correct user:
✓ Required for authentication & display
Name
Email address
User ID (internal, tokenized)
Profile photo (if enabled)
Account status (active/suspended)
✓ Required for security
Session ID
Authentication token
Login timestamp
Device/browser metadata
No additional platform data is synced to the blog.
3. What Information Is NOT Shared
The Blog Platform does NOT access or store:
Payment information
Saved cards
Roster data
Child profiles or minor information
Signatures or waiver documents
Program registrations or event attendance
Organization-specific data
Parent/guardian linked accounts
Messages or platform communications
Location history
Program purchases
Medical or emergency information
Your Blog login is strictly informational for commenting, and nothing else.
4. How Authentication Cookies Work
When you log in to comment:
An authentication cookie is created
This cookie keeps you logged in until you log out
If you close the tab but do not log out, the cookie may persist
The cookie does not track you across sites
The cookie does not store sensitive information
The cookie is encrypted and limited to the Blog Platform
You may remove it at any time by logging out or clearing cookies.
5. Minor Account Protection
Because Natty Hatty serves youth communities:
Minors may read the blog
Minors should not comment
If a minor logs in and posts a comment:
The comment may be removed
Commenting access may be disabled
A guardian may be notified
Safety concerns may trigger review
Natty Hatty enforces zero-tolerance policies around minor safety.
6. Account Suspension & Blog Access
If your Natty Hatty Customer App account is:
Suspended — You may lose commenting privileges
Terminated — You will no longer be able to log into the Blog Platform
Still active — You retain full commenting access
The Blog Platform follows your main account status — it does not maintain a separate account layer.
7. No Cross-Platform Tracking
Natty Hatty does not use Blog Platform login to:
Track your behavior across the main Platform
Track your activity across websites
Link blog activity to program or payment behavior
Build marketing or behavioral profiles
Your comment interactions remain isolated to the Blog Platform.
8. Data Storage & Retention
The Blog Platform stores:
Your comments (until deleted)
Your display name and profile photo (if shown)
Your login session (until expired or logged out)
Security logs (for anti-abuse detection)
Data is stored in secure AWS environments.
9. Security Protections
Natty Hatty uses:
TLS 1.2+
AES-256 encrypted storage
Secure token authentication
Firewall & CDN protection (Cloudflare)
Automated abuse detection
Rate limiting
No AI/ML processing of user data
These controls ensure the Blog Platform remains safe for all users.
10. Revoking Access
You can revoke access at any time by:
Logging out of the Blog Platform
Clearing cookies
Requesting account deletion (Customer App)
Requesting comment removal
After revocation:
Blog Platform access stops
Comments may remain unless you request deletion
Login tokens are invalidated