FoodABCs API Terms

You must be legally able to enter into this agreement and, if you use the API services for an organization, authorized to bind that organization. “Partner” and “you” mean that organization and its authorized users.

These terms incorporate the FoodABCs Privacy Policy. If a signed order form, data-processing agreement, business associate agreement, or other written agreement conflicts with these terms, the signed agreement controls for that conflict.

You must provide accurate account information, keep it current, and limit account access to authorized personnel. You are responsible for activity under your partner account and applications.

API keys, client secrets, access tokens, refresh tokens, and other credentials are confidential. Do not publish them, place secret credentials in client-side code, or share them outside your organization except with service providers that are bound to protect them. Notify FoodABCs promptly if credentials may have been lost, exposed, or misused.

New accounts begin with sandbox access and the standard Tier 1 partner level. Live access, additional scopes, Tier 2 features, analytics, exports, and individual-level access may require review, approval, user authorization, and additional compliance or commercial terms.

FoodABCs may apply rate limits, spend limits, scopes, environment restrictions, data-suppression rules, and other safeguards. Approval for one application or use case does not approve a different application or use case.

You may use the API services to integrate published FoodABCs functionality into your approved products and workflows, manage your integration, and access information made available to your account under your tier, scopes, user permissions, and written agreements.

You must follow the documentation, use credentials only for their assigned application and environment, provide legally required notices and choices to users, and comply with applicable laws and contractual obligations.

You may not, and may not allow others to:

• access data, endpoints, scopes, tiers, or environments you are not authorized to use;
• bypass authentication, consent, rate limits, security controls, usage metering, or data-suppression rules;
• use the API services for unlawful, deceptive, discriminatory, harmful, emergency, or high-risk medical decision-making;
• sell, license, publish, or disclose user-level data except as expressly authorized by the user, FoodABCs, and applicable law;
• use FoodABCs data or outputs to train or improve a general-purpose model without prior written permission;
• introduce malware, probe for vulnerabilities without authorization, interfere with the services, or attempt to derive source code or nonpublic systems; or
• misrepresent your relationship with FoodABCs or use FoodABCs names, logos, or marks without permission.

You may access individual-level information only when the relevant user has granted the required permission, the user is properly associated with your application or organization, and your account has the required tier, scope, role, and compliance approval.

You may use user information only for the authorized purpose presented to the user. You must honor revocations, deletions, access limits, and other user choices, and you may not combine FoodABCs data with other information in a way that defeats a user’s permissions or reasonably creates an unauthorized profile.

Aggregated, cohort, or de-identified information may be subject to minimum-group, suppression, export, and re-identification restrictions. You may not attempt to identify an individual from that information.

FoodABCs is a wellness platform and does not provide medical advice, diagnosis, treatment, emergency monitoring, or clinical decision support. API results and automated outputs may be incomplete or inaccurate and must be independently reviewed for your use case.

If your use involves protected health information, regulated healthcare activities, consumer health data, or another legally protected category, you are responsible for determining which laws and agreements apply. Do not send or access protected health information through a regulated workflow until all required written agreements, including any required business associate agreement or similar addendum, are in effect.

You must maintain administrative, technical, and organizational safeguards appropriate to the sensitivity of the information and the risks of your integration. At a minimum, use encrypted transport, protect credentials, restrict access, keep software current, monitor for misuse, and retain data only as long as needed for an authorized purpose.

Notify FoodABCs without undue delay of any actual or suspected unauthorized access, disclosure, loss, alteration, or misuse involving the API services, credentials, or FoodABCs information. You must cooperate with reasonable investigation, containment, remediation, and legally required notice activities.

Usage is metered at the published endpoint and tier rates. Sandbox and live calls are billable at the same rates unless FoodABCs expressly marks an account or event as exempt. You are responsible for charges generated by your credentials and applications, applicable taxes, and any fees stated in the developer portal, pricing page, order form, or other written agreement.

By completing payment setup, you authorize FoodABCs and its payment processor to save your card and automatically charge variable, usage-based invoices after each UTC calendar month and when you request final account closure. Current usage is an estimate until invoiced. Very small amounts that cannot be charged may carry forward to a later invoice; a qualifying final amount below the processor minimum may be written off during closure.

A failed payment does not immediately stop API access. FoodABCs ordinarily provides a fourteen-day grace period while payment retries and notices continue, after which unresolved billing may suspend credentials while usage and payment obligations already incurred remain due. Ownership changes require billing to be current. Account deletion requires all reported usage, issued invoices, processor balances, and final closeout usage to be settled.

FoodABCs may change pricing prospectively with notice when required. Billing disputes and refund requests must be submitted promptly with enough detail to investigate; undisputed amounts remain payable. If billing has not yet been activated for your account, no statement on the site creates a promise of free or perpetual access.

FoodABCs may update, add, deprecate, or remove features, endpoints, documentation, limits, and technical requirements. When practical, we will provide reasonable notice of material breaking changes, but emergency security, legal, or reliability changes may take effect sooner.

Unless a separate written agreement states otherwise, the API services are provided without a service-level commitment and may be unavailable, interrupted, or changed.

FoodABCs and its licensors retain all rights in the API services, documentation, technology, and FoodABCs marks. These terms grant only the limited right to use the API services as described here and do not transfer ownership.

You retain rights in your application and information you lawfully provide. If you provide feedback, you allow FoodABCs to use it without restriction or payment, provided we do not identify you publicly without permission.

FoodABCs may suspend or restrict access to protect users, security, service reliability, legal compliance, billing integrity, or other partners, or if we reasonably believe you violated these terms. We may terminate access for a material breach or as allowed by a separate agreement.

When access ends, you must stop using the API services and credentials and delete FoodABCs information you are no longer authorized or legally required to retain. Provisions that by their nature should survive termination will survive, including confidentiality, ownership, payment, disclaimers, liability limits, and indemnification.

To the maximum extent permitted by law, the API services are provided “as is” and “as available.” FoodABCs disclaims implied warranties, including merchantability, fitness for a particular purpose, noninfringement, and warranties arising from course of dealing or usage of trade.

To the maximum extent permitted by law, neither party will be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenues, data, goodwill, or business interruption. FoodABCs’ aggregate liability arising from the API services will not exceed the amount you paid or owed for the API services during the twelve months before the event giving rise to the claim.

You will defend and indemnify FoodABCs and its affiliates, personnel, and service providers against third-party claims, losses, liabilities, and reasonable costs arising from your application, your content, your violation of these terms, your misuse of the API services, or your infringement or violation of another person’s rights, except to the extent caused by FoodABCs’ own unlawful conduct.

FoodABCs may update these terms. We will update the effective date and provide additional notice when required. Continued use after revised terms take effect means you accept the revised terms; if you do not agree, you must stop using the API services.

You may not assign this agreement without FoodABCs’ written consent, except as part of a merger or sale of substantially all relevant assets. FoodABCs may assign it as part of a reorganization, financing, merger, or sale. If any provision is unenforceable, the remaining provisions remain in effect. A failure to enforce a provision is not a waiver.

Any governing-law, venue, dispute-resolution, notice, or order-of-precedence terms in a signed agreement or order form apply. If none exists, applicable law determines those matters.

Questions about these terms or the API services can be sent to support@goldminds.education.