Studio document

Privacy Policy

How the current static Got Ur Web project handles browser-local data, forms, resources, and possible hosting logs.

1. Scope and controller status

This policy describes the current static goturweb.com project. No incorporated entity, physical office, or separate data controller is claimed on this site. Questions may be directed to [email protected], an address found consistently in the domain archive, though delivery is not guaranteed by the static site.

2. Data provided through forms

The project outline and contact forms run entirely in the browser. The contact form validates fields but has no submission endpoint. It does not send or store the entered message. The project outline can be stored in localStorage only after the visitor chooses Save.

3. Local browser storage

The site uses goturweb_consent_v1 for the local-storage notice, goturweb_state_v1 for a saved project outline, and goturweb_events_v1 for a local QA event queue. These records remain on the device and can be removed through site controls or browser settings.

4. Server and hosting logs

A future host may process standard request data such as IP address, requested URL, user agent, timestamp, and response status for security and reliability. This static package does not configure a host, retention period, analytics provider, or advertising profile.

5. Analytics and advertising

No remote analytics, advertising pixel, behavioural profiling, or cross-site tracking is included in this build. The JavaScript dataLayer and event queue are local QA mechanisms and are not connected to an endpoint.

6. Third-party resources

Google Fonts may receive network request information when fonts load. A production deployment may choose locally hosted fonts to remove that request. External links lead to services with their own policies; visiting them is a separate action.

7. Purposes and legal bases

Browser-local processing supports requested functions and interface testing. If server logging is later enabled, a host may rely on legitimate interests in security and service operation. Any enquiry endpoint or analytics provider requires a policy update before activation.

8. Retention and deletion

Local records persist until cleared through the outline tool, browser storage settings, or site-data deletion. The site cannot remotely access or delete them. Hosting-log retention depends on a future host and must be documented when deployment is configured.

9. Rights and choices

Visitors can decline to interact with local tools, clear local records, block third-party fonts, and use browser privacy controls. Requests about any future server-held personal data should identify the route and approximate date so the responsible operator can investigate.

10. Changes and contact

Material changes to forms, analytics, hosting, or third parties require this policy to be revised with a new effective date. Contact: [email protected]. Do not send sensitive personal data through an address whose delivery has not been independently verified.