Telion privacy notice

TELION PRIVACY NOTICE

Version: 2026-09-13

TELION LLC operates Telion. This notice describes information used for accounts,
licensing, purchases, support and the desktop features below. For privacy
questions or requests, contact management@telion.ltd or use the Telion contact
page at https://www.telion.ltd/contact.

Accounts and licensing

Telion processes account identifiers, email and profile information, organization
membership and roles, plan eligibility, purchase and entitlement records,
activated-device identity, security events, legal acceptance records and support
communications. These records support authentication, eligibility and license
enforcement, purchases, access management, abuse prevention and support.
Academic email verification does not establish every eligibility or authority
fact that a plan may require.

Direct accounts are for adults aged 18 or older, including students. Educational
and Academic Research access requires a verified account email whose domain ends
in .edu, including for each member of an academic group plan. This requirement
applies equally to Google sign-in and Telion email accounts. No separate
institution agreement is required. Accounts for minors are unavailable. Telion
does not use student data for behavioral advertising.

Local diagnostics and optional support sharing

Telion automatically creates local diagnostic reports when relevant errors or
operations occur. Creating a local report does not require support-sharing
consent and does not, by itself, upload the report. Local reports can contain
sanitized error text, study or node labels, operation details and environment
information. Sanitization reduces exposure but cannot guarantee that arbitrary
text never contains sensitive information.

The desktop keeps the newest 100 local diagnostic report files in its Diagnostics folder,
pruning older files when a report is recorded. This is a file-count limit, not a
time-based deletion schedule. Prepared support submissions are stored separately.

Remote support sharing requires the current sharing disclosure, review of the
report and an explicit Send Report action. An error alone does not send a report.
Submissions also require an authorized account and device and enabled remote
support. You can withdraw sharing consent to stop future submissions.

An ordinary submission contains selected diagnostic and environment metadata and
any description you enter. It excludes local diagnostic messages, tracebacks,
filesystem paths, model contents, geometry, meshes, expressions, credentials and
simulation results. Your description is sent as entered, subject to a length
limit. Review it for sensitive information.

Including model.py is a separate choice for each report. You can inspect the
exact source before sending. It may contain geometry, parameters, expressions,
material and physics settings, custom Python, local references, proprietary
information and replay data. Optional source is sent exactly as previewed,
without automatic redaction or secret scanning. Remove secrets and send only
material you are authorized to share.

Telion saves the prepared request locally before attempting an upload so retries
can use the same contents. It includes your description and any optional model
source. These local submission journals have no automatic age expiry or count
limit and can remain after an upload or withdrawal of sharing consent.

Diagnostic metadata and your description are recorded in a private GitHub support
issue. Optional model source is stored in private Vercel Blob storage and is
available through authenticated Telion administration; it is not pasted into the
GitHub issue. Telion maintainers may use reports and explicitly included source
for debugging, analysis and Telion product development.

Submitted model source is retained until a Telion administrator manually deletes
it. That deletion removes the stored model source while preserving diagnostic
and consent records, its hash and size, the GitHub issue and a deletion audit.
It does not remove the saved request from your desktop. Withdrawing consent does
not automatically delete earlier local or remote records. To request deletion,
contact Telion and include the support reference shown after submission.

Optional AI connections

AI connections are user-directed. Before connection, Telion identifies the
selected provider and the categories of information that may be sent. No
provider request is made before the versioned disclosure is accepted. Requests
may include messages, opened-model source and context, tool results, and material
you attach or authorize. The provider's terms and privacy practices apply
separately, including its retention practices. Withdrawing connection consent
stops future use; it does not delete historical provider data or local AI history.

Website advertising measurement

Optional Google Ads measurement on Telion's public website requires a separate
choice through Cookie preferences. The Google advertising tag stays unloaded
until you allow advertising cookies. Your choice is saved in a first-party
preference cookie and can be changed at any time. Browser Global Privacy Control
keeps optional advertising measurement disabled.

After you allow it, Google receives the public page address, browser and network
information, and advertising measurement data. A separate, query-free page can
measure a completed, live initial paid subscription purchase after Telion verifies
the signed-in purchaser's ownership and payment with Stripe. This shares only
the paid amount, currency and an opaque transaction reference with Google;
free checkouts, test payments and subscription renewals are excluded. The
reference prevents duplicate counting when the page is refreshed. Purchase
measurement requires a new explicit Cookie preferences choice; previous
visit-only permissions do not authorize it. It depends on returning to the
website and can be prevented by browser privacy controls or blocking software.
For advertising attribution,
Telion may supply Google advertising click identifiers (gclid, gbraid and wbraid)
and aggregate advertising source and campaign identifiers (gad_source and
gad_campaignid) from public landing-page links. These aggregate identifiers
describe the advertising source and campaign, rather than a Telion account.
Telion accepts only bounded identifier formats and excludes all other URL query
parameters, URL fragments, account or checkout identifiers, and desktop model
and support contents. The advertising tag is not loaded on sign-in, account,
checkout, activation or administration pages. Analytics storage and personalized
advertising remain disabled. Google does not receive the private receipt page,
account or checkout identifiers, email addresses, or desktop activity. A signed,
account-bound first-party measurement receipt is inaccessible to website scripts
and expires after five minutes. Purchase records remain in the account and
payment systems under their separate retention rules.

Rejecting advertising cookies prevents future tag loading and removes Google
advertising cookies accessible on Telion's website. If the tag is already loaded,
the website reloads the page to stop its activity. This does not erase information
previously sent to Google. Google's privacy practices apply separately:
https://policies.google.com/privacy.

Privacy requests

Use the contact details above to request access, correction or deletion of your
information, or to raise a privacy concern. Telion may need information to verify
the request and identify the relevant account or support submission. An expired
license or withdrawn feature consent does not itself delete account, purchase,
security or acceptance records.