Privacy
What hide.lat keeps.
Effective September 8, 2026
Public workbench
Source pasted into the public workbench is processed for the current request. It is not saved as an account project or build record. Operational logs retain request timing, response status and security information, but not the pasted script body.
Accounts and projects
When you create an account, hide.lat stores your email address, display name, password hash, verification state and account settings. Project source and build output are encrypted at rest. Each managed build retains an encrypted snapshot of both its original input and protected output so the exact release can be recovered later.
Keys, devices and execution records
License keys are stored as one-way hashes after initial display. Device and network identifiers used for abuse prevention and licensing are also hashed. Execution records can include status, denial reason, runtime label and timing data.
Cookies and advertising
hide.lat uses an essential session cookie to keep signed-in accounts authenticated. Anonymous pages may load Google AdSense, which can use cookies or similar technologies to select, measure and prevent abuse of ads. Signed-in accounts do not load AdSense. Google explains its advertising data practices in its own privacy documentation.
Email addresses are used for verification, account recovery and direct replies to support requests. Transactional delivery is handled by the configured mail provider. hide.lat does not sell account email addresses.
Deletion and questions
Use the dashboard support area to request account data help or deletion. Security and fraud records may be retained where reasonably necessary to protect the service and comply with legal obligations.