How Recipe Book protects information
This page summarizes the safeguards used for personal data, email preferences, and public site features.
Data protection
Email addresses and unsubscribe tokens are encrypted at rest. Keyed or one-way hashes are used for duplicate checks and token lookups without placing the original values in searchable database columns.
Controlled access
Administrative areas require authenticated, authorized access. Public forms use server-side validation, CSRF protection, consent checks where required, and rate limits to reduce abuse.
Email controls
Every site email includes privacy, security, and tokenized unsubscribe links. Recurring content and promotional messages require a separate checkbox and email confirmation, are sent through a rate-limited server queue, and are not reactivated by unrelated email forms after an unsubscribe.
Contact message controls
Contact messages use CSRF protection, strict length and format validation, a hidden spam trap, request throttling, encrypted storage, parameterized database writes, and escaped administration and email output.
Responsible operation
No online system can guarantee absolute security. Recipe Book limits collected data, avoids exposing sensitive values in public responses, and keeps security-sensitive configuration outside frontend code.