Developer Terms

Last updated: 2026-02-27. These terms are provided for transparency and product governance and are not legal advice.

1. Definitions

  • LoginSign: the authentication service and Developer Portal.
  • Developer / You: the person or entity creating or operating an application.
  • Application: an OAuth client registered in the Developer Portal (including redirect URIs, website, icons, terms/privacy URLs).
  • End user: a person who authenticates or creates an account through your Application via LoginSign.
  • Credentials: any secrets, tokens, API keys, or client credentials issued for your Application.

2. Eligibility and account responsibility

You represent that you have the authority to accept these Developer Terms on behalf of yourself or your organization. You are responsible for all activity that occurs under your account and for maintaining appropriate access controls for your team.

3. Use of the service (license and scope)

Subject to these Developer Terms, LoginSign grants you a limited, non-exclusive, non-transferable, revocable right to use the Developer Portal and related APIs solely to integrate LoginSign authentication into your Application.

You may create one or more Applications. Each Application must have accurate metadata (name, website, redirect URIs, and—if you use custom links—valid Terms and Privacy Policy URLs).

4. Your obligations

  • Accuracy: Keep Application metadata accurate and up to date.
  • Security: Protect Credentials, use secure storage, and rotate secrets when necessary.
  • Compliance: Comply with applicable laws, including consumer protection and data protection laws.
  • User transparency: Provide your own Terms and Privacy Policy if your services process user data.
  • Support: Provide a reasonable channel for end-user support related to your Application.

5. Redirect URIs and security requirements

You must only use redirect URIs that you control and that are registered in the Developer Portal. The redirect URI used in OAuth requests must match a registered URI exactly.

  • HTTPS: Use HTTPS in production. Localhost HTTP is only for development.
  • No open redirects: Do not implement redirect handlers that allow arbitrary forwarding.
  • Incident response: If you suspect compromise, rotate Credentials immediately.

6. Prohibited use

You must not:

  • Misrepresent your identity, your Application, or your relationship with LoginSign.
  • Use LoginSign to facilitate phishing, malware, fraud, spam, or abusive behavior.
  • Attempt to bypass security controls, rate limits, authentication, or authorization.
  • Scrape, reverse engineer, or probe the service in a manner that harms stability or security.
  • Use data obtained via LoginSign for advertising targeting, resale, or purposes not authorized by the end user.

7. User data and privacy

LoginSign may provide your Application with user data in accordance with user consent and our policies. You must handle data in compliance with applicable law, minimize collection, and use it only for purposes the user expects and authorized.

8. Application icons and branding

You may upload icons for your Application. You must have the rights to use any content you upload and must not upload illegal, infringing, or deceptive content.

9. Availability and changes

LoginSign may change, suspend, or discontinue parts of the Developer Portal or APIs, enforce limits, or deprecate features.

10. Enforcement, suspension, and termination

We may suspend or revoke your Application or access if we reasonably believe you violated these terms, our general terms, or applicable law. On suspension, your Application may stop functioning for new authentications.

11. Intellectual property

You retain rights to your Application. LoginSign retains rights to its services, APIs, documentation, and branding.

12. Disclaimers and limitation of liability

The Developer Portal and APIs are provided on an “as is” and “as available” basis. To the maximum extent permitted by law, LoginSign disclaims warranties and is not liable for indirect, incidental, special, consequential, or punitive damages.

13. Contact

For legal and privacy questions, see Imprint or contact us via Contact.

Privacy Policy · Terms of Service · Imprint