Snapshot 96977

Document
Privacy policy
URL
https://b2b.lokdon.com/privacy-policy
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
browser
Size
25406 bytes
SHA-256 (raw)
a5d1598fe0a811b2969269c74f63ee4c581642ba64b46ee9132c8a4474da4646
SHA-256 (normalized text)
aa797d24c4ce40a2fff41946d866730ae68e71635990b4f814e6d52d80a49c86

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Back to LokDon|Privacy Policy
LokDon AISM · Data & Privacy
Privacy Policy
LokDon is built on the principle that your identity and data belong to you. This policy explains exactly what we collect, how we use it, and how you can remove yourself from our platform at any time.
Effective date: June 1, 2026 · Last updated: June 12, 2026
1. Who We Are
LokDon (operating as CyberLockX / LokDon AISM) provides a licensed AI Security Module delivering quantum-resistant cryptographic identity and communication infrastructure for enterprise AI systems and SaaS applications. Our principal office is located at 711 Saluda Ave, Columbia, SC 29205, USA.
For privacy matters, contact us at: privacy@lokdon.com.
2. What We Collect and Why
2.1 Identity Data
When you enroll in the LokDon platform, we collect your full name, email address, and a Universal Wallet Address (UWA) — a quantum-resistant cryptographic identity token generated for you during enrollment. Your UWA is bound to your device hardware fingerprint and is never transferable.
2.2 Device Binding Data
To prevent session hijacking and unauthorized access, LokDon binds your authenticated session to a device identifier (CM3 fingerprint). This is a hardware-level signal — not a tracking cookie — and is used solely for authentication continuity.
2.3 Encrypted Field Data (ECSMID)
Any sensitive form fields — including passwords, personal identifiers, and cryptographic credentials — are encrypted using ECSMID (Endpoint-to-Endpoint Cryptographic System for Cloud, Mobile, and IoT Devices) before they ever leave your browser. LokDon stores only the ciphertext. Plaintext personally identifiable information (PII) is never written to our database.
2.4 Support & Communication Data
When you submit a support ticket, we collect the content of your message, your email address, and your plan tier, in order to route and resolve your request. Replies sent by our agents are stored in our system and emailed to you via Resend (our email delivery provider).
2.5 Usage Data
We log API request timestamps, response codes, and SPC/SPU credit usage linked to your account. We do not sell this data, use it for advertising, or share it with third parties outside of what is necessary to operate the platform.
2.6 Payment Data
Payments are processed by Stripe. LokDon does not store payment card numbers. Stripe's privacy policy governs payment data: stripe.com/privacy.
3. How We Use Your Data
To authenticate you and establish a cryptographic identity session via UWA and DDNA.
To deliver the ECSMID-encrypted communication and conference services you subscribe to.
To process support tickets, route them to the correct agent, and send you email responses.
To deduct SPC/SPU credits for API usage associated with your account.
To send transactional emails (enrollment confirmations, trial approvals, support replies).
To detect and block malicious activity through our GHOST and IMMUNE AI security agents.
To comply with legal obligations.
We do not use your data for behavioral advertising, sell it to data brokers, or use it to train third-party AI models.
4. Data Sharing & Sub-Processors
LokDon shares your data only with the following sub-processors, strictly to operate the platform:
Service	Purpose	Data Shared
LokDon ECSMID API (RapidAPI)	Field encryption / decryption	Ciphertext only — never plaintext PII
Resend	Transactional email delivery	Email address, message body
Stripe	Payment processing	Billing details (card data not stored by us)
OpenAI	TIC report generation (admin use)	Anonymized threat intelligence summaries
Replit (hosting)	Infrastructure / server	All data in transit (TLS encrypted)
5. Data Retention
Active accounts: Data is retained for the duration of your enrollment plus 90 days after account closure.
Support tickets & replies: Retained for 2 years for audit and continuity purposes.
ECSMID ciphertext: Retained while your account is active. Deleted within 30 days of a verified opt-out request.
Payment records: Retained for 7 years as required by financial regulations.
Security logs (GHOST / IMMUNE): Retained for 180 days for threat-intelligence continuity, then deleted.
6. Your Rights & How to Opt Out
You have the right to withdraw from the LokDon program at any time — no questions asked.
When you opt out, we will:
Deactivate your UWA and invalidate all active sessions immediately.
Delete your ECSMID-encrypted credentials and sensitive identity fields immediately.
Remove your account from all active queues, pilot programs, and communications.
Retain only what is legally required (payment records, security logs per §5).
How to exercise your rights:
Portal opt-out (instant): Log into your Dashboard → Account tab → Close My Account. This immediately invalidates all sessions, clears your ECSMID credentials, and deactivates your UWA — no waiting period. A confirmation email is sent automatically.
Email opt-out: Send a request to privacy@lokdon.com from the email address associated with your account. Include your UWA or full name so we can locate your record.
Support ticket: Submit a ticket via the Support page with subject "Account deletion request". Our team will process it within 5 business days.
You also have the right to access a copy of your data, request corrections to inaccurate data, or file a complaint with your local data protection authority if you believe your rights have been violated.
7. Security Measures
LokDon's security architecture is designed so that a breach of our database does not expose your personal data in readable form:
ECSMID encryption (12,288-bit equivalent) is the sole encryption layer across the entire LokDon platform — covering all data in transit and at rest. This includes identity and enrollment fields, vault entries, conference and KQPC communications, and TEKPC-processed data. ECSMID ciphertext is what travels over the network between client and server, and what is stored in the database. Plaintext PII is never present in persistent storage.
Third-party API connections (OpenAI for report generation, Stripe for payment processing) use TLS 1.3 for transit — these external services do not support ECSMID. Data sent to them is limited to the minimum necessary and never includes ECSMID-sealed credentials or identity fields.
Split-Cipher (Transcendental Gate) — during the SIEVVE authentication handshake, the server produces an ECSMID-encrypted challenge (derived from cryptographic Intermediate Representations — IR material, not plaintext). That cipher is immediately split: Part A is sent to the client, Part B is held server-side in the DDNA session. Neither half alone is sufficient to reconstruct the cipher. The two halves are reunited in server memory for a single instant only when the client proves possession of Part A — then immediately discarded. No plaintext crosses this boundary at any point.
Device binding prevents stolen session tokens from being used on a different device.
GHOST agent monitors for anomalous access patterns in real time.
8. Cookies & Tracking
LokDon uses session cookies solely to maintain your authenticated state while you are logged in. We do not use tracking pixels, third-party analytics cookies (e.g., Google Analytics), or any form of cross-site behavioral tracking.
Third-party font delivery: This site loads fonts from Google Fonts (fonts.googleapis.com). This is a standard web font service — your browser makes a request to Google's servers to download the font files, which means Google receives your IP address as part of that request. Google Fonts does not set cookies or build behavioral profiles. We do not control Google's data practices for this request; for details, see Google's Privacy Policy. We plan to self-host fonts in a future release to eliminate this third-party connection entirely.
You may disable cookies in your browser settings, but doing so will prevent you from logging into the platform.
9. Changes to This Policy
We may update this Privacy Policy to reflect changes in our practices or legal requirements. When we do, we will update the "Last updated" date at the top of this page and, where the changes are material, notify enrolled principals by email at least 14 days before the changes take effect.
Continued use of the platform after the effective date constitutes acceptance of the updated policy. If you do not agree, you may opt out per Section 6 before the effective date.
10. Contact Us
For any privacy-related questions, data requests, or opt-out submissions:
Privacy: privacy@lokdon.com
Support: support@lokdon.com
Mail: LokDon / CyberLockX, 711 Saluda Ave, Columbia, SC 29205, USA
We aim to respond to all privacy requests within 5 business days.
View our Terms of Service →