Legal information
Privacy policy
This page explains the intended data practices of the current ServiceOps working prototype.
Last updated: 12 July 2026
1. Prototype status
ServiceOps is presently a local learning and working-prototype application. Before a public or commercial launch, the operator must publish verified business identity, contact, hosting, retention and jurisdiction details and obtain appropriate legal review.
2. Information processed
The application may process owner and employee account details; tenant membership and roles; customer names, phone numbers and email addresses; service-site addresses; installation and asset records; complaints, assignments and service-visit notes; confirmation details; and uploaded service attachments.
3. Why information is used
Information is used to authenticate users, isolate company workspaces, register serviced equipment, coordinate complaints and technician visits, maintain service history, secure public service links and operate and troubleshoot the application.
4. Tenant responsibility
Each company using a workspace controls the customer and service information it enters. Workspace owners are responsible for having an appropriate reason and any required notice or consent for collecting that information, inviting only authorized staff and keeping records accurate.
5. Sharing and service providers
The prototype does not sell personal information. A future hosted version may use infrastructure, database, file-storage, email, SMS or monitoring providers only as needed to operate the service. Production providers and cross-border processing details must be disclosed before launch.
6. Security
The application is designed around cookie authentication, role authorization, tenant-scoped queries, secure random public tokens and private attachment access. No system can guarantee absolute security, and production deployment requires operational controls, backups, key management, monitoring and incident response.
7. Retention and deletion
The prototype preserves operational history when records are deactivated. A production retention schedule and verified deletion/export workflow have not yet been finalized. Do not enter live customer data until the deployment operator has established these controls.
8. Cookies
ServiceOps uses essential authentication and security cookies. The prototype does not intentionally include advertising cookies or cross-site behavioral tracking.
9. Requests and questions
For access, correction or privacy questions about information in a workspace, contact that workspace’s owner or the person who provided access to this deployment. Verified operator contact details must be added before public launch.
10. Applicable privacy framework
An Indian production deployment may be subject to the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025, including provisions that commence on different dates. The deployment operator must assess the obligations that apply to its role and processing before launch. See the official Act and Rules.