Privacy · Updated 14 October 2026
Your schedule stays on your side of the glass.
Releasefold is designed as a browser-local calculation tool. This notice describes what the current review build processes and what it deliberately does not collect.
Schedule inputs
Grant names, token symbols, allocation amounts, dates, and release terms are processed in your browser. To keep an in-progress Studio draft while you navigate this site, Releasefold stores valid base and comparison terms, the selected month, active mode, and synthetic-example marker in sessionStorage for this tab. The draft survives reloads and same-tab navigation, is not written to persistent localStorage, and is removed when the tab session ends or you reset the example. The current build has no application account, database, upload endpoint, or synchronization service.
Files
JSON and CSV files are created only when you choose an export action. Imported JSON is read in the browser for format and digest checks; it is not sent to Releasefold. After download, you decide where a file is stored or shared.
Wallets and networks
Wallet connection is optional and read-only. When you choose Connect wallet, Releasefold asks the injected browser provider for a public account and the selected network identifier so it can show connection status and the matching explorer. It does not request a signature, network switch, approval, balance, or transaction, and it does not store or upload the public address.
Browser and hosting data
The application does not add behavioral analytics or advertising trackers. Ordinary hosting infrastructure may still process request metadata such as an IP address, user agent, requested path, timestamp, and security log to deliver the site.
Sensitive information
Do not enter private keys, recovery phrases, confidential identity data, unpublished compensation records, or information you are not authorized to review. Use neutral schedule labels where possible.