Responsible Use Policy

This policy explains how to use FildraAI services responsibly, including our website, mobile apps, APIs, FieldGuide, FieldState, FieldVision, FieldAudio, fieldmap, media search, and related tools.

Core Principle

FildraAI provides informational, analytical, translation, and workflow support. Our services help users think, document, and decide more carefully, but they do not replace human judgment, professional advice, emergency services, product labels, laws, or regulatory requirements.

Last updated: 2026

1. Services Covered by This Policy

These guidelines apply whenever you access or use FildraAI products, whether through the website, mobile applications, APIs, integrations, playgrounds, or internal tools made available to you.

Apps and Web Services

FieldGuide, FieldState, account pages, dashboards, playgrounds, support forms, and website features.

APIs and Developer Access

API keys, quotas, image diagnosis endpoints, translation endpoints, media search, and integrations.

AI and Analysis Tools

FieldVision image analysis, FieldAudio transcription and translation, fieldmap, summaries, recommendations, and generated outputs.

Security and Platform Integrity

Login systems, usage limits, anti-abuse monitoring, payment/credit access, storage, and service reliability controls.

2. How to Use FildraAI Responsibly

Use Outputs as Decision Support

Treat AI outputs, translations, predictions, and summaries as support for your review. They may be incomplete, uncertain, outdated, or wrong. You are responsible for checking important outputs before acting on them.

  • Review generated answers before using them in operational, financial, safety, or customer-facing decisions.
  • Provide accurate context, such as crop, location, season, language, image quality, and relevant constraints.
  • Do not rely on FildraAI as an emergency system or as the only source for high-risk decisions.
  • Use the service in a way that respects other users, local communities, and applicable laws.
  • Report outputs that appear unsafe, misleading, discriminatory, or inconsistent with local reality.

Service-Specific Notes

  • FieldGuide and FieldState: Use guidance and farm memory as planning support. Verify important actions with local expertise, records, labels, and regulations.
  • FieldVision: Image diagnosis depends on image quality, crop coverage, lighting, symptoms, and model limitations. Confirm uncertain results before treatment.
  • FieldAudio: Transcription and translation may be imperfect, especially with accents, noise, dialects, mixed languages, or technical terms. Review important translations.
  • fieldmap and location tools: Maps, weather context, and spatial outputs are decision-support information and may not reflect real-time conditions or legal boundaries.
  • APIs: Use API keys only for authorized applications and within your plan, quota, scope, and security responsibilities.

3. Human Review and High-Risk Decisions

FildraAI is designed to support decisions, not make final decisions on your behalf. Higher-risk uses require stronger human review, local validation, and where appropriate, qualified professional advice.

Keep a Human in the Loop

Review important AI outputs before using them in decisions that affect crops, livestock, finances, compliance, safety, or other people.

Not for Emergencies

Do not rely on FildraAI for emergency response, poisoning, contamination, life-threatening events, or urgent legal/regulatory actions.

Follow Applicable Law

When FildraAI output conflicts with laws, product labels, contracts, certification rules, or official guidance, those sources take priority.

Keep Records

Keep your own records of important actions, assumptions, images, diagnoses, and decisions. Do not rely only on generated summaries.

4. Inputs, Uploads, and Data Hygiene

