Privacy, layer by layer.
A small stacking game has a small information footprint, but email and hosting still deserve an explanation.
The active tower
Sweet Stack calculates moving layers, overlap and the result inside your current browser page. No player account receives the tower or an ongoing performance history. Restarting or reloading begins another attempt instead of loading a cloud save.
A remembered preference
The storage banner records your decision. Allowing display preferences also enables a separate reduced-motion record. These values are not tower measurements; the Cookies inventory explains the two records and how to remove them.
The message you build
Contact combines your name, reply email, topic, message and optional context into a draft. It is prepared on this device, not delivered as a web form submission. Use your email application to review it and decide whether to send.
The message that arrives
When an email is actually sent, the receiving mailbox and mail providers may handle the content and delivery headers. The correspondence is used to address the issue and any related follow-up. Never include account secrets or payment credentials in a gameplay report.
Where technical logs may exist
A server must receive requests to deliver the site files. Its security or access logs may therefore record an IP address, time and requested resource independently of the stacking code. No analytics vendor, advertising pixel or payment service is embedded in these pages.
Questions at any layer
Write to [email protected] about a privacy issue or retained exchange. You can request a correction or removal and ask for provider or retention details. The operator's hosting and mail arrangements are separate from browser storage, so this notice does not assign them an unverified country or deletion period.
Choose what this browser remembers
Storage controls are separate from information already sent in an email.