1. Scope and status
This draft concerns the public EFG website. It is a code-based description of a few current features, not a complete inventory of information that a hosting provider, email service or platform may process. EFG’s legal operator, effective date, applicable regions and final privacy contact process remain to be supplied or confirmed.
2. Current site paths shown in the code
Optional page-load analytics
If the deployment sets POLSIA_ANALYTICS_SLUG, the framework mounts a page-load beacon. In the browser, it reads or creates a random visitor identifier in local storage under polsia_vid, then sends the app slug and visitor identifier to the configured Polsia API base (default https://polsia.com). This code path does not confirm whether analytics is enabled on the live deployment, or what Polsia does with a received beacon, who receives it, or how long platform-side records remain.
Theme preference
The light/dark theme control uses the browser’s local storage key theme for the selected preference. The app code describes this browser-side setting; it does not establish any separate server storage for it.
Example name submission
The public /example page sends a submitted name to /api/example. The current handler validates the name and returns it with a generated identifier; a GET request returns an empty list. The handler’s database seam is commented out, so this code does not persist the submission in EFG’s application database. The page holds the returned item in client state. This does not establish whether hosting logs or any system outside this code records the request or response.
Email to EFG
A visitor may choose to email EFG at efg@polsia.app. Following the link opens the visitor’s email software; the visitor chooses whether to send a message. If a message is sent, its handling and retention depend in part on the mailbox provider and settings, which have not been confirmed for this draft.
3. Practices not confirmed by this repository
The available app code does not establish hosting request-log contents or retention, mailbox access or retention, platform-side analytics recipients or retention, or whether anything outside the shown handler retains /example submissions. This draft therefore makes no promise about those practices, deletion, security measures or sharing. EFG should confirm each item with the relevant providers before finalizing this notice.
4. Questions and privacy requests
For a question about this draft, email efg@polsia.app. This contact link is not yet a defined process for exercising privacy rights. The owner must confirm which rights and regions apply, how requests should be handled, and where information may be transferred.
5. Updates
EFG may revise this page as the site or its data practices change. Before publication as a final policy, the owner should add the effective date and review any changes against the actual deployment and applicable law.
6. Owner completion list
Before this notice is treated as final, the owner should confirm:
- EFG’s legal entity, contact/address details, effective date and applicable privacy-rights process.
- Production analytics status, platform recipients and retention, hosting request logs and retention, and mailbox provider and retention.
- Whether
/exampleis intended for production and whether any system outside its shown handler retains submissions. - Applicable regions, international transfers and the intended age-related scope.