LicenseSphere 360

Company registration in process. LicenseSphere 360 is in the process of being registered as a private limited company in India under the Companies Act, 2013. Registration is currently in process. Until it is complete, the service is operated by its founders on behalf of the company to be incorporated; once incorporated, the company will take over these policies and we will update this page and notify customers.

Privacy Policy

Last updated:

This Privacy Policy explains how LicenseSphere 360 ("LicenseSphere", "we", "us") collects, uses and protects personal data when you use LicenseSphere 360 and licensesphere360.com. It is intended to meet the notice requirements of the Digital Personal Data Protection Act, 2023 ("DPDP Act"), the Information Technology Act, 2000 ("IT Act") and the rules made under them. LicenseSphere 360 is in the process of being registered as a private limited company in India under the Companies Act, 2013. Registration is currently in process. Until it is complete, the service is operated by its founders on behalf of the company to be incorporated; once incorporated, the company will take over these policies and we will update this page and notify customers.

1. Our roles: Data Fiduciary and Data Processor

For account, billing-contact, website and support data about you and your administrators, we are the Data Fiduciary (we decide the purpose and means of processing). You are the Data Principal (the individual to whom the personal data relates).

For the data your organisation puts into or collects through the Service (licenses, vendors, user lists, device inventory and so on, "Customer Data"), your organisation is the Data Fiduciary and we are its Data Processor. We process Customer Data only on your instructions, as set out in the Terms, under a valid contract. On request we will enter into a data processing agreement with you.

Paddle.com Market Limited and its group companies ("Paddle") act as Merchant of Record and handle payment and checkout data under their own privacy policy (see section 6).

2. Data we collect

Depending on how you use the Service, we process:

  • Self-serve trial signup data: when you start a free trial, we collect your name and email address (from your Google sign-in or the email address you enter), the company name you enter, your IP address (kept for abuse prevention and cleared after 90 days), and a record of your acceptance of the Terms with its date. We use this to create your trial workspace and for security and abuse prevention, including enforcing the one-trial-per-email and per-business-domain limit.
  • Account and authentication data: name, work email, role, department, organisation (tenant) name and domain, and sign-in identifiers from our authentication provider (Firebase Authentication). We do not store your password in readable form.
  • Licence and vendor data you enter or import: software products, vendors, contracts, costs, renewal dates, seat allocations, compliance and savings records.
  • Device inventory from endpoint agents (if you deploy them): the list of installed software (name, version, publisher, install date), hostname, operating system, architecture, agent version, a machine ID (a random identifier created at enrollment) and, optionally, a user email. Agents check in hourly by default (an administrator can change this). Agents do not collect process activity, launch or last-run times, executable paths, file contents, keystrokes, browsing activity or SaaS usage. An agent is authorised by an IT administrator who creates a revocable, tenant-scoped agent key; keys are stored only as hashed values.
  • Integration data: if you connect third-party services (for example identity, collaboration or chat platforms), the credentials and connection settings, which are encrypted at rest, and the data you authorise us to read. For Google Workspace and Microsoft Entra / Microsoft 365 directory connections this is each user's last sign-in time and disabled state, pulled when an administrator runs a sync. Slack and Microsoft Teams incoming webhooks are used only to send alerts.
  • Audit and security logs: records of actions in the app, such as who changed what and when, plus IP address and request metadata used for security and rate limiting.
  • Billing data we receive from Paddle: customer and subscription identifiers, number of purchased units, status, billing dates, invoice references and refunds. We do not receive full card numbers.
  • Trial data choice: after you subscribe, the app asks you once whether to keep or clean up the data created during the trial. Cleanup permanently deletes licenses, assignments, devices and discovered software records; users, integrations, agent keys, invoices and the audit log are kept.
  • Support communications: messages you send to [email protected] or [email protected].
  • Technical and cookie data: see section 10.

3. Notice, consent and legitimate uses

This policy is our notice to you under the DPDP Act. It describes the personal data we process and why, how you can exercise your rights and make a complaint to us, and how to complain to the Data Protection Board of India.

We process personal data either (a) with your consent, which is free, specific, informed, unconditional and unambiguous, given by a clear affirmative action such as accepting these terms or ticking a box, and which you can withdraw at any time as easily as you gave it; or (b) for the "legitimate uses" the DPDP Act recognises, for example where you voluntarily provide data for a purpose and do not indicate that you withhold consent, to comply with Indian law or a court or authority order, or for employment-related purposes by your organisation. Withdrawing consent does not affect the lawfulness of processing done before withdrawal, but we may no longer be able to provide the Service.

Where your organisation is the Data Fiduciary for Customer Data, it is responsible for giving notice to, and obtaining consent from or relying on a legitimate use for, the individuals (such as employees) whose data it puts into the Service, including device users where endpoint agents are deployed.

4. How and why we use data

We use personal data only for specified purposes. We use it to:

  • provide, operate and secure the Service, including inventory, compliance analysis and notifications;
  • authenticate users and enforce roles and tenant isolation;
  • manage subscriptions, trials, billing status and refunds with Paddle, including using the email addresses of users and the hostnames of devices in your tenant to count the Managed Units used for billing;
  • provide support and communicate about the Service, security and changes to our terms;
  • detect abuse, prevent fraud and keep audit trails;
  • improve and maintain the Service;
  • comply with law and enforce our rights.