The quality and safety of FildraAI outputs depend heavily on what users submit. Use care when uploading, recording, typing, or syncing information.

  • Provide accurate context: Include relevant crop, location, language, season, symptoms, image angle, and management details where useful.
  • Use clear uploads: Blurry images, noisy audio, incomplete records, or wrong location context may reduce output quality.
  • Avoid sensitive personal data: Do not submit government ID numbers, passwords, banking credentials, private medical information, or other unnecessary sensitive data.
  • Respect permissions: Do not upload images, audio, documents, locations, or records that you do not have the right to use or share. Specifically: do not upload images you found online, scraped, or downloaded from another product unless you own the copyright or have an explicit licence; do not upload someone else’s voice recording unless they have given you clear, informed consent to record and share it; do not upload copyrighted material (book pages, news photos, music, paid datasets) belonging to a third party. Accounts that repeatedly upload infringing or non-consensual media may be suspended or terminated.
  • Be careful with people in media: Avoid uploading identifiable people, private conversations, children, or bystanders unless you have appropriate permission.
  • Voice recordings need consent: When you use FieldAudio to record speech, you are responsible for confirming that everyone whose voice is captured has knowingly agreed to be recorded for this purpose. Some jurisdictions require all-parties consent; others only one party. Know which applies to where you are. We never use your recordings to train voice-cloning or speaker-recognition models, but local recording-consent law applies to you regardless of what we do with the audio.
  • Image copyright matters: FieldVision is designed for photographs you take of your own fields, crops, livestock, and equipment. If you submit images you did not take, you must have a written licence or other clear permission to use them in this product. Submitting someone else’s copyrighted image can expose you to a takedown notice, a copyright claim, or account suspension.

5. Fair Use, API Access, and Platform Integrity

We provide FildraAI services to support legitimate product, research, agricultural, translation, and operational workflows. To maintain service quality and protect our systems, users must access the platform responsibly.

5.1 Acceptable Use

  • Using FildraAI tools for normal account, app, website, research, translation, diagnosis, mapping, or workflow support.
  • Using APIs within your authorized keys, scopes, quotas, and plan limits.
  • Uploading reasonable files, images, audio, prompts, and records that you have the right to submit.
  • Sharing outputs within your organization or project where permitted by your plan and applicable law.

5.2 Prohibited Activities

These Activities May Result in Account Suspension

The following activities violate our policies and may result in restricted access, suspension, termination, or other action:

  • Unauthorized Automated Access: Using bots, scrapers, crawlers, scripts, or automation to access services without written permission.
  • Data Harvesting: Systematically extracting content, outputs, model behavior, knowledge base data, translations, media, or platform information.
  • Excessive or Abusive Requests: Sending requests that exceed plan limits, degrade reliability, bypass quotas, or resemble denial-of-service activity.
  • Reverse Engineering: Attempting to extract, replicate, probe, or reverse-engineer models, prompts, training data, infrastructure, security controls, or algorithms.
  • Unauthorized Resale or Redistribution: Reselling, sublicensing, republishing, or redistributing FildraAI services, outputs, API access, or content without permission.
  • Credential and Access Abuse: Sharing login credentials, leaking API keys, bypassing access controls, impersonating others, or using another user's account.
  • Illegal, Harmful, or Rights-Violating Use: Using services to violate laws, infringe rights, deceive others, harass people, or process content you are not authorized to use.
  • Security Testing Without Permission: Scanning, penetration testing, vulnerability probing, load testing, or stress testing FildraAI systems without written authorization.
  • Third-Party Personal Data Without Consent: Submitting personal data of other people (including photographs of identifiable persons) without their informed consent.
  • Prompt Injection or Jailbreak Attempts: Crafting inputs designed to override model instructions, bypass safety filters, extract system prompts, or coerce the AI into producing prohibited content.
  • Regulatory or Biosecurity Violations: Using FildraAI to generate or apply content that violates South African or your local agricultural, biosecurity, pesticide, livestock, or food-safety regulations.

5.3 Rate Limits & Usage Monitoring

We may use rate limits, quotas, plan scopes, logging, and automated abuse detection to protect service quality:

  • Requests per minute, hour, day, or billing cycle based on plan and endpoint type.
  • File size, upload frequency, audio length, media processing, and storage limits.
  • API scopes that limit which services a key may call.
  • Automated detection of abnormal usage, scraping, key leakage, or bot-like behavior.
Automated Detection

Our systems may automatically block suspicious patterns such as rapid-fire requests, systematic extraction, unusual access patterns, failed authentication spikes, or bot-like behavior. If legitimate use triggers protection, contact support.

6. Content Ownership and Output Use

