Your expansion plan
The planning tools calculate in your browser. Remembering a draft on this device is optional and off by default. If enabled, local storage retains your working plan in that browser profile. Someone using the same profile may be able to access it.
Use the reset control in the planning workspace to remove the saved draft, or clear this site’s storage in your browser settings. JSON and printable brief exports are created locally. Clearing site data can permanently remove an unexported draft. Plan inputs are not automatically attached to either form or sent to the owner.
Your learning progress
The learning hub and article controls work without an account. Saving progress on this device is optional and off by default. When enabled, a separate record in this browser holds public guide/tool identifiers, read or tried status, bookmarks and the versions of completed practice activities. It does not store your practice answers, expansion-plan inputs or form submissions. Progress is not sent to ELN’s owner.
Use learning settings to export or reset this learning record. Resetting learning does not reset your separate planning draft. Clearing all site data can remove both. People sharing the browser profile may see saved activity. Learning points and milestones describe your activity, rather than a legal qualification or permission to operate.
Interest and contact forms
The interest form asks for name, company, annual recurring revenue (ARR) and email. ARR is optional; you can state the currency and amount, “not recurring” or “not known.” The contact form asks for your comments and email. Use it for enquiries, corrections and privacy requests.
An interest registration requests ELN Network updates and follow-up about joining the network. Contact enquiries are used to review and respond to the enquiry you submitted. Submissions are visible in an owner-only board protected by sign-in. Your details are not published or used for unrelated marketing. To stop network updates, use the contact form and identify the email you registered with. Please keep confidential contracts, payment credentials and sensitive personal records out of comments.
Retention and your controls
The application automatically removes form submissions after 365 days from submission. The owner can delete a record earlier. To request access, correction or deletion, use the contact form and identify the email you used; verification may be needed before a record is disclosed or changed.
Deleting a live record does not remove copies already exported by the owner, correspondence held elsewhere, or provider records subject to separate retention. An encrypted database backup runs daily to a separate private Railway storage bucket. Backup copies become eligible for deletion after six days; expired copies are removed after a successful backup, so a failed job can delay removal. Deleting a live record does not immediately edit an older backup. A restoration must reapply known deletion requests before records are used again. The owner should manage any exported copies consistently with the original purpose and your request.
Storage and access
Submitted form information is held in a database on persistent Railway storage. It is separate from public guides and browser-local plans. Public API requests cannot read the owner’s board, exports or records. Passwords are stored as salted hashes, and sign-in sessions use an HTTP-only cookie that expires after 12 hours. Single-use recovery codes support password recovery without email; only their hashes are stored. Changing or recovering a password revokes existing sessions.
The application does not log submitted names, email addresses, comments, ARR values or passwords. Short-lived, keyed hashes are used in memory to limit abuse; raw IP addresses are not stored by this application for that purpose. The hosting provider processes ordinary network requests separately.
Cookies and tracking
The public forms do not require an account cookie. The owner board sets a necessary sign-in cookie for its owner. The optional planning draft and optional learning record use separate browser storage keys. This build has no advertising pixel, third-party analytics service, embedded chat widget or automatic marketing emails. Fonts and application assets are served with the site.
Hosting requests and provider terms
The application and live database run in Railway’s U.S. West region. Encrypted backups use a separate Railway bucket in San Jose, California; backup encryption keys remain separate from stored backup objects. The provider can process IP addresses, request paths, browser information and timestamps to deliver and protect the service. The application sends form values in request bodies, not public URLs.
Railway’s published log documentation gives the current Hobby plan seven days of displayed log history and says a plan upgrade can restore older logs. This is not a guarantee that every provider record is permanently erased after seven days. No third-party log forwarding is configured here.
Railway publishes a Data Processing Addendum with separate roles for customer data and its own account/usage data. Publication of that document does not establish execution for this account. Applicable processing, transfer and retention arrangements remain the operator’s responsibility.
Contact ELN
Send questions or a data request through Contact us. Include the relevant page or the email used for your submission. Your contact details are used for a private response.