5. No sale of data and no AI training

We do not sell personal data and we do not use Customer Data to train artificial intelligence models. We collect only the personal data needed for the purposes above.

6. Payments and Paddle

Paddle is our Merchant of Record. When you buy, Paddle collects your payment details, billing name, address, email and tax information and processes them under its own privacy policy (https://www.paddle.com/legal/privacy). We receive only the information needed to manage your subscription, as listed above. Paddle may share limited data with payment processors, fraud-prevention and tax providers. Paddle collects and remits applicable taxes and issues your invoices.

7. Data Processors and recipients

We share personal data only with service providers (Data Processors) who need it to deliver the Service, under contracts requiring appropriate protection. Categories include:

  • cloud hosting and database infrastructure (Amazon Web Services);
  • authentication services (Google Firebase Authentication);
  • payment, tax and invoicing (Paddle, as described above);
  • email and customer-support tools;
  • monitoring, logging and security tooling;
  • integrations that you enable yourself;
  • professional advisers, and courts or authorities where we are legally required to disclose.

8. Where data is stored and retention

Our primary data is stored on Amazon Web Services in the AWS Asia Pacific (Mumbai) region (ap-south-1), in India.

We keep account data and Customer Data for as long as your tenant is active or as needed for the purpose it was collected. For trial workspaces that are never converted to a paid subscription, the trial data (licenses, assignments, devices, discovered software, vendors, alerts and compliance records) is permanently deleted 3 days after the trial ends; users, integrations and your account remain until you ask us to delete them. We will email the account administrators before deletion. After cancellation or termination, or once the purpose is served or you withdraw consent, we will delete or return your tenant data on request, unless we must keep it by law. Device inventory is replaced by each agent report and removed when a device is deleted. Audit logs and billing records are kept for as long as needed for security, accounting and legal requirements. Backups and logs are retained for a limited period and are overwritten or removed in the ordinary course.

9. Security and data breaches

We implement reasonable security safeguards to protect personal data, in line with section 43A of the IT Act and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, and the security safeguards required by the DPDP Act. These include HTTPS in transit, tenant-level data isolation, role-based access control, hashed agent keys, encrypted storage of integration secrets, signed and verified payment webhooks, security headers, CSRF and origin checks, rate limiting and audit logging. Section 72A of the IT Act penalises disclosure of personal information in breach of a lawful contract, and we handle data with that in mind.

No system is perfectly secure. If a personal data breach occurs, we will notify the Data Protection Board of India and affected Data Principals in the manner and within the time required by the DPDP Act and its rules, and will notify your organisation without undue delay where we act as its Data Processor.

10. Cookies and local storage

We use strictly necessary cookies, browser storage and authentication tokens to sign you in and keep your session secure, and local storage to remember preferences such as your colour theme. Paddle may set its own cookies or similar technologies on its checkout to process payments and prevent fraud. We do not use advertising cookies. If we add analytics or other non-essential cookies we will ask for your consent first. You can clear or block storage in your browser settings, though the Service may not work properly without the essential items.

11. Cross-border transfers

Our service providers, including Paddle and Firebase, may process personal data outside India. Under section 16 of the DPDP Act we may transfer personal data outside India except to any country or territory the Government of India restricts by notification. Where we do, we require the recipient to protect the data under contract and we remain responsible for it. Customers outside India may have local statutory rights that cannot be excluded.

12. Your rights as a Data Principal

Under the DPDP Act you have the right to:

  • access a summary of the personal data we process about you, the processing activities, and the other Data Fiduciaries and Data Processors we have shared it with;
  • correct inaccurate or misleading data, complete incomplete data and update it;
  • request erasure of your personal data once it is no longer needed for the purpose for which it was collected, unless we must keep it by law;
  • have your grievances redressed by us (see section 13);
  • nominate another individual who may exercise your rights if you die or become incapacitated;
  • withdraw consent at any time.

13. Grievance redressal and the Data Protection Board

To exercise your rights or raise a complaint, contact our Grievance Officer (see section 16). We will acknowledge within 48 hours and aim to respond to rights requests and grievances within one month, or any shorter period the law prescribes. We may need to verify your identity first. If your data is in a customer organisation's tenant, we may refer you to that organisation, which is the Data Fiduciary.

You should first use our grievance process. If you are not satisfied, or do not get a response in time, you may complain to the Data Protection Board of India as provided under the DPDP Act. You must also perform your duties as a Data Principal, including providing authentic information and not filing false or frivolous complaints.

14. Children

The Service is intended for businesses and adults aged 18 or over and is not directed to children. Under the DPDP Act a child is a person under 18, and processing a child's personal data requires verifiable parental or guardian consent. We do not knowingly collect personal data from anyone under 18, and we do not track or target children. If you believe a child has provided us data, contact us and we will delete it.

15. Changes to this policy

We may update this policy. We will post the new version with a new "last updated" date and notify you of material changes by email or in the app.

16. Contact: Grievance Officer

Grievance Officer, LicenseSphere 360, India (the officer's name and the registered office address will be published here once the company registration is complete). Email: [email protected]. Product support: [email protected].