AltioraBIM Public Beta Privacy Notice
Version: altiorabim-public-beta-privacy-beta4-20261012-v4 Version date: 12 October 2026.
Controller and contact
Vladimir Ribentsov, an individual developer using the AltioraSky brand, determines how personal data is used for the AltioraBIM Public Beta. AltioraSky is not described as a registered company. For a privacy question or request, email contact@altiorasky.com with “Privacy request” in the subject. We will verify that a request concerns your own account before disclosing or changing its records.
What we collect
Registration requires your full name and email address. You may choose to give an organization, professional role, country, Revit version, approximate family-library size and intended use case. We record the versions and time associated with acceptance of the Evaluation Terms and acknowledgement of this Notice. These are separate required choices: accepting the Terms forms the evaluation agreement; acknowledging this Notice confirms that you have been shown the information. The acknowledgement is not consent for every processing purpose, and there is no marketing opt-in in this release.
Email verification and recovery use short-lived links. The service holds registration and license identifiers; keyed digests of email addresses, activation codes, verification and recovery tokens, and download grants; and the times and status needed to administer them. First activation records a hash derived from the local installation identifier, the original activation time, a 30-day expiry and a signed entitlement copy. This is an installation identifier, not a claim of hardware-level identity. Protected download sessions hold a browser public key, nonces, authorizations and response-start events. A response-start record does not prove that you saved or installed the file. Security controls use request counts and keyed digests derived from IP addresses; these digests may still be personal data.
The add-in stores its signed entitlement in protected local Windows state so it can validate the trial offline. The account and activation information held by the online service is separate from that local copy.
If you submit the Public Beta feedback form, Netlify receives the name and registration email you enter, product and Revit versions, workflow description and comments. The email supports manual, provisional matching with a registration; the form does not authenticate you or automatically decide complimentary-license eligibility. A separate support email may contain whatever you choose to send. Do not send an activation code, confidential project material, proprietary RFA files or another person's information unless support specifically and securely requests it. The licensing flow does not automatically upload RFA contents or diagnostic logs.
Purposes and lawful bases
| Purpose | Data used | GDPR basis |
|---|---|---|
| Register, verify email, issue a code, authorize a protected download, activate and provide the fixed trial, and handle requested recovery | Required profile and account, code, license, installation and transaction records; transactional email | Article 6(1)(b): performance of the requested evaluation agreement or steps requested before it |
| Record Terms acceptance and Privacy Notice acknowledgement and maintain evidence of what was shown | Version identifiers and time | Article 6(1)(b) for the Terms record; Article 6(1)(f) for the limited notice/accountability record |
| Protect accounts, downloads and the service against abuse or misuse | Turnstile result, rate-window digests, request counts, session nonces and relevant audit | Article 6(1)(f): security and fraud-prevention interests |
| Understand professional workflows from optional profile details and voluntary feedback, and respond to that feedback | Optional fields, feedback and correspondence | Article 6(1)(f): improve the product and respond to voluntary feedback, subject to the right to object |
| Resolve a request about a current license or account | The minimum account and correspondence data needed | Article 6(1)(b) where needed to deliver support under the evaluation; otherwise Article 6(1)(f) for handling a voluntary enquiry |
| Meet a specific binding legal duty, if one applies | Only the records that duty requires | Article 6(1)(c), assessed for that duty rather than used as a general basis |
Providing required registration details is necessary for account access. Optional profile details and feedback can be omitted without preventing registration. We do not send marketing email or make solely automated complimentary-license decisions. Where legitimate interests apply, you may object; we will assess the request under applicable law.
Service providers and transfers
Cloudflare hosts the Worker, D1 registration and licensing database, private R2 installer storage and Turnstile. Resend delivers transactional verification and recovery email and must receive the recipient address and message link. Netlify hosts the public website and receives its contact and feedback forms. Purelymail receives messages sent to the contact mailbox. These providers may use infrastructure, staff or subprocessors outside the EEA. An EEUR hint for the D1 database does not mean all related processing stays in the EEA. The providers publish data-processing terms, subprocessor information and international-transfer arrangements, including Standard Contractual Clauses where applicable. Contact us to request information about safeguards relevant to your data.
The Beta Ready browser flow temporarily uses session storage to display the issued code and then clears it. A non-extractable browser signing key is kept in IndexedDB for the protected download session; losing it may require email recovery. Neither feature makes a compromised browser or email account safe.
Retention
The following limits apply to records under our control. Separate provider logs and backups are explained below.
| Record | Limit |
|---|---|
| Unverified registration without an issued code | 30 days after the last verification attempt |
| Expired verification and recovery challenge data | Deleted within 7 days after expiry |
| Rate-limit digests | Deleted within 48 hours after the relevant window ends |
| Verified account without an activation, including its unused code | 90 days after the last meaningful activity |
| Activated account, license and installation-binding records | Up to 12 calendar months after the original 30-day trial expiry |
| Session, nonce, grant and download audit records for an activated account | Up to 90 days after trial expiry, subject to earlier account deletion; for a never-activated account, they leave with the account |
| Feedback and support correspondence under our control | 12 months after the last relevant interaction unless a documented exception applies |
“Meaningful activity” includes successful verification, recovery redemption or protected download activity; merely requesting a recovery email does not extend the inactive-account period. Deleting an unused code makes it unusable. Once account history has lawfully been deleted, the service does not retain a permanent marker to stop the same email from registering again. A new registration may therefore start a new evaluation. Deleting a server account cannot necessarily disable a previously issued offline entitlement before its original expiry.
The D1 cleanup selects unverified registrations after 29 days, inactive verified accounts after 89 days, activated accounts 24 hours before the 12-calendar-month limit, and session and download audit after 89 days. It selects expired verification and recovery challenges after six days and rate-limit records after 24 hours from the end of their window. These earlier eligibility points leave time to correct missed runs before the maximum limits. Used tokens become invalid immediately through the verification or recovery flow. Cleanup is scheduled hourly and monitored for failures and backlog. A failed or missed run does not extend the limits above.
These limits do not establish the deletion schedule for separate Cloudflare service logs or D1 Time Travel, Resend mail and logs, Netlify service logs or forms backups, the receiving mailbox, or separately exported local backups. Those copies have provider-specific controls and periods; erasure from active D1 tables is not instant erasure from all such copies. Feedback and support correspondence require a separate manual deletion process. A documented legal obligation, security investigation or claim may require a limited exception, with its basis and duration recorded.
Your rights
You may ask to access, correct or delete your data, restrict its use, object where legitimate interests are relied on, or receive portable data where applicable. Rights may have legal limits. Send requests to contact@altiorasky.com with “Privacy request” in the subject. We will verify control of the relevant account with proportionate evidence; do not send an activation code or identity document by default. We will explain any remaining data and applicable exception. You may complain to your competent data protection authority.
Changes
Material changes to this Notice will receive a new version identifier. The registration system records the current version identifiers and an acceptance/acknowledgement time, but does not keep an independent full history of every later acceptance event. We will provide the updated information before asking for a new acknowledgement when required.