Information stored
For each note, ScholarNote stores a random note identifier, encrypted ciphertext, a unique encryption initialization value, the optional public profile URL supplied by the sender, creation and unread-expiration timestamps, and after reveal the first-reveal and deletion timestamps.
Information not stored
ScholarNote does not store readable note text, the decryption key, sender names, recipient email addresses, user accounts, uploaded files, browser fingerprints, or tracking identifiers in the notes database. The service does not fetch, scrape, or enrich profile links.
Browser-side encryption
Your browser generates a random 256-bit AES-GCM key and encrypts the note before transmission. The key appears after the # in the complete link. That fragment is not included in normal HTTP requests to ScholarNote. The recipient's browser uses it locally to decrypt the encrypted response.
Expiration and deletion
- The sender chooses an unread lifetime of one, three, or seven days and a post-reveal window of one, five, ten, or thirty minutes.
- The first successful reveal fixes that deadline; another reveal cannot extend it.
- Expired records are rejected immediately and removed by request-time checks and scheduled cleanup.
- Normal backup and provider-level recovery systems, if enabled by the operator, may have separate retention characteristics documented by the hosting provider.
Cookies and browser storage
The core service does not require cookies. After creation, the complete link is temporarily placed in the sender's session storage so the created page can display it. The browser clears session storage according to its own tab and session behavior. ScholarNote does not use that value for tracking.
Advertising
The first implementation contains labelled placeholders, not an advertising network. No advertising, analytics, tracking pixels, or external scripts are loaded on recipient landing or revealed-note pages. If advertising is introduced later, this notice will be updated before deployment and private-note pages will remain ad-free.
Server logs
Hosting and security infrastructure may process routine request metadata such as timestamps, requested paths, network addresses, user-agent strings, and error information for operations, abuse prevention, and security. Application code does not intentionally log note content, ciphertext, or URL fragments. Network infrastructure cannot receive the fragment during a normal request.
Public profile links
The optional profile URL is stored alongside the ciphertext and shown to the recipient before and after reveal. It is supplied by the sender, may identify them publicly, and is not independently verified. Only https:// URLs are accepted.
Legal requests
ScholarNote may preserve or disclose available records when required by a valid legal process. Because the operator does not hold the decryption key, stored note content is intended to remain encrypted; nevertheless, metadata and profile URLs may be available while a record exists.
Security limitations
No online system is perfectly secure. A recipient can copy or photograph visible text. Anyone who obtains the complete link can attempt to reveal it. Compromised devices, browser extensions, malicious software, network configuration, implementation defects, or future cryptographic weaknesses may affect confidentiality. Do not use ScholarNote for highly sensitive regulated information or as the only record of important communication.
Contact
Privacy questions and data-related requests: [privacy contact email to be added before launch]. The operator should replace this placeholder with a monitored address before public deployment.