Privacy Policy

1. Who this policy applies to

This policy applies to:

People who create and use DevPayr accounts (developers, designers, agencies, startups, teams).
People who visit our website, documentation, or marketing pages.
People who contact us for support, sales, or partnership enquiries.

Your own clients and end-users (the people who use the software you protect with DevPayr) are primarily your responsibility. DevPayr may process limited technical data about them (for example, license checks, domains, or IP metadata), but you remain the main “controller” of that relationship.

2. Information we collect

We only collect information we actually need to run DevPayr, improve it, and keep it secure. Broadly, this falls into a few buckets:

a) Account & contact information

When you create an account or contact us, we may collect:

Name, email address, password (hashed), and profile details.
Company name, role, and other optional info you choose to share.
Communication preferences and related settings.

b) Billing & payment information

For paid plans, our payment providers may collect:

Billing address and country.
Partial payment details (e.g. last digits of a card) as allowed by them.
Transaction history for your DevPayr subscriptions.

We do not store full card numbers ourselves. That is handled by our payment partners.

c) Usage & technical data

When you visit our site or use the dashboard, we may log:

IP address, browser type/version, operating system, and device type.
Pages viewed, time spent, clicks, and general navigation patterns.
Basic diagnostic data when errors occur.

d) License & integration data

When DevPayr is integrated into your app or site and performs checks, we may process:

License keys, token IDs, and related project references.
Domains, subdomains, or IP metadata used during license validation.
Environment details (e.g. “production”, “staging”) where you configure them.
Simple request logs for security, debugging, and audit trails.

We do not need or want full copies of your application data, customer content, or databases. DevPayr is focused on licensing and access control, not your core business data.

e) Support & communication data

When you reach out to us via email, livechat, or forms, we collect:

Your contact details and message content.
Any attachments or screenshots you choose to share.
Ticket metadata (timestamps, status, who handled it, etc.).

3. How we use your information

We use the information we collect for a few clear purposes:

To provide the service: Create and manage your account, run license checks, send API responses, and render the dashboard.
To keep things secure: Detect suspicious patterns, prevent abuse or fraud, and protect DevPayr and its users from attacks.
To improve DevPayr: Understand which features are used, where users get stuck, and what we should fix or build next.
To communicate with you: Respond to support requests, send service updates, and let you know about important changes in terms, privacy, or platform behaviour.
To manage billing: Process payments, send invoices, handle plan changes, and respond to billing-related questions.
To meet legal requirements: Keep certain records, respond to lawful requests, and comply with regulations that apply to us.

If we ever want to use your data for a purpose that is meaningfully different from what is described here, we will either ask for your consent or make it very clear what is changing.

4. Legal bases (where applicable)

Different laws use different language, but in simple terms, we rely on a few main bases to process your data:

Contract: We process data that is necessary to provide DevPayr under our Terms of Use (for example, account, billing, and license checks).
Legitimate interest: We process data to improve our service, keep systems secure, and understand how DevPayr is used, in ways that do not override your privacy rights.
Consent: For certain communications or optional tracking, we may rely on your explicit consent. You can withdraw this where applicable.
Legal obligation: We may process or retain some information to comply with applicable laws, regulations, or lawful requests.

5. Cookies & similar technologies

We use cookies and similar technologies on our website and dashboard. These may include:

Essential cookies: Needed for login sessions, security, and basic site features.
Preference cookies: For things like theme selection (light/dark) and language.
Analytics cookies: To understand general usage patterns and improve performance.

You can usually control cookies through your browser settings (for example, blocking certain types or clearing them). Be aware that blocking essential cookies may cause parts of DevPayr to stop working properly.

6. When we share your data

We do not sell your personal data. We only share it in a few situations:

Service providers: With trusted vendors who help us run DevPayr (for example, hosting, payment processing, logging, analytics, email delivery). They only get the data they need to do their job, and they are bound by confidentiality and data protection obligations.
Legal or safety reasons: If we are required by law, court order, or a valid legal process, or if it is necessary to protect our rights, users, or the public.
Business transfers: If DevPayr or Kopium LLC is involved in a merger, acquisition, or sale of assets, data may be part of that process. If that happens, we will take steps to ensure your data remains protected and let you know where appropriate.

Outside of these situations, your data stays between you, us, and the specific services you choose to integrate with DevPayr.

7. How long we keep your data

We keep your data only for as long as we genuinely need it for the purposes in this policy, or as long as the law requires.

Account data: Kept while you have an active account. Some data may be kept for a period after closure for legal, billing, or audit reasons.
Billing records: Kept for the period required by tax and accounting laws.
License & API logs: Kept for a reasonable period to help with debugging, security investigations, and fraud prevention.
Support conversations: Kept so we can see history, understand context, and improve our support and product.

When data is no longer needed, we will delete it or anonymise it so it can no longer be linked back to you.

8. How we protect your data

We take security seriously and use a mix of technical and organisational measures to protect your data, such as:

Transport encryption (HTTPS) for data in transit.
Access controls and authentication for internal tools.
Hashed passwords and limited access to sensitive data.
Security-minded coding practices and monitoring.

That said, no online system is ever completely risk-free. We encourage you to:

Use strong, unique passwords and enable 2FA where possible.
Rotate keys regularly and remove unused keys or projects.
Limit who in your organisation has access to production credentials.

If you suspect a security issue that involves DevPayr, please contact us quickly at security@devpayr.com .

9. Your choices & rights

Depending on where you live, you may have specific legal rights around your personal data. In general, we try to honour the following for all users where reasonable:

Access: You can request a copy of the personal data we hold about you.
Correction: You can ask us to correct information that is inaccurate or incomplete.
Deletion: You can ask us to delete certain data, subject to legal or contractual limits.
Restriction or objection: You may be able to ask us to limit or stop certain uses of your data, where the law gives you that right.
Consent withdrawal: If we rely on consent for certain processing, you can withdraw it at any time (for example, unsubscribing from certain emails).

To exercise any of these rights, you can contact us at privacy@devpayr.com . We may need to verify your identity before acting on your request.

10. International data transfers

DevPayr is operated by Kopium LLC (a U.S.-registered company), but we may use service providers and infrastructure located in other countries. This means your data may be transferred to, stored in, or processed in places outside your home country.

Regardless of where processing happens, we aim to ensure your data is protected in line with this policy, through contracts, access controls, and reasonable security safeguards.

11. Children & age limits

DevPayr is not designed for children and is intended for adults and organisations working on software and digital products. We do not knowingly collect personal data from children under the age where they can legally consent to such services in their country.

If you believe a child has created an account or shared data with us without proper consent, please contact us at privacy@devpayr.com so we can review and take appropriate action.

12. Third-party services & links

DevPayr may integrate with or link to other services (for example, payment processors, analytics, or developer tools). Those services have their own privacy policies and terms, which we do not control.

When you use those services, you are doing so under their rules. We recommend that you read them carefully, especially if you are sending or syncing any personal data.

13. Changes to this Privacy Policy

We may update this Privacy Policy as DevPayr evolves or as legal requirements change. When we make important changes, we will try to notify you via email, an in-app message, or a clear notice on the site.

The “Last updated” date at the top of this page tells you when it was last changed. If you keep using DevPayr after an updated version is posted, it means you accept the new version.

14. How to contact us

If you have questions, concerns, or complaints about this Privacy Policy or how we handle your data, please reach out. We’d rather you ask than stay unsure.

General support: support@devpayr.com
Privacy questions: privacy@devpayr.com
Abuse or misuse reports: abuse@devpayr.com

When you write to us, including relevant details (like your account email, project ID, or screenshot) will help us respond faster and more accurately.