1. Core terms
We store email, a password hash, subscription and pack state, payment and limit-debit history, support requests and files voluntarily attached to them, the extension installation public key, session details (client type, time, shortened User-Agent and country), and a limited security log. The extension locally processes the Zero Block opened by the user and the layout package. During normal imports, layouts, text, images, layer names and clipboard contents are not sent to the TildEka server; images are uploaded directly to the user’s own Tilda media storage.
2. Processing and access
This data supports sign-in, access checks, plan recovery, support, replay protection and abuse prevention. The server receives only aggregate import data: Frame count, screen widths, media count and a technical trigger. Robokassa and Paddle receive email and order details; TildEka never receives or stores card credentials. For USDT, the recipient, amount and public TXID are stored, while the transaction itself is public on BSC.
3. Management
The web session token is stored in a protected cookie. The extension session token stays in extension-local storage and is device-key-bound. Sessions can be revoked in the account. Account deletion anonymizes personal fields, revokes sessions and requests cancellation of supported renewals; mandatory financial records may be retained where required by law.
4. Contact and limitations
TildEka’s use and transfer of information received through the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for the disclosed import function, account operation, security and support; it is not sold, used for personalized advertising or creditworthiness, or made available for human reading except with the user’s explicit consent or when required for support, security or law.
5. Provider details
For data requests, create a support ticket or email kismet7313@gmail.com. Never send passwords, API keys, card data or seed phrases.