SwathMap Data Processing Addendum

Effective Date: October 15, 2026

This Data Processing Addendum ("DPA") is part of the SwathMap Terms of Service (the "Agreement") between Agri Flight Logs LLC ("AFL") and the customer ("Customer"). It applies automatically to every customer. Customers who use SwathMap inside the Agri Flight Logs or ApplicatorView apps are covered by those apps' terms instead, and customers who use it through a Partner App are covered by AFL's agreement with that app's operator (Agreement section 2.3).

1. Definitions

2. Scope and roles

2.1 AFL processes Customer Data on Customer's behalf to provide the Service.

2.2 For Personal Information, Customer is the "business" or "controller", and AFL is the "service provider" or "processor".

2.3 AFL handles all Customer Data as Customer's confidential information under this DPA, whether or not any of it is Personal Information.

3. Instructions

3.1 AFL processes Customer Data only:

• (a) for the business purposes in section 4;
• (b) on Customer's documented instructions, including those given through the Service's settings and functions, such as sharing a map, sending it to a Partner App, or turning model training off;
• (c) as the law requires, with notice to Customer unless the law forbids it.

3.2 AFL will tell Customer if it believes an instruction breaks Data Protection Law.

4. Business purposes

5. California service-provider terms

These apply to the extent the CCPA applies to Customer.

5.1 What AFL won't do. AFL will not:

• (a) sell or share Personal Information;
• (b) retain, use or disclose it for any purpose other than the business purposes in section 4, including any other commercial purpose;
• (c) retain, use or disclose it outside the direct business relationship between AFL and Customer, except as the CCPA regulations allow for improving AFL's own services;
• (d) combine it with personal information AFL receives from or on behalf of anyone else, or collects from its own interactions with individuals, except as the CCPA regulations allow.

5.2 Compliance and notice.

• AFL will comply with the CCPA's obligations that apply to it, and give Personal Information the level of privacy protection the CCPA requires.
• AFL will notify Customer within 10 business days if it determines it can no longer meet these obligations.

5.3 Customer's oversight. Customer may take reasonable and appropriate steps to ensure AFL uses Personal Information consistently with Customer's obligations. On notice, Customer may stop and remediate unauthorized use.

5.4 Certification. AFL certifies that it understands and will comply with this section.

6. People

6.1 AFL limits access to Customer Data to personnel who need it for the purposes in section 4.

7. Subprocessors

7.1 Current list. Customer authorizes the Subprocessors in Annex C.

7.2 AFL's duties. AFL has a written contract with each Subprocessor requiring at least the protection Data Protection Law requires, with confidentiality and security terms appropriate to the data, and remains responsible for its Subprocessors.

7.3 New Subprocessors. AFL gives at least 30 days' notice of a new Subprocessor, by email.

7.4 Objections.

• Customer may object on reasonable data-protection grounds within that period.
• If AFL can't reasonably accommodate the objection, Customer may end the affected Service, with a refund of unused prepaid fees (Agreement section 4.5).

8. Security

8.1 AFL maintains the measures in Annex B.

8.2 AFL may update them, but not in a way that materially reduces the protection of Customer Data.

9. Security Incidents

9.1 Notice. AFL notifies Customer without undue delay, and within 72 hours after confirming a Security Incident that affects Customer's data, or sooner where the law requires.

9.2 What the notice says, as far as known: what happened; the data involved; the likely consequences; the steps taken. AFL updates Customer as it learns more.

9.3 Cooperation and decisions.

• AFL cooperates with Customer's response.
• Customer decides on notices to individuals or regulators about its data, and AFL helps.
• A notice under this section is not an admission of fault.

10. Assistance

10.1 Individuals' requests. AFL helps Customer respond to requests from individuals (to access, delete or correct data), through the Service's functions or on request.

10.2 Requests sent to AFL. AFL passes on requests it receives directly.

10.3 Assessments. AFL gives reasonable help with Customer's privacy or security assessments.

11. Deletion and return

11.1 Export. Customer can export its maps, drawings and exports at any time while its account is open, including the 30 days after its subscription ends. Original photos can't be exported once deleted (Agreement section 10.1).

11.2 Deletion. AFL deletes Customer Data on the schedule in Agreement section 10, or on Customer's request:

• photos 72 hours after the map is done;
• maps 30 days after the subscription ends;
• support copies when the case closes.

AFL keeps only the minimal map records described there, and training copies under Agreement section 5.3. Database backups are overwritten within 7 days.

11.3 Certificate. On request, AFL confirms deletion in writing.

12. Audits

12.1 Questionnaires and summaries. Once a year, on request, AFL will answer a reasonable written security questionnaire and share summaries of relevant security reviews.

12.2 On-site audits happen only where a law or regulator requires one, with reasonable notice, at Customer's cost and under confidentiality.

13. Location

13.1 Customer Data is stored and processed in the United States. Map tiles may be delivered through Cloudflare's global network.

13.2 AFL gives 30 days' notice before moving storage or processing to another country.

14. Liability and precedence

14.1 This DPA is subject to the Agreement's limitations of liability.

14.2 For Customer Data, this DPA prevails over the rest of the Agreement.

14.3 It lasts as long as AFL processes Customer Data.

Annex A: Processing details

Annex B: Security measures

1. Encryption in transit: TLS on every public endpoint; HSTS on the API.
2. Encryption at rest: object storage is encrypted at rest (AES-256, metadata included) by the provider; database backups are encrypted with GPG to a key kept off the processing fleet.
3. Server access: processing servers and the control plane accept SSH keys only, with no password logins; default-deny firewalls and brute-force protection run on each server.
4. API: every route requires authentication; keys are stored only as hashes; each customer's data is filtered by tenant inside the database queries, with cross-tenant tests in continuous integration; files move through single-object signed links that expire in 5 to 60 minutes; rate limits apply per customer and per frontend.
5. Processing isolation: processing containers run with no network access, no added privileges and pinned images; storage credentials never enter the processing container.
6. Patching: automatic security updates run on the processing fleet; the database is kept on a current minor release.
7. Resilience: the database streams in real time to two standby servers, and encrypted dumps run every 15 minutes. Customer maps are held as one copy, with no separate backup (disclosed in Agreement section 10.2).
8. Monitoring: an external watchdog checks the service every 5 minutes, and a processing event log is recorded.
9. Personnel: access is limited to named staff.
10. Incident response: a 72-hour customer notice (section 9).

Annex C: Subprocessors

Client data is hosted and read from Cloudflare R2. Our own internal and test datasets on other systems are not Customer Data.

Also used, with no Customer Data: Netlify (hosts swathmap.com and its contact form); GitHub (code); healthchecks.io (uptime pings); Linear (task tracking). None of them stores customer files, except that support emails you send us may carry attachments.

Last Updated: October 15, 2026