Privacy Policy
This Privacy Policy explains how BLISSe handles information collected through blisse-app.com and related demo links. BLISSe is currently a product and portfolio experience for visual place discovery.
Information We Collect
We may collect limited technical and usage information when you visit the website or click a demo button, including:
- Demo button click type, such as end-user demo or business demo.
- Page path, referring page, browser/user-agent information and timestamp.
- A randomly generated session identifier stored locally in your browser.
- Information you voluntarily send by email or through direct contact.
How We Use Information
We use this information to understand interest in BLISSe, measure demo demand, improve the website and respond to business or user inquiries. We do not sell personal information.
Analytics and Firebase
BLISSe uses Firebase services to store aggregated demo click counters and related click events. Firebase is provided by Google and may process technical information according to Google's service terms and privacy practices.
Cookies and Local Storage
The website may use browser local storage to create a session identifier for demo click measurement. You can clear local storage through your browser settings.
Third-Party Links
The website may link to the BLISSe demo, email, Google services, Firebase or other third-party services. Their privacy practices are controlled by those services, not by BLISSe.
Data Retention
Demo click counters and related events may be retained as long as needed to understand product interest, maintain the website and evaluate business demand.
Your Choices
You can disable or clear local storage in your browser. If you contact us by email, you can ask us to delete or correct information you provided directly.
Contact
For privacy questions or requests, contact shaabon.royei@gmail.com.
Legal Note
This policy is a general privacy notice for the current BLISSe website and demo. It is not legal advice and may need to be updated as the product, audience, jurisdictions or data practices change.