1. Introduction
IN AEC Tools respects the privacy of users of IN AEC CCTV. This Privacy Policy explains what information may be processed when you use IN AEC CCTV, why that information is processed, how it is protected, how long it may be retained, and how you can contact us regarding privacy questions or requests.
IN AEC CCTV is a desktop add-in for Autodesk Revit. Licensing is designed as a separate commercial-security layer and is not intended to process the contents of customer Revit models.
Contact:
IN AEC Tools
Email: in.aec.tools@gmail.com
Website: https://in-aec-tools-website.pages.dev
2. Licensing Architecture and Service Transition
IN AEC CCTV currently uses, or may continue to use during a controlled migration period, Keygen Cloud for license activation and validation.
IN AEC Tools is developing a standalone multi-product licensing platform using Supabase. The new platform is designed to become the server-authoritative licensing backend for IN AEC CCTV and future IN AEC Tools products.
During migration:
- Keygen may remain available until the controlled migration is formally closed.
- A valid customer entitlement is not intended to be cancelled merely because the backend platform changes.
- Licensing data may be migrated or recreated under controlled administrative procedures.
- The desktop client will not contain Supabase service-role credentials or a private signing key.
This policy will be updated if the deployed production data-processing model materially changes.
3. Information We Process
To provide, secure, and manage software licensing, IN AEC CCTV may process the following categories of information.
3.1 License Information
This may include:
- license identifier;
- protected or hashed representation of the license key;
- license status;
- product entitlement;
- plan identifier;
- license start and expiration times;
- trial or paid-subscription state;
- configured machine/device limit;
- activation and validation results;
- suspension or revocation state.
The server is intended to be authoritative for license status, trial eligibility, expiry, and machine limits.
3.2 Device Information
IN AEC CCTV may generate a device fingerprint derived from a stable Windows machine identifier such as Windows MachineGuid.
The intended policy is:
- raw Windows MachineGuid is used only as an input to derive a device identity;
- raw Windows MachineGuid should not be stored as plain server-side licensing data;
- a derived or hashed device fingerprint may be transmitted and stored;
- the device fingerprint may be versioned so future fingerprint methods can coexist.
The device fingerprint may be used to:
- bind a license to an authorized device;
- enforce machine limits;
- prevent unauthorized sharing;
- prevent repeated trial abuse;
- support legitimate device-transfer requests;
- investigate licensing or security issues.
A hashed device fingerprint remains privacy-relevant because it may act as a persistent device identifier.
3.3 Technical Licensing Information
The licensing system may process:
- product code;
- application version;
- platform information;
- activation time;
- validation time;
- request identifiers;
- authorization result codes;
- device-binding state;
- short-lived lease identifiers;
- limited technical information needed to diagnose licensing failures.
4. Revit Project and Engineering Data
The licensing system is not designed to upload or process customer Revit model contents for licensing purposes.
IN AEC Tools does not intend to collect through the licensing system:
- Revit model geometry;
- project drawings;
- camera layouts;
- schedules;
- linked-model contents;
- engineering calculations;
- report contents;
- customer project files.
Licensing state is not intended to be stored in:
- Revit parameters;
- Extensible Storage;
- DataStorage;
- linked documents;
- customer project settings.
If a future cloud feature requires additional engineering or project information, the relevant privacy disclosure will be updated before that processing is introduced.
5. Local Storage
IN AEC CCTV may store licensing information locally on the user's Windows account.
The current and planned Windows client architecture may use Windows Data Protection API (DPAPI), CurrentUser scope, to protect local licensing state.
Local protected data may include:
- license key;
- product identifier;
- short-lived authorization lease;
- temporary licensing state;
- schema/version information.
The local store must not contain:
- Supabase service-role credentials;
- database passwords;
- private lease-signing keys;
- administrative credentials.
6. Server-Authoritative Trial and Expiry
The approved licensing policy is:
- Trial duration: 15 days.
- Trial start: first successful server-authorized trial activation.
- Downloading, installing, or merely opening the application does not start the trial.
- Standard trial machine limit: 1 device.
- The client clock must not create or extend the trial.
- Paid-license expiry is also server-authoritative.
- A plan or license name is not itself expiry authority.
The exact production behavior must be implemented and verified before it is represented as fully automated in customer-facing product claims.
7. Short-Lived Authorization
The planned Supabase licensing architecture uses short-lived signed authorization leases.
The client may verify a signed lease using a public verification key.
Private signing keys remain server-side.
The initial conservative lease target is approximately 15 minutes.
If the system cannot safely prove authorization, protected functionality is intended to fail closed.
8. Internet Connection
Internet access may be required for:
- trial activation;
- paid license activation;
- periodic license validation;
- lease renewal;
- recovery from an expired or invalid local authorization state.
If the licensing service cannot safely verify authorization, protected product functionality may be unavailable until validation succeeds.
9. Licensing Service Providers
IN AEC Tools may use third-party infrastructure providers to operate licensing.
During the migration period, this may include:
- Keygen for current or legacy license validation;
- Supabase infrastructure for the new IN AEC Licensing Platform.
Third-party providers may process limited licensing information only as necessary to provide the licensing service.
10. Purpose of Processing
Licensing-related information may be processed to:
- issue and activate trial licenses;
- issue and validate paid licenses;
- enforce server-controlled expiry;
- enforce device limits;
- maintain explicit machine binding;
- prevent repeated trial abuse;
- suspend or revoke unauthorized licenses;
- manage legitimate license recovery;
- diagnose licensing failures;
- maintain audit records;
- provide customer support;
- protect the licensing system against fraud and misuse.
11. Trial Information
IN AEC CCTV is intended to offer a 15-day free trial to eligible new users.
The standard approved trial policy is:
- trial begins on first successful server-authorized activation;
- standard trial machine limit is one device;
- reinstalling the application does not automatically grant a new trial;
- no payment card is intended to be required to begin the standard trial;
- the trial does not automatically convert to paid billing;
- the trial does not automatically renew.
A device fingerprint and, where applicable, an email address or another limited identity signal may be used to determine whether a trial has already been claimed.
12. Paid Subscription Route
Paid subscriptions are sold externally through IN AEC Tools.
Autodesk Marketplace is intended to be used for product discovery and/or trial distribution and is not the payment processor under the current commercial policy.
Current prices, plan limits, purchase instructions, renewal terms, cancellation terms, and applicable refund terms should be shown on the official IN AEC Tools purchase route.
13. Data Sharing
IN AEC Tools does not sell personal information.
Licensing information may be shared only when reasonably necessary with:
- licensing infrastructure providers;
- hosting/database providers;
- security or operational providers;
- payment providers if later introduced for external sales;
- legal or regulatory authorities when required by law.
14. Data Retention
Licensing and audit information may be retained for as long as reasonably necessary to:
- provide active licenses and subscriptions;
- enforce trial and device restrictions;
- process support requests;
- investigate fraud, abuse, or security incidents;
- maintain required operational and legal records.
Where information is no longer required, IN AEC Tools may delete, anonymize, or aggregate it.
Specific retention periods may vary by data type and deployed licensing infrastructure.
15. Security
IN AEC Tools uses reasonable technical and organizational measures designed to protect licensing information.
The approved architecture includes principles such as:
- HTTPS communication;
- server-authoritative licensing decisions;
- no direct desktop-client database access;
- no Supabase service-role key in customer software;
- no private signing key in customer software;
- DPAPI-protected local storage;
- derived device identifiers;
- explicit machine binding;
- short-lived signed leases;
- auditable server mutations;
- fail-closed behavior;
- separation of licensing from Revit model data.
16. User Rights and Requests
Depending on applicable law, you may request information about licensing-related personal data associated with you and may request correction or deletion where legally and technically appropriate.
Contact:
in.aec.tools@gmail.com
Please provide enough information to identify the relevant license or account without sending passwords or unnecessary confidential project information.
IN AEC Tools may need to verify the requester before processing a privacy request.
17. Trial-Abuse and Security Records
Certain limited records may need to be retained even after a deletion request where reasonably necessary to:
- prevent repeated free-trial abuse;
- detect fraud;
- protect the licensing platform;
- satisfy legal obligations.
Where possible, these records should be minimized and retained in hashed or non-plain-text form.
18. Changes to This Policy
This Privacy Policy may be updated when:
- the Supabase licensing platform enters production;
- Keygen migration is completed;
- new service providers are introduced;
- new data categories are processed;
- payment or customer-portal functionality is added;
- marketplace or legal requirements change.
19. Contact
IN AEC Tools
Email: in.aec.tools@gmail.com
Website: https://in-aec-tools-website.pages.dev
END OF PRIVACY POLICY