Terms
Move into Terms to review the usage rules, access boundaries, and responsibilities that apply on the public surface.
Open pagePrivacy
Privacy is treated as an operating principle here, not only as a legal page
This page explains how Tranhatam.com handles the public surface, intake routes, and the minimum data layers needed to run, respond, and protect the system.
Current scope
What this page currently covers on the public web
-
Minimum technical data
Infrastructure may generate basic technical logs to load pages, prevent abuse, rate limit requests, and keep public routes safe.
-
Data a user intentionally submits
When you use Contact, Partner, Newsletter, or Auth, the submitted data enters only the intake and security layers needed to respond through the correct route.
-
No advertising tracking
The website is not designed to run ad pixels, behavioral tracking for data resale, or profiling beyond real operating need.
Operating rules
How privacy stays consistent across the system
-
Collect only with a clear purpose
Each form or route should request only the data needed for intake, authentication, access support, or the next continuity step.
-
Keep data in the correct layer
Data must not be hard-coded in scattered places, copied casually, or moved outside technical and legal processing layers that are explicitly authorized.
-
Update the policy when the system changes
When the member system, commerce layer, or CMS opens new public-facing surfaces, this page must be updated before those layers are treated as live-ready.
Related routes
If you need more context on system boundaries, open the correct next route
Notice
Open Notice to review the current operating state and what is still in a controlled build phase.
Open pageContact
Use Contact if you need to clarify how data is handled for a specific need or route.
Start a conversation