Privacy Policy

DJS Solutions, Medavakkam, Chennai, India, is responsible for the personal data described here. Contact us at support@expla.me.

• Account details — your email address, your name if you give one, and a cryptographic hash of your password. We never store the password itself. If you sign in with Google we receive your email address, name and profile picture from Google.
• What you create — the prompts you write, the images you upload, and the video, images and music generated from them.
• Billing records — what you paid, when, and the identifier Razorpay gives the payment. We never see or store your card details; they are handled entirely by Razorpay.
• Operational logs — technical records of requests and errors, used to keep the service working.

Model providers. To generate anything, your prompt and any images you supply are sent to the provider you choose — Google or ByteDance. They process it under their own terms. We send only what the generation needs; we do not send your email address or billing details.

Razorpay. Payments are processed by Razorpay, which collects your payment details directly.

Amazon Web Services. The application runs on AWS and your files are stored there.

We do not sell your data, and we do not use it to train models.

• Generated files — 7 days without a storage plan, then permanently deleted. Indefinitely while a plan is active.
• Account and billing records — for as long as you have an account, and afterwards where tax and accounting law requires it.
• Prompts and generation history — kept with your account so you can see what you paid for, even after the file itself is deleted.

You can ask for a copy of your data, ask us to correct it, or ask us to delete your account and its contents. Write to support@expla.me from the address on the account. We respond within thirty days.

Deleting your account removes your generated files and personal details. We keep the minimum billing records the law requires us to keep. Anything already sent to a model provider is subject to that provider's own retention.

We set a cookie to keep you signed in, and one to protect forms against cross-site request forgery. Both are necessary for the service to work. We do not use advertising or tracking cookies.

Passwords are hashed with scrypt. Traffic is encrypted in transit and files are encrypted at rest. Access to production data is limited to those who need it. No system is perfectly secure, and we will tell you promptly if a breach affects your data.