Privacy-first customer data handling
This notice explains, in plain language, what information the TemplateJar Invoice Pro sales platform may collect and why. It is a technical/commercial template and should be reviewed and adapted to your actual business, jurisdiction and legal obligations before launch.
1. Information we collect
Depending on the action, we may collect name, email address, optional phone number, order/payment identifiers, license acceptance records, support messages and account activity. Payment card or UPI credentials are handled by the payment provider and should not be entered into our forms.
2. Why we use it
We use information to process purchases, deliver source code, create customer accounts, provide support, manage licenses, prevent abuse, maintain security and comply with applicable accounting or legal requirements.
3. Data minimisation
The contact form does not require a phone number. We avoid storing raw IP addresses in support requests; a keyed hash is used for abuse-rate limiting. Passwords are stored as one-way password hashes. Permanent plaintext passwords are not emailed.
4. Payment data
Payment processing is performed by the configured payment gateway. The sales application stores order and payment identifiers needed for reconciliation, not payment-card secrets.
5. Security
The platform uses prepared SQL statements, CSRF protection, secure session cookies, password hashing, rate limiting, security headers, protected download tokens and access-controlled admin pages. No security measure can guarantee absolute security.
6. Retention
Configure an appropriate retention period in your operational policy. Support and account data should be retained only as long as reasonably necessary for the stated purpose, contractual needs, accounting obligations or applicable law.
7. Your requests
Customers may request access, correction, deletion or withdrawal of consent where applicable. Accounting/order records may need to be retained where a legal or contractual obligation requires it. Requests should be reviewed before action is taken.
8. Children & sensitive data
The service is intended for business users. Do not submit health, financial-account credentials, passwords, OTPs, government identity numbers or other sensitive information through the contact form unless specifically required and lawfully handled.
9. Contact
For privacy questions, use the Contact page. The final published notice should identify the actual legal entity, contact details, applicable jurisdiction and any appointed privacy/data-protection contact.