7 WritingThis page explains how 7 Writing currently handles data. The maintainer is Blaine. Last updated: 2026-10-15. Use the contact page to ask about or request action on your data.
Accounts and learning records
Accounts distinguish learners. The server stores usernames, scrypt password hashes, session records and, when passkeys are used, credential public keys and related details. It does not store plaintext passwords. A sign-in cookie maintains your session.
Learning progress is stored in the local browser and synced to the server database after sign-in. Synced data includes exercise answers, essays and related feedback, depending on the features used. The server maintainer has operational access; separate account records do not mean the maintainer is technically unable to access them.
AI requests
When you request AI feedback, question generation, revision checks or image recognition, the relevant text or images are sent to the configured AI provider. Do not submit unnecessary sensitive information such as names, identity documents or contact details. Provider data handling depends on the service's policies.
The server logs the time, task, model, duration, usage and success or failure of AI calls. Error logs may contain error details returned by the service. Essays and feedback in learning progress are stored separately.
Waitlist and access records
The waitlist stores the email, optional practice needs and submission time you provide. Email is used for trial opening notifications, and practice needs help us understand product demand. We ask separately before quoting feedback publicly. Currently, information is recorded only; automated notification email is not connected. The server processes IP addresses for rate limiting and keeps operational access logs.
Contact form
The project server stores your email, message and submission time only to handle product feedback, content corrections and data requests. This does not add you to the waitlist or automatically send email. The server processes IP addresses for rate limiting but does not save IP addresses in the message file. Retention and deletion follow the section below.
Page resources and cookies
The site requests fonts from Google Fonts, so your browser sends network requests to that service. Sign-in cookies maintain sessions; browser local storage keeps learning records and interface state. Advertising tracking is not connected. Public page analytics are described below.
Retention, backups and requests
There is no unified automatic expiry and deletion feature currently. Server backups may retain historical data. To access, correct or delete account data, learning records, waitlist details or contact messages, contact the maintainer and identify the account or email. Identity verification may be needed. Do not send account passwords.
This page describes the current implementation. It will be updated if new data uses or third-party services are added.
Public website analytics
Public website pages use Google Analytics 4 and analytics cookies to measure visits. The tag is not installed in the signed-in practice app. Essays, answers, waitlist or contact form content and URL query parameters are not sent. Google Signals and advertising personalization are disabled.
The public website uses a site_lang cookie to remember the language you choose with the language switcher for up to one year. This cookie is only for language preferences, not sign-in credentials.