Smart Recipient Selection
PREMIUM FEATURE
Free: Select 1 recipient
Paid: Unlimited recipients
Industry-Standard Security. Row Level Security Isolation. Complete Transparency.
How DeathNote Works
Private delivery, encrypted storage, and fail-safe timing rules designed around the product DeathNote ships today.
Three-step process overview
1. Sign Up
Create an account, then manage writing, timing, recipients, and delivery rules from the same DeathNote workspace.
2. Write Messages
Write, revise, print, and save private messages with a rich editor, templates, and direct recipient controls. Your content stays attached to your account until delivery conditions are met.
3. Automatic Delivery
Reminder emails, final warnings, and verification checks run before any delivery attempt. If a critical dependency fails, the system skips sending instead of guessing.
Invite Freely, Select Carefully
Recipient selection stays explicit. You can invite as many contacts as needed, then decide exactly who should receive a message if delivery is ever triggered.
Unlimited Invitations
FREE FOR ALL USERS
Secure contact management with cryptographically signed invitation tokens and verified email delivery. No artificial limits.
Free Forever
- Unlimited contact invitations
- 1 selected recipient
- 30-day check-in intervals
- Secure message storage
Paid Features
- Unlimited recipients
- Custom check-in intervals (1-365 days)
- Priority support
- Advanced delivery options
Control & Safety: Only contacts you explicitly select will receive your death note. This prevents accidental delivery and ensures your final message reaches only those you intend.
What Happens When You Miss a Check-in
DeathNote gives you warning emails, re-checks your latest status, and only proceeds when delivery conditions still qualify.
User misses verification deadline
Your scheduled check-in period expires without confirmation.
Immediate: Send early warning
We immediately send you an urgent notification to check-in.
Final warning sent
A final urgent reminder is sent giving you one last chance to check-in.
Delivery window opens
After the final warning window passes, DeathNote evaluates the latest verification state and begins private delivery only if the account still qualifies.
Send death notes to selected recipients
Your final messages are delivered to contacts you've specifically selected to receive them.
Keep delivery private
DeathNote's core experience is direct delivery to selected recipients rather than a public posting or comment flow.
Lock the account and record delivery activity
Once delivery reaches a terminal outcome, the account is marked expired, locked from further editing, and the final delivery state is recorded for review if something goes wrong.
Important: You receive warning emails before delivery. Checking in from any reminder resets your timer and keeps your messages private.
Comprehensive Security Architecture
A public summary of the protections, hosted infrastructure, and fail-safe rules behind private message delivery.
Security Monitoring
Critical routes and delivery jobs are monitored through status checks, logs, and health endpoints.
Encrypted Storage
Messages live inside encrypted hosted infrastructure and travel over TLS-protected connections.
Privacy Controls
The public DeathNote flow is centered on private recipient delivery, account controls, and clear privacy documentation.
Strict Privacy
Row Level Security helps isolate account data at the database layer so each user sees only their own records.
Authentication & Access Control
Flexible Sign-In
Email and password is always supported, and OAuth options may vary by current configuration.
Hosted Session Management
Signed-in sessions, protected routes, and password recovery flows run through Supabase Auth.
Shared Account Rules
Every supported sign-in method lands in the same DeathNote account and delivery settings.
Explicit Recipient Selection
Messages only go to contacts you explicitly choose in the dashboard.
Invitation Boundaries
Adding a contact does not automatically make them a recipient or expose your note content.
Billing Separation
Payment details are handled by Stripe rather than stored in DeathNote message records.
Data Encryption & Privacy
Encrypted Storage
Message and recipient data are stored in encrypted hosted infrastructure.
TLS 1.3 Transport Security
Traffic is encrypted in transit between browser and services.
Row Level Security Isolation
Database policies isolate each account's records.
Recipient Privacy
Contact emails are used for invitations and delivery rather than public discovery.
Hosted Backups and Recovery
Platform providers handle database backup and recovery operations behind the scenes.
Deletion and Export Controls
Users can manage their account data, but critical personal records should still be kept in independent backups you control.
Infrastructure & Network Security
Hosted Infrastructure
Vercel, Supabase, Stripe, and Resend handle hosting, auth, billing, and email delivery.
Health Checks
Public and internal endpoints help monitor timing jobs and delivery-related routes.
Rate Limiting and Validation
Abuse-sensitive endpoints validate inputs and apply protective request handling.
Environment Secret Management
Sensitive keys stay in deployment environment configuration rather than shipping to clients.
Rate Limiting
Critical routes are designed to reduce abuse and accidental retries.
Fail-Safe Delivery
If a critical dependency or verification check fails, DeathNote does not send the message.
We Build for Ourselves Too
The creators of DeathNote use this platform for their own final messages. We built it with the same operational constraints and privacy expectations we expect everyone else to rely on.
Database & Application Security
Row Level Security (RLS)
Database-enforced data isolation per user
SQL Injection Prevention
Typed queries and server-side validation reduce unsafe data access patterns.
Protected Editor Surfaces
Rich-text content is handled through shared editor constraints and sanitization rules.
Authenticated API Routes
Sensitive actions require account context and route-level authorization.
Input Sanitization
Inputs are validated before they affect delivery, billing, or editor workflows.
Distributed Locking
Prevents race conditions and data corruption
Signed Billing Webhooks
Stripe webhook processing uses signature verification and idempotent handling.
Monitoring & Compliance
External Status Monitoring
Uptime and route health are monitored through external status checks.
Delivery and Account Logs
Operational logs help track critical account, billing, and delivery events.
Build and Test Gates
Changes are validated with type checks, builds, and automated tests before shipping.
Terms and Privacy Documentation
Public policy pages explain data handling, billing, and account responsibilities.
Hosted Payment Compliance
Stripe handles payment data under its own PCI-managed infrastructure.
Operational Review
Failures are surfaced through monitoring, logs, and support channels for follow-up.
Private Delivery Safeguards
Selected Recipients Only
Nothing is delivered unless you explicitly select that recipient.
No Public Posting Layer
DeathNote does not require public posting or a public comment surface for delivery.
Editable Until Delivery
You can keep revising message content, recipients, and timing while your account stays active.
Separate Eulogy Workflow
Eulogies are a separate writing tool, not a public output automatically attached to delivery.
Printed Copies Stay User-Controlled
Print and copy tools generate user-owned documents without exposing the surrounding dashboard UI.
Fail-Closed Delivery Logic
If verification or infrastructure checks do not pass, DeathNote skips sending instead of risking a bad delivery.
Security & Privacy Commitment
Your trust is our foundation. Learn about our commitment to protecting your most personal messages.
Terms of Service
Not a Legal Document
DeathNote is not a legal document and is not a replacement for legally binding contracts, wills, or estate planning documents.
Service Description
Our service allows users to store messages that are automatically shared if check-ins are missed. Paid subscriptions enable additional features.
User Responsibilities
Users are responsible for maintaining accurate contact information and responding to check-in emails.
Privacy Policy
Data Collection
We collect only essential information: email addresses, names, and message content. No unnecessary personal data is stored.
Data Security
All messages are encrypted and stored securely. Access is strictly limited to automated systems and essential maintenance only.
Account Deletion
Users may delete their accounts and all associated data at any time. This cannot be reversed.
Sign In Your Way
DeathNote supports email and password, and may also expose OAuth sign-in options depending on the current auth configuration.
Every supported sign-in path lands in the same account and uses the same privacy, billing, and delivery rules.
Free to start, with optional paid features.
What Delivery Looks Like
The core DeathNote experience is private, editable, and centered on the people you choose.
Choose who receives it
Add contacts freely, then explicitly mark which recipients should receive your message if delivery is triggered.
Keep editing until it matters
You can keep refining your note, print a clean copy, or test the editor workflow while your account remains active.
Use eulogy tools separately
When you need a eulogy, DeathNote provides a separate guided writing flow instead of attaching any public page to the delivery path.
Frequently Asked Questions
Complete guide to private final-message delivery, proof-of-life timing, editor capabilities, and the safeguards DeathNote uses today.
Common Use Cases & Scenarios
Security & Privacy
Reliability & Trust
Technical Details
Using DeathNote
Features & Subscription
Business & Trust
Design Philosophy
Ready to Secure Your Legacy?
Start with the free plan, set up your private delivery flow, and upgrade only if you need more recipients or flexible timing controls.
Free. Forever. Always.