Privacy Policy

1. Overview

Field Capture Client (FCC) is a self-hosted mobile data collection platform. This policy explains what data the FCC server handles, how it is used, and what responsibilities rest with the organisation or individual deploying and operating the server.

2. Data Collected

The server receives and stores the following data submitted through the mobile app:

• Form field values (text, numbers, dates, selections)
• GPS coordinates captured during a session
• Photos, audio recordings, and other media files
• Digital signatures
• Barcode and QR code scan results
• Contact details entered by the user during capture
• Device sensor readings (accelerometer, barometer, compass, light)

All data is scoped to an organisation and user identifier as supplied by the app at submission time. The server does not collect device identifiers, IP addresses for tracking, or any data beyond what workflows explicitly request.

3. How Data Is Used

Submitted data is used solely to fulfil the purpose of the workflow it was collected under. Specifically:

• Stored on the server for retrieval by authorised users of the same organisation
• Exported on request (PDF, XLSX, CSV) by the organisation administrator
• Forwarded to a configured submission target if the workflow specifies one

Data is not sold, shared with third parties, or used for advertising. It is not processed for profiling or automated decision-making by Warky Devs.

4. Submission Targets — Operator Responsibility

FCC workflows may include a submission target — an external URL to which completed session data is forwarded (REST endpoint, webhook, n8n, or email). The operator who authors or imports a workflow is solely responsible for:

• Ensuring the target endpoint is authorised to receive the data being sent
• Ensuring end-users are informed that their submission will be forwarded to that target
• The security, retention, and processing practices of the receiving system
• Compliance with applicable data protection laws (e.g. POPIA, GDPR) for data sent to that target

Warky Devs has no visibility into, and accepts no liability for, data processed by third-party submission targets configured by operators.

5. Data Retention

Data is retained on the server for as long as the operator maintains their deployment. There is no automatic expiry. Operators are responsible for deleting submissions and media when retention obligations require it. A future admin interface will provide bulk-delete functionality.

6. Data Security

All API endpoints that accept or serve submission data require bearer token authentication. Operators are responsible for keeping their token confidential, using HTTPS in production, and securing the host environment. Warky Devs provides the software; the operator controls the infrastructure.

7. Self-Hosted Deployments

FCC is designed to be self-hosted. When you run your own instance, you are the data controller. Warky Devs is the software provider only and does not have access to data stored on your server.

8. Contact

For questions about this policy or the FCC platform, contact hein.puth@gmail.com.