Developers

Developer Policy

Rules for consent, security and permitted API use.

Effective
5 August 2026
Version
2026.08
Operator
Glemad Inc.

Build for people

  • Make the application’s identity and purpose obvious.
  • Explain what data is requested before consent.
  • Offer meaningful functionality independent of unnecessary permissions.
  • Respect revocation, deletion and account disconnection promptly.

Prohibited uses

  • Surveillance, unlawful discrimination, eligibility scoring or sensitive-trait profiling.
  • Scraping, credential harvesting, spam or engagement manipulation.
  • Re-identifying aggregate or de-identified data.
  • Transferring data to data brokers or using it to train unrelated models without express authorization.

Data minimization

Collect the minimum fields, use the shortest practical retention period, restrict employee access and encrypt sensitive data in transit and at rest.

User control

Provide accessible ways to view, correct, export and delete data received from Nabtap. A person who disconnects your app should not have to contact support to stop future access.

Changes to this document

We may update this document to reflect changes to Nabtap, the law or the way we protect the community. When a change is material, we will provide notice appropriate to its significance and request fresh acceptance where required.

Contact

Questions about this document can be sent through the Nabtap Contact Centre. Choose the topic that best matches your request so it reaches the appropriate team at Glemad Inc.