WalletCoreWalletCore
HomeAboutFeaturesSecurityCareersPressFAQContact
Log inCreate wallet

© 2026 CryptoWallet

TermsPrivacyCookies
CompareGuidesIntegrationsAssetsChangelogRoadmapStatusAUPDeveloper TermsDPABDTC DisclosuresPrint All TermsSub‑processorsRetentionPrivacy TransparencyPrint All PrivacyWhitepaperExplorer

Developer Terms

Rules for using our APIs, SDKs, and developer tools. Keep users safe, respect rate limits, and be transparent.

Create walletLog in
Last updated: 2026-01-15
On this page
OverviewAPI keys & rate limitsSecurity & dataBrand & attributionCompliance & user consentMonetization & feesFair use & cachingData residencySecurity controls checklistReviews & SLAsRevocation & terminationContact

Overview

These Developer Terms govern your use of WalletCore APIs, SDKs, libraries, and sample code. They supplement the global Terms.

API keys & rate limits

Keep keys confidential, rotate them regularly, and scope them to least privilege. Do not share keys publicly or attempt to bypass rate limits. We may adjust or revoke limits to protect the platform.

Security & data

Secure user data at rest and in transit. Do not collect more data than necessary. If you suffer a breach affecting users, promptly notify your users and applicable authorities as required by law, and inform us if our systems are implicated.

Brand & attribution

Use our brand assets only as permitted. Do not imply endorsement. Provide clear attribution or “Powered by WalletCore” where required by documentation.

Compliance & user consent

Follow applicable laws and obtain meaningful user consent for data collection. Publish a privacy notice. Honor user requests and platform settings.

Monetization & fees

We may charge for certain APIs. Fees and billing terms will be disclosed where applicable. You are responsible for taxes and for notifying your users about any fees you charge.

Fair use & caching

Respect published quotas and do not degrade service for others. Cache results only within documented TTLs; do not persist sensitive data longer than necessary. Batch requests where feasible and use backoff on errors.

Data residency

Some datasets may be regionally constrained. Do not export or store data outside allowed regions where residency applies. Use region‑scoped endpoints and storage per documentation.

Security controls checklist

  • Use OAuth or signed requests; rotate credentials and least‑privilege scopes.
  • Encrypt in transit; store secrets in a vault; never in client apps.
  • Implement rate limiting, input validation, and audit logging.
  • Provide user‑visible privacy notices and consent UIs where required.

Reviews & SLAs

We may review apps for compliance and safety prior to granting elevated quotas or marketplace listing. Service levels, support response times, and deprecation schedules are documented in our status and developer portals and may change with notice.

Revocation & termination

We may revoke API access that creates risk, violates these terms, or harms users. We may provide notice and remediation guidance where feasible.

Contact

For developer matters, open a ticket via the support center with your app ID and logs.