1. Who we are
Scarab Solutions LTD (Company No. 09759786, Cambridge House, 32 Padwell Rd, Southampton SO14 6QZ, United Kingdom; “Scarab”, “we”, “us”) develops and supports the applications covered by this policy.
Scarab and the organisation that authorises your access (for example, your employer, farm operator or Scarab customer) may have different data-protection roles. The organisation normally determines why agronomic work records are created and used. Scarab processes those records to provide and support the service and may also act as controller for app diagnostics, security and direct support communications. Your organisation can provide further information about its own processing.
2. Apps covered by this policy
This single policy applies to the following Android apps, which share the same core functionality:
| App | Google Play package ID |
|---|---|
| Scarab Precision | com.scarabsolutions.precision |
| Scarab Crop Husbandry | com.scarabsolutions.crophusbandry |
| Scarab White Rust | com.scarabsolutions.whiterust |
It applies to data handled through the apps, their synchronisation services and support functions. A customer’s separate websites, systems or policies may also apply when clearly identified.
3. Privacy summary
- The apps are professional agronomic tools and do not contain advertising.
- We do not sell personal data and do not use it for cross-app advertising or marketing profiles.
- Precise location is used while the app is in use to attach a field position to an observation. The apps do not request background-location permission.
- The camera is used to scan a setup QR code. Camera images and video are not uploaded by the apps.
- A random app installation identifier and basic device information are used for pairing, synchronisation, compatibility and support.
- Sentry receives diagnostic information to identify crashes and synchronisation errors.
4. Data we access, collect and use
| Google Play data category | Specific data | How and why it is used | Sent off the device? |
|---|---|---|---|
| Personal information | User or enumerator name and user ID assigned by the authorised organisation. | To select the authorised worker, authenticate access, attribute field records and maintain operational traceability. | Yes, with agronomic records and the organisation’s Scarab service. |
| Authentication information | A hashed representation of the assigned password; session and access tokens. | To verify authorised access, including offline access, and secure synchronisation. The password typed at login is processed temporarily on the device, converted to a hash for comparison and cleared after the attempt. The app does not send the typed password to the server. | Tokens are exchanged with the service. The typed password is not transmitted by the app. |
| Precise location | GPS latitude and longitude associated with a field stop, together with the location timestamp. | To confirm where an observation was made, identify the relevant field area and support agronomic traceability. | Yes, when the user synchronises records. It can also be included in a user-initiated support export. |
| User-generated content / app activity | Agronomic observations and values, such as counts, presence or scores; crop, template, work order, farm, map, block, bed or trap references; dates, times and synchronisation status. | To record fieldwork, show summaries, work offline and synchronise completed observations. | Yes, with the organisation’s Scarab service. |
| Device or other IDs | A random installation ID generated by the app; pairing/client identifiers. | To pair the installation with the correct organisation, authorise access, prevent mix-ups between clients and trace synchronisation. | Yes, with the organisation’s Scarab service. |
| Device and app information | Device manufacturer and model, Android version, app name/version, language/time-zone configuration, network status and technical network metadata such as IP address when connecting. | Registration, compatibility, correct date/time handling, secure communications, troubleshooting and service protection. | Yes, as necessary for registration, network operation and diagnostics. |
| App information and performance | Crash reports, error messages, stack traces, timestamps, app/device context and limited activity context associated with a failure. | To detect, diagnose and correct crashes, failed synchronisations and reliability problems. | Yes, to Sentry. Error details may also be available to Scarab support. |
| Camera and QR setup data | Live camera view and the contents of a Scarab setup QR code, including the service address and temporary pairing code. | To connect the app to the correct customer environment. QR contents are read on the device; the pairing code is then sent to the specified service to complete setup. | The camera image/video is not uploaded. The QR setup values are used to contact the specified service. |
| Support communications and files | Information included in emails or support requests. An authorised user may choose to export a compressed copy of the local app database, which can contain the categories listed above. | To investigate and resolve a support incident. | Only when the user or administrator initiates the export and confirms sending it through an email app. |
The apps do not collect payment information, contacts, call logs, SMS, health data or advertising IDs. They do not access personal photos, videos or audio; camera processing is limited to scanning the setup QR code on the device. The apps do not use Google Analytics or Firebase Analytics.
5. How data is collected and permissions are used
Information supplied by you or your organisation
- Your organisation supplies authorised-user, farm, crop, map, template and work-order information.
- You enter observation values and choose the relevant field area, bed or trap.
- You scan a setup QR code supplied by an authorised administrator.
- You may voluntarily send a support message or initiate a database export.
Information collected automatically
- The app generates a random installation ID during QR setup and obtains basic device/app information.
- When you use the observation screen and create a record, the app obtains the device’s current GPS position. Location updates stop when that screen is paused or closed.
- Sentry automatically receives crash and error diagnostics when a reportable problem occurs.
- Servers necessarily receive connection metadata, including IP address and request time, when the app communicates with them.
Annex A explains the Android permissions used by the apps. Denying camera or location access prevents the related feature from working, but the permission can be changed later in Android settings.
6. Purposes and legal bases
| Purpose | Data involved | Legal basis, where applicable |
|---|---|---|
| Provide pairing, authorised access, offline field recording, summaries and synchronisation | Account, installation, agronomic and location data | Performance of a contract and steps necessary to provide the requested service |
| Maintain farm traceability, quality control and operational records | User ID, location, timestamps and agronomic records | Performance of a contract and legitimate interests of Scarab and the authorised organisation |
| Protect the service and prevent unauthorised access or incorrect client pairing | Tokens, IDs, device/app and network information | Legitimate interests in security and fraud prevention; legal obligations where applicable |
| Diagnose crashes and service errors and provide support | Diagnostics, device/app context, support messages and optional support exports | Legitimate interests in reliability and support; your request or affirmative action for optional exports |
| Meet legal requirements and establish or defend legal claims | Only information reasonably necessary for the relevant requirement | Legal obligation or legitimate interests |
Where local law requires consent for a specific activity, we rely on consent and you may withdraw it for future processing. Withdrawing or denying permission does not affect earlier lawful processing, but may make the corresponding app feature unavailable.
8. Data retention
| Data | Retention approach |
|---|---|
| Data on the device | Pending observations remain until they can be synchronised. The app periodically removes successfully synchronised observation records older than seven days from its active database. Configuration, catalogues, credentials in hashed form, tokens and auxiliary files may remain until replaced, the app’s storage is cleared or the app is uninstalled. |
| Agronomic records on the organisation’s service | Retained for the duration required by the customer relationship, agronomic traceability, operational needs and applicable law. The applicable organisation or Scarab will delete or de-identify records when they are no longer needed, subject to legitimate retention duties. |
| Diagnostic data | Retained in Sentry for the period configured for Scarab’s service plan and only as long as reasonably necessary to investigate reliability and security issues. |
| Support communications and exports | Retained while the support case is active and for a reasonable period afterwards for follow-up, security and accountability, then deleted or de-identified unless longer retention is legally required. |
| Legal and security records | Retained for the period required by applicable law or reasonably necessary to establish, exercise or defend legal claims and prevent abuse. |
Because work records may belong to or be controlled by your organisation, its retention schedule may also apply. Contact us or your organisation for the schedule applicable to your deployment.
9. Security
Scarab uses safeguards appropriate to the nature of the data, including HTTPS/TLS for production network communications, app-specific Android storage, access/session tokens, role-based access to customer environments, restricted support access and contractual confidentiality. The apps prevent Android from including their local storage in the automatic device backup linked to a user’s personal Google account. This is separate from Scarab synchronisation: agronomic records sent through the app remain stored in the organisation’s server database according to Section 8. A support database is shared through Android’s controlled file-sharing mechanism and only after a user initiates the action.
No system is completely secure. Users should protect their device and credentials, install updates, use only QR codes supplied by an authorised administrator and avoid sending database exports unless requested through a trusted support channel. Please report a suspected security or privacy incident using the contact details below.
10. International data transfers
Scarab is established in the United Kingdom, customers may operate in other countries, customer application servers may be hosted in different regions, and Sentry processes service data using infrastructure in the United States and Germany. Data may therefore be processed outside the country where it was collected.
Where required, Scarab uses recognised safeguards for international transfers, such as adequacy regulations or decisions, the UK International Data Transfer Addendum, the European Commission’s Standard Contractual Clauses, the EU–U.S. Data Privacy Framework where applicable, or another lawful mechanism. You may contact us for information relevant to your deployment.
11. Your choices and data-protection rights
Depending on your location and the applicable law, you may have rights to:
- request access to and a copy of your personal data;
- correct incomplete or inaccurate data;
- request deletion or restriction of processing;
- object to processing based on legitimate interests;
- request portability of data you provided, where applicable;
- withdraw consent for future processing where consent is the basis; and
- complain to the UK Information Commissioner’s Office or your local data-protection authority.
The apps do not make decisions that produce legal or similarly significant effects solely through automated processing. To exercise a right, contact us and identify the app, your organisation/farm and your user name or assigned user ID. We may need to verify your identity and coordinate with the organisation that authorised your account.
12. Account and data-deletion requests
The apps do not let users create an account. User access is provisioned and managed by an authorised organisation. To deactivate your access or request deletion of personal data, contact your organisation’s administrator or email info@scarab-solutions.com with:
- the name of the app;
- your organisation, client or farm;
- your user name or assigned user ID; and
- a clear description of the account or data you want deleted.
We will acknowledge and process a valid request within the period required by applicable law, normally within 30 days, or forward it promptly to the organisation responsible for the data. If records must be retained for legal, security or legitimate farm-traceability reasons, we will explain the applicable limitation and, where appropriate, restrict, delete or de-identify the personal link.
Uninstalling the app or clearing its storage removes the app’s local data from that device. Android’s automatic device backup is disabled, but this is separate from Scarab synchronisation. Uninstalling does not delete records already synchronised to the organisation’s server database, diagnostic records already sent to Sentry, or copies previously sent by email; those require the request described above.
13. Children
The apps are professional workplace tools intended for authorised users aged 18 or over. They are not directed to children, and Scarab does not knowingly collect personal data from children through them. If you believe a child has provided data, contact us so it can be investigated and deleted where appropriate.
14. Changes to this policy
We may update this policy to reflect changes to the apps, service providers, law or our practices. The “Last updated” date identifies the current version. If a change materially affects how personal data is used, we will provide reasonable notice through the app, Google Play, this page or the authorised organisation, as appropriate.
15. Contact
Privacy contact — Scarab Solutions LTD
Email: info@scarab-solutions.com
Address: Cambridge House, 32 Padwell Rd, Southampton SO14 6QZ, United Kingdom
Support: www.scarab-solutions.com/support
You may also contact the organisation that provided your app access. UK users may complain to the Information Commissioner’s Office.
Annex A – Android permissions and sensitive access
| Permission or capability | Use | When used |
|---|---|---|
| Precise and approximate location | Obtains the current field position and attaches it to an observation. The precise GPS position is used when available. | While the observation screen is in use. No background-location permission is requested. |
| Camera | Scans a QR code to connect the installation to the correct customer environment. | During initial setup or when the user chooses to scan a new code. Images and video are not uploaded by the app. |
| Internet and network state | Registers the installation, downloads assigned catalogues/work and synchronises records; checks whether a connection is available. | During setup and synchronisation. |
| App-specific storage / controlled file sharing | Creates a compressed support export in the app-specific storage area and passes access to the email app selected by the user. This does not require access to the user’s photos, media or other files. | Only when an authorised user chooses the database export function. |
| Vibration | Provides optional feedback after a field observation is successfully captured. | When enabled in app settings. |
Annex B – Definitions
“Agronomic records” means field observations, counts, presence/score values and their related crop, work-order, map, bed/trap, user, time and location context.
“Authorised organisation” means the employer, farm operator, customer or other organisation that grants a user access to one of the apps.
“Personal data” means information relating to an identified or identifiable person, as defined by applicable data-protection law.
“Processing” includes collecting, accessing, storing, using, transmitting, sharing, deleting or otherwise handling data.