Account and billing
Email and billing identifiers will be processed only after accounts and purchasing launch. Stripe payment details will not be stored by apps.sedaj.com.
Privacy by design
Less data.
Less risk.
The licensing server should know only what is needed for licensing, secure downloads, and audit—not the contents of a protected site.
Current statusAccounts, payments, and telemetry have not launched publicly
Planned categories
What the platform may process.
Every category has a purpose, minimum scope, retention class, and restricted access.
Licenses
A pseudonymous installation identifier, public installation key, product version, scope, and technical entitlement status.
Security audit
Action, time, pseudonymous actor, internal target, and a small allowlist of technical reason codes.
Downloads
Internal license and release IDs, an installation pseudonym, token hash, expiry, and use count.
Outside the boundary
What the licensing server does not need.
- ×Form contents
- ×Raw IP addresses in the licensing database
- ×WordPress users and passwords
- ×Cookies or authorization headers in audit records
- ×URLs containing sensitive query parameters
- ×Unlimited behavioral telemetry
Retention
Data should not remain forever.
Operational records have short lifetimes. Security audit data is pseudonymous. Billing records are retained only as legally required.
This is a technical privacy design, not a final legal notice.Before accounts and payments launch, the controller, legal bases, subprocessors, contact point, and final retention periods must be completed for the applicable law.