What we collect
A newsletter email address when a reader chooses to subscribe, plus the account and activity information needed to protect the private admin area.
Legal / PrivacyYour information
Your information
should stay yours.
This starter policy explains the intended data boundaries for the local Insightly preview. Replace it with counsel-reviewed language before a public launch.
Last updated: September 10, 2026.
Insightly is currently a dummy-data demonstration. No Firebase project is connected, and newsletter submissions return a preview response rather than being stored. The sections below describe the intended product behaviour once services are configured.
Why we use it
To send publication updates, operate the CMS, prevent abuse, respond to requests, and understand whether the service is working as intended.
What we do not do
We do not sell subscriber information or use a reader’s email address for unrelated advertising without clear permission.
Information you provide
If you contact the publication, we receive the information in your message and the address needed to reply. If you subscribe after Firebase is configured, the email address will be stored in the project’s subscriber collection with a timestamp and source label.
Technical information
Hosting providers, security systems, and analytics tools may process basic technical information such as request time, browser type, approximate location, and error details. The final implementation should document the actual providers and retention periods used.
Cookies and local storage
Essential session cookies may be used for authenticated administration. Optional analytics should remain disabled until explicitly configured. See the cookie policy for the starter behaviour.
Choices and requests
You may ask what information is held about you, request correction, or ask for deletion where applicable. Contact the editorial team and include enough detail for us to find the relevant record.
A note from Insightly
Ask a question ↗Privacy depends on the final setup.
Before launch, confirm Firebase rules, hosting logs, analytics settings, email provider behaviour, retention periods, and the jurisdiction-specific notices your publication needs.