1. Important security notice
This page is informational. It describes JK FieldOps security and data practices at a high level. It is not a security certification, audit report, service-level agreement, warranty, guarantee of uninterrupted service, or promise that a security incident, data loss, or unauthorized access can never occur.
Specific contractual security commitments, if any, must be stated in a signed written agreement with JK FieldOps. Security practices, service providers, and procedures may change as the service develops or as threats and operational requirements change.
2. Customer data and control
Customers retain ownership of the records and content they provide to JK FieldOps, including tickets, images, PDFs, spreadsheets, project information, reconciliation records, payment-related records, agreements, equipment records, and other uploaded or created business information ("Customer Data").
JK FieldOps processes Customer Data only as reasonably necessary to provide, secure, maintain, support, troubleshoot, and improve the service; to follow authorized customer instructions; or to comply with applicable law.
JK FieldOps does not sell Customer Data or use Customer Data for third-party behavioral advertising.
Customers are responsible for determining what data they upload, ensuring they have the right to provide it, and configuring their users and permissions appropriately.
3. Access and account controls
Controlled access
JK FieldOps is designed so access to customer records can be limited according to authorized organization, project, company, and user relationships.
Permission management
Customers can assign different levels of access based on business responsibilities rather than giving every user the same capabilities.
Administrative access
Administrative access is limited to authorized functions and personnel needed to operate, support, secure, and administer the service.
Account safeguards
JK FieldOps uses account and access safeguards designed to protect credentials and reduce unauthorized access. Specific security mechanisms are not publicly detailed.
No access-control system can prevent every misuse. Customers remain responsible for credential security, authorized-user management, endpoint security, and promptly removing access that is no longer appropriate.
4. Records, files, and auditability
JK FieldOps is designed to keep supporting files connected to the operational records they support. Depending on the feature, the service may maintain audit or history information about important actions and record changes.
Audit and history features are operational aids. They are not guaranteed to capture every event, are not a substitute for any legally required recordkeeping system, and do not independently establish the legal validity, authenticity, admissibility, or contractual effect of a record.
5. Service outputs and customer verification
Information produced, transformed, compared, calculated, matched, or otherwise presented by the Service may be incomplete, inaccurate, duplicated, delayed, or affected by the quality, completeness, or configuration of Customer Data.
Customers must independently review and verify material records and values before relying on them for billing, reconciliation, payment, legal claims, compliance, safety, or other consequential decisions. JK FieldOps does not certify source documents, establish that work was performed, determine contractual entitlement, or guarantee the accuracy, completeness, or acceptance of Service outputs.
6. Data resilience and availability
JK FieldOps uses operational measures intended to reduce the risk of data loss and service disruption. No online service can eliminate all risk of corruption, deletion, loss, outage, cyberattack, third-party failure, or human error.
Customers remain responsible for their own contractual, legal, tax, regulatory, and business record-retention obligations and should maintain independent copies of records they cannot afford to lose. Unless a signed agreement expressly states otherwise, JK FieldOps does not warrant any particular recovery point, recovery time, retention period, or uninterrupted availability.
7. Third-party services
JK FieldOps may rely on third-party service providers where reasonably necessary to operate, secure, support, communicate about, or administer the Service.
Third-party services are outside JK FieldOps's direct control and may be subject to their own terms, practices, outages, changes, or discontinuation. JK FieldOps uses reasonable business judgment in selecting and managing providers but cannot guarantee the uninterrupted operation or absolute security of systems outside its direct control.
8. Sensitive and specially regulated data
Unless JK FieldOps expressly agrees otherwise in writing, the service is not designed to serve as a dedicated system of record for payment-card data, protected health information, consumer credit-reporting data, classified information, export-controlled technical data, biometric templates, or other information subject to specialized security or regulatory regimes.
Customers should not upload Social Security numbers, complete payment-card credentials, authentication secrets, private cryptographic keys, or other highly sensitive information unless the information is necessary for an authorized workflow and the customer has confirmed that its use is appropriate.
9. Security incidents
If JK FieldOps becomes aware of a confirmed security incident affecting Customer Data, JK FieldOps will investigate and take reasonable steps appropriate to the nature of the incident. Any customer notification obligations, timing, or cooperation requirements are governed by applicable law and any signed written agreement.
Customers must promptly notify JK FieldOps of suspected unauthorized access to their accounts and cooperate in reasonable containment and investigation steps.
10. Security testing and vulnerability reports
Do not probe, scan, exploit, stress-test, or attempt to bypass JK FieldOps security controls without prior written authorization. Good-faith vulnerability reports may be sent to contact@jkfieldops.com. Do not include passwords, private keys, or unnecessary Customer Data in the initial report.
Submitting a report does not authorize destructive testing, access to another customer's data, disruption of service, social engineering, or any activity prohibited by law or the Terms of Service.
11. Data lifecycle
Retention
Customer Data may be retained while an account is active and afterward for a reasonable period where necessary for security, dispute resolution, billing, legal compliance, fraud prevention, service continuity, or legitimate business records.
Export
Where supported, customers may export records through application features or request reasonable assistance subject to the applicable agreement. Customers should export information they need before account termination.
Deletion
Deletion requests are subject to identity and authority verification, applicable contractual obligations, legal requirements, technical limitations, and legitimate security, accounting, or operational needs. Deletion from active systems does not necessarily result in immediate deletion from retained copies, logs, or legally required records.
12. Shared responsibility
Customers are responsible for managing their own users, permissions, devices, passwords, email accounts, scanners, local files, exports, and business procedures. Customers should apply least-privilege access, promptly disable former users, use trusted devices and networks, verify recipient addresses before sending records, and maintain independent copies of critical records.
JK FieldOps is not responsible for compromise or disclosure caused by customer credential sharing, customer-controlled devices, unauthorized customer users, insecure customer networks, customer configuration, or third-party systems selected or controlled by the customer.
13. Changes to security practices
Security practices evolve. JK FieldOps may modify controls, providers, procedures, and this page without reducing any express commitment contained in a signed written agreement. The date at the top identifies the current public version.
14. Contact
Security and data questions can be sent to contact@jkfieldops.com.