Developer Agreement

This Agreement applies to any User who creates a Developer profile, registers an OAuth application, installs the Pixel, runs a Promote campaign, operates a Cast station via developer tools, configures or uses TrueFans Creator (white-label artist portals, signed portal links, and related console or API tooling), or otherwise uses the Developer Portal or our APIs (collectively, "Developer Products").

• You may create one or more developer profiles. Each profile has its own API keys, prepaid balance, rate-limit ceiling, network rules (CORS allowed origins and IP whitelist), and usage logs.
• Profiles may belong to an organization. Organization members may have differing roles and permissions; the organization owner is responsible for member access and for actions taken under any profile in the organization.
• You will keep contact and billing information current. Notices we send to the email on file are deemed received.
• You will not share, sublicense, or resell access to your profiles without our written permission.

• API keys, OAuth client secrets, and webhook signing secrets are confidential credentials. You are responsible for keeping them secret and for all activity under your credentials.
• Do not embed secret credentials in client-side code, mobile apps, public repositories, or third-party tools that may expose them.
• Rotate credentials promptly upon any suspected compromise and notify us at [email protected].
• We may rotate, revoke, or invalidate keys at any time for security, abuse prevention, or operational reasons.

• Developer Products are paid for from a prepaid balance held per developer profile. You top up your balance through Everyware; balance is denominated in U.S. dollars.
• Balances are a ledger entry, not a deposit. They are not held in trust, are not FDIC-insured, do not earn interest, and may not be transferred between unaffiliated profiles without our consent.
• Prepaid balances are non-refundable, except where required by law or as a goodwill gesture at our sole discretion (for example, in response to extended outages of paid products you were unable to use).
• Unused balance may expire after extended inactivity (typically 24 months from the last top-up or usage event), subject to applicable unclaimed-property law. We will provide reasonable notice before expiration.
• Usage debits balance based on our measurements. Our logs are presumptively correct absent manifest error.
• You may enable budget alerts and auto-reload. You authorize the corresponding charges to your payment method on file.

The following pricing applies as of the effective date and may be updated prospectively:

Pricing is subject to change with reasonable advance notice for material increases. Promote clicks may be invalidated and credited back at our sole discretion under our invalid-traffic policy. Calls that fail server-side validation, partner errors, or rate-limited responses are generally not charged.

• Default rate limits per developer profile are approximately 60 requests/minute, 1,000 requests/hour, and 10,000 requests/day. Specific endpoints may have lower abuse-protection caps (for example, Pixel collect per IP per site per minute).
• We may adjust rate limits up or down per profile or per endpoint to manage abuse, capacity, or commercial fit.
• Requests that fail rate-limit checks return HTTP 429 and are generally not charged.
• Burst protections, bot-detection signals, and origin checks may throttle or block requests that appear automated or abusive even if within the headline limits.

In addition to the Acceptable Use Policy, you must not:

• Use APIs to bulk-create fake accounts, fake artists, fake venues, fake shows, or fake engagement;
• Scrape personal data, donor lists, fan rosters, or aggregated analytics beyond what your access scopes and product addenda permit;
• Evade CORS allowed-origins lists, IP whitelists, allowed-domain checks on the Pixel, or other access controls;
• Use APIs to discriminate based on protected classes (housing, employment, credit), facilitate stalking, or enable surveillance of vulnerable populations;
• Use APIs to redistribute, sell, sublicense, or build a competing service from TrueFans CONNECT™ data;
• Conduct benchmarking, competitive analysis, or public performance testing without our prior written consent;
• Cache or store API responses beyond stated TTLs or beyond what is reasonably necessary for the user-facing feature you are building.

• Data accessed via the Developer Products may include aggregated platform analytics, listings, public profiles, and — through OAuth or Pixel — end-user personal data scoped by consent. You will only use data for the purpose disclosed to and authorized by the user and consistent with these Terms.
• You are a data controller for personal data you receive under OAuth or via the Pixel Identify/Resolve APIs. You will publish a privacy notice, honor user rights (access, correction, deletion, opt-out where applicable), respect deletion-and-revocation signals from us, and comply with GDPR, UK-GDPR, CCPA/CPRA, and similar laws.
• You will not re-identify users who have opted out, exported, or deleted their data.
• You will not combine TrueFans data with data acquired through unlawful means or for prohibited purposes.
• If you are required by law to disclose TrueFans data, you will give us prompt notice (where lawful) so we can seek protective relief.

Some Developer Products are labeled beta, preview, experimental, or "coming soon." They are provided AS-IS, may change or be removed at any time, are not covered by any SLA, and may have additional limits. We may add, modify, or discontinue Developer Products with notice. Existing prepaid balance remains usable on remaining Developer Products at the rates then in effect.

Non-public information you receive about the Service (including API endpoints not publicly documented, performance metrics, roadmap, pricing tests, and aggregated platform statistics) is our confidential information. You will use it only to use the Service and will not disclose it to third parties. Standard exceptions (already known, independently developed, publicly available without breach, lawfully received, compelled by law) apply.

You will use commercially reasonable measures to protect credentials and user data. Report suspected vulnerabilities to [email protected] and give us a reasonable opportunity to remediate before public disclosure. Do not test the security of the Service against accounts or data you do not own without our written authorization.

When you use these products, the corresponding addendum also applies:

• OAuth Integrator Addendum
• Pixel & Visitor Tracking Addendum
• Promote (Advertising) Addendum
• Enterprise Search & AI Seat Addendum
• Cast Station Addendum

TrueFans Creator. When you use TrueFans Creator, this Developer Agreement governs your access to the Creator Console, Creator API, branding configuration, artist onboarding, and signed portal links. Artists you onboard remain Creators under the Creator Agreement. Referral or revenue-share amounts (if any) are as disclosed in the product or your commercial arrangement with us; we may change those economics prospectively on reasonable notice.

• Standard support is provided by email and through the Developer Portal; response times are best-effort.
• We do not offer service-level commitments (uptime, throughput, latency) for non-Enterprise plans. Aspirational status pages and incident notices are informational only.
• We may give you notice through the Developer Portal, email, or our changelog. You will give us notice at [email protected].

• We may suspend or revoke keys, throttle traffic, freeze balance, and terminate access at any time, with or without notice, for suspected violation of these Terms, AUP, security risk, capacity concerns, or non-payment.
• On termination for cause (including AUP violation, fraud, abuse, or repeated security incidents), we may forfeit remaining balance in whole or in part.
• On termination without cause, we will refund unused balance pro rata to the extent practical, less any amounts owed.
• Provisions that by their nature should survive — including pricing for usage incurred before termination, indemnification, confidentiality, IP, disclaimers, liability cap, and dispute resolution — will survive.

In addition to Section 24 of the Master Terms, you will defend, indemnify, and hold Company harmless from claims arising out of: (a) your use of the Developer Products; (b) your handling of end-user data, including any privacy, marketing-compliance, or security claim; (c) your products, apps, and Cast stations and their interactions with end users; and (d) any act or omission by your employees, contractors, organization members, or end users you permitted access to your profile.

If you engage freelancers, agencies, or contractors to build on our APIs, you are responsible for their compliance and will ensure written agreements assign IP in your integrations to you and clarify they are independent contractors without authority to bind TrueFans CONNECT™. Your liability to Company and dispute resolution with Company are subject to Sections 23, 26, and 27 of the Master Terms (including the twelve-month liability cap and binding arbitration).