Legal
Privacy Policy
Effective 29 July 2026This policy describes the application's current data handling design. The final operator identity, hosting location, retention schedule and support contact must be confirmed before commercial launch.
1. Who is responsible
The organisation identified as the Fencalc operator in your order, deployment or subscription communication is responsible for the personal information processed through the service.
2. Information collected
The service stores account details such as name, email address, password hash and administrator status. It also stores subscription settings, payment method and transaction references, project records, technical calculation inputs, uploaded branding, collaboration permissions and timestamps associated with use of the service.
3. Why information is used
Information is used to authenticate users, provide project calculations, save work, control collaboration, administer subscriptions, secure the service, diagnose faults and respond to support requests. Aggregated operational information may be used to improve reliability and usability without exposing another user's project content.
4. Project access
A project owner controls which registered users receive viewer or editor access. Administrators can manage platform accounts and subscriptions, but ordinary users cannot browse projects they do not own or share.
5. Cookies and local preferences
The application uses essential session and security cookies for sign-in and request protection. Navigation placement and colour mode preferences may be stored in the browser. The current application does not require advertising cookies to provide its core functions.
6. Sharing and service providers
Information should be shared only with infrastructure, hosting, support or billing providers required to operate the service, under appropriate contractual and security controls. A short payment alert containing account, plan, amount, method and reference details may be sent to the operator through Telegram; project content is not included. Project content is visible to collaborators selected by the project owner.
7. Retention
Account, subscription and project data is retained while needed to provide the service, meet agreed record-keeping requirements, resolve disputes and protect the system. A final commercial deployment should publish its specific retention and backup periods.
8. Security
The application uses account authentication, authorisation checks and password hashing. No service can guarantee absolute security, so users should use unique passwords, restrict collaboration access and avoid placing unnecessary personal information in project notes.
9. Your choices
You may request access to or correction of account information and ask about deletion or export options by contacting the service operator. Some records may need to be retained where required by law, contract, security or legitimate record-keeping needs.
10. Policy updates
This policy may change as hosting, billing, support or product features evolve. The effective date will be updated when a revised policy is published.
11. Contact
Privacy questions should be directed to the support contact supplied with your subscription or deployment. The Help Desk explains the available support path.