Skip to content

Backup Responsibility

crawl55 edited this page Apr 1, 2026 · 1 revision

Backup Responsibility

Last Updated: March 28, 2026

This Backup Responsibility Policy explains the roles and responsibilities related to data backup and recovery within the FarmPath application ("App").

This policy supplements:

  • Terms of Service
  • Privacy Policy
  • Data Governance Policy

1. Backup Philosophy

FarmPath is designed as a farm management tool, not a data backup service.

FarmPath is not intended to function as:

  • A disaster recovery system
  • A financial archive system
  • A regulatory storage system
  • A permanent data preservation system

Users must maintain independent backups of important data.


2. User Responsibility for Backups

Users are solely responsible for:

  • Maintaining backups
  • Exporting important records
  • Protecting backup files
  • Verifying backup accuracy

Users should not rely on FarmPath as their only data storage.


3. Local Storage Risks

Data stored locally on a device may be lost due to:

  • Device failure
  • Device damage
  • Device theft
  • Operating system issues
  • App removal
  • Factory reset

FarmPath cannot recover locally deleted data.

Users assume these risks.


4. Cloud Sync Is Not a Backup

Cloud synchronization is designed for data availability, not backup.

Cloud sync may:

  • Overwrite data
  • Propagate deletions
  • Propagate errors
  • Sync corrupted records

Cloud sync does not guarantee historical recovery.

Users should maintain separate backups.

(This is a critical enterprise clause.)


5. Sync Conflict Risks

When multiple devices sync:

Conflicts may result in:

  • Overwritten records
  • Duplicate records
  • Deleted records
  • Outdated records

FarmPath does not guarantee preservation of all data versions.

Users must verify data after syncing.


6. Export Features

FarmPath may provide data export tools.

Exports may include:

  • Financial records
  • Operational data
  • Animal records
  • Equipment records

Users are responsible for:

  • Saving exports
  • Securing exports
  • Maintaining exports

Exported files are outside FarmPath control.


7. Backup Best Practices

We strongly recommend users:

  • Export data regularly
  • Store backups securely
  • Keep multiple backup copies
  • Verify backups periodically

These practices reduce data loss risk.


8. Data Recovery Limitations

FarmPath does not guarantee:

  • Recovery of deleted records
  • Recovery after sync conflicts
  • Recovery after device failure
  • Historical rollback
  • Backup restoration

Users acknowledge data recovery may not be possible.


9. Shared Data Risks

If data is shared:

Other authorized users may:

  • Delete records
  • Modify records
  • Overwrite records

FarmPath is not responsible for data loss caused by authorized users.

Users should manage access carefully.


10. Subscription Status and Data

Subscription expiration does not automatically delete user data.

However:

Certain features may become unavailable.

Users remain responsible for exporting data if needed.

(This prevents disputes.)


11. Data Integrity Limitations

FarmPath does not guarantee:

  • Continuous storage
  • Perfect data preservation
  • Error-free sync
  • Permanent retention

Users must verify critical records independently.


12. Third Party Storage Dependencies

FarmPath may rely on:

  • Apple CloudKit
  • Device operating systems
  • File systems

We are not responsible for failures of third party storage systems.


13. Business Continuity Disclaimer

FarmPath is not a business continuity system.

Users must maintain:

  • Independent accounting records
  • Operational documentation
  • Regulatory documentation

FarmPath should not be the sole storage of critical business information.

(This is standard enterprise SaaS language.)


14. Regulatory Compliance Disclaimer

Users remain responsible for maintaining records required for:

  • Tax reporting
  • Agricultural compliance
  • Business reporting

FarmPath does not guarantee regulatory record retention.


15. User Device Responsibility

Users should:

  • Secure devices
  • Backup devices
  • Wipe devices before transfer
  • Reset devices before sale

We are not responsible for data left on transferred devices.


16. Backup Security

Users should protect backups from:

  • Unauthorized access
  • Data corruption
  • Accidental deletion

FarmPath cannot secure exported files.


17. No Liability for Data Loss

To the fullest extent permitted by law:

Crawford Family Farm is not liable for:

  • Lost data
  • Lost financial records
  • Lost operational records
  • Lost animal records
  • Lost equipment records

Users assume responsibility for backup management.

(This is one of the most important clauses.)


18. Recommended Backup Strategy

We recommend:

  • Regular exports
  • Multiple storage locations
  • Secure storage
  • Periodic verification

This significantly reduces risk.


19. Future Backup Features

FarmPath may introduce future backup features.

However:

We do not guarantee permanent data preservation.

Users should maintain independent backup practices.


20. Changes

We may update this policy.

Continued use constitutes acceptance.


21. Contact

Questions regarding backup responsibilities:

support@farmpath.app

Crawford Family Farm


22. Summary

FarmPath is not a backup system.

Users are responsible for backing up their data.

Cloud sync is not a backup.

Users must export important data.

We believe users should control their farm records and backups.

Clone this wiki locally