6.1 Your Inputs and Data

You retain ownership of information, images, audio, text, records, and other content you submit, subject to any rights held by others. By using our services, you grant FildraAI the permissions needed to:

  • Process your inputs to provide services, outputs, storage, syncing, translation, analysis, and support.
  • Operate, secure, debug, and improve our services as described in our Privacy Policy and Terms.
  • Use aggregated, de-identified operational metadata (request counts, latency, error rates, feature usage) for reliability and non-AI service improvement. We do not use the content you upload — photos, voice recordings, prompts, FieldState records — to train, fine-tune, or build our AI models. Our crop-diagnosis models are trained on publicly available agricultural datasets and on data we have separately licensed for that purpose.

6.2 FildraAI Services, Content, and Technology

FildraAI services, interfaces, models, prompts, knowledge bases, workflows, source code, documentation, branding, and methodologies are owned by FildraAI or its licensors. You may not:

  • Copy, modify, resell, sublicense, or create derivative works from our technology or service content without permission.
  • Extract or harvest knowledge bases, model behavior, prompts, training data, or proprietary workflows.
  • Use FildraAI outputs or access patterns to train, benchmark, or build competing systems without permission.
  • Remove notices, hide attribution, or misrepresent FildraAI outputs as independently verified professional advice.

6.3 Generated Outputs

You may use generated outputs for your authorized personal, farm, research, internal business, or operational purposes, but you acknowledge that:

  • Outputs may be incomplete, uncertain, outdated, or incorrect.
  • Similar or identical outputs may be generated for other users with similar inputs.
  • You should not present outputs as guaranteed, certified, professional, legal, medical, financial, or regulatory advice.
  • You are responsible for reviewing outputs before relying on or sharing them.

7. Emergency and High-Risk Situations

Do Not Rely Solely on FildraAI in Emergencies

FildraAI is not an emergency response system. For emergencies, life-threatening events, poisoning, contamination, security incidents, or urgent legal/regulatory issues, contact appropriate local authorities, emergency services, qualified professionals, or official support channels immediately.

Seek professional or official help immediately for situations including:

  • Medical, veterinary, poisoning, contamination, or life-threatening situations.
  • Regulatory, quarantine, legal, certification, or movement-restriction decisions.
  • Major financial, contractual, employment, or safety decisions.
  • Security incidents, suspected account compromise, leaked API keys, or unauthorized access.
  • Critical operational failures where delay may cause serious harm or loss.

8. Enforcement and Consequences

8.1 Violation Handling

We may investigate and act on violations of this policy, our Terms, security requirements, or applicable law. Depending on severity, we may:

  • Issue warnings or request corrective action for minor issues.
  • Rate limit, restrict, revoke, or rotate API keys and access tokens.
  • Temporarily suspend features, accounts, workspaces, or integrations during investigation.
  • Terminate accounts for serious, repeated, abusive, illegal, or harmful violations.
  • Preserve evidence, seek legal remedies, or report illegal activity to appropriate authorities.

8.2 Appeals

If you believe an enforcement action was made in error, you may contact us with:

  • The account, workspace, API key, or email address involved.
  • A clear explanation of the activity and why you believe the action was incorrect.
  • Any steps you have taken to prevent future issues, such as securing credentials or adjusting traffic patterns.

9. Help Us Improve Responsible Use

Responsible use is something we build together. Your feedback helps us improve safety, reliability, accessibility, and clarity across FildraAI services:

  • Report outputs that appear unsafe, inaccurate, misleading, or inconsistent with local reality.
  • Tell us when translations, transcriptions, or summaries fail important meaning.
  • Report confusing UI flows, missing warnings, or unclear consent/permission behavior.
  • Notify us if you believe your account or API key has been compromised.
  • Suggest improvements to documentation, warnings, service limits, or accessibility.
Questions About Responsible Use?

We are happy to discuss how to integrate FildraAI into your workflows safely and transparently. Contact our team.