Policies & agreements
Privacy Notice
How Hafrix handles website enquiries, accounts, operational records and analytics, and how to contact Briza Group LLC.
Review draft · 21 September 2026. This notice describes the current product surfaces and the proposed commercial privacy framework. The retention schedule and service-provider register are being finalized before an unrestricted launch.
Contact and responsibility
Hafrix is operated by Briza Group LLC, 12955 Biscayne Blvd Ste 200 #128, Miami, FL 33181, United States. Send privacy enquiries to info@brizagroup.com; telephone +1 (561) 571-1121.
For website enquiries and management of our customer relationship, Briza Group LLC determines how the information is used. For personal information a customer places in its operational workspace, the customer determines the business purpose and Hafrix processes it under the applicable agreement. Contact your employer or workspace administrator about the business records they manage.
Information handled by the service
| Context | Information involved | Purpose |
|---|---|---|
| Demo and support requests | Name, work email, company, message and email-confirmation status | Respond to the request and maintain the conversation |
| Website protection | Request address, browser information and security events | Prevent misuse, diagnose failures and protect the service |
| User accounts | Identity, workspace membership, roles, authentication and session records | Sign-in, access management and account security |
| Customer operations | Records customers enter, such as contact details, assigned personnel, tickets, signatures and attachments | Deliver the workflows chosen by the customer |
| Product support | Details a user submits and information needed to investigate the reported issue | Troubleshooting and responding to the user |
Please avoid putting passwords, payment-card details or unrelated sensitive personal information into free-text support forms. Operational imports should contain only the information required for the intended workflow.
Website analytics and browser storage
The marketing website currently loads Google Analytics to understand visits and use of the website. Google receives browser and page interaction information and may use analytics cookies. The website tag is not installed in the authenticated application or platform administration layout. One-time request-confirmation tokens are removed from the page address before the tag loads.
The signed-in application uses browser storage for sessions and supported offline work. This is separate from website analytics. On a shared device, follow the workspace's sign-out and device-management procedures. A submitted field action is not considered synchronized until the application confirms synchronization.
You can manage cookies and site storage in your browser and review Google's information about partner-site data. Browser controls can affect sign-in and offline features. A jurisdiction-appropriate analytics consent and preference process is part of the open-launch privacy work; this draft does not claim that such a preference center is already available.
Access and service providers
Authorized customer users see information according to their workspace access. Infrastructure, storage, communication and other service providers may process information needed to operate the contracted service. Website analytics is provided by Google. Customer-selected integrations may involve additional providers under the customer's own arrangements.
The service-provider register should identify the purpose, processing location and transfer arrangements applicable to the customer. A US business address does not mean all customer data is hosted in the United States. Confirm required hosting and transfer conditions during contracting.
Retention and your requests
Information should be retained for its operational or contractual purpose, applicable legal obligations and a defined security or recovery period. The agreed schedule must distinguish active workspace data, enquiry records, security logs and backup copies. Deleting an active record does not imply that every historical backup is rewritten immediately.
Contact us to ask about access, correction, deletion or other applicable privacy rights. We may need to verify your identity and authority and coordinate with the workspace customer. Where applicable, you may also contact the relevant supervisory authority. Specific rights and lawful processing grounds depend on the jurisdiction and processing activity; those details must be included in the finalized notice.
Keeping this notice current
We will identify material changes to the finalized notice and provide an updated effective date. Read this notice alongside the DPA, security overview and your customer agreement.
Keep the context
Questions aboutyour requirements?
Talk through your workspace, data requirements and the agreements that apply to your team.
Discuss your requirements