01
Who this policy covers
AccessRA Field Handbook is developed and operated by AccessRA in Port Harcourt, Nigeria. It is a field-support application for instrumentation, calibration, measurement and well-test-related engineering work.
Privacy enquiries can be sent to handbook@accessra.com. General company enquiries can be sent to contact@accessra.com.
02
Information you enter in the app
The current Field Handbook can store working calibration records on your device. Depending on the record you create, this can include instrument tag, instrument type, technician name, LRV, URV, engineering unit, tolerance, calibration points, as-found/as-left status, remarks, pass/fail result and record date/time.
These records are entered by you for your own field workflow. The current app does not require an AccessRA account for this local record workflow, and the core calibration record is not automatically uploaded to AccessRA simply because you save it in the app.
03
Information you send to AccessRA
If you contact AccessRA by email or through an AccessRA support channel, we receive the information you choose to send. This may include your name, email address, organization, support message, screenshots or other material you deliberately attach. We use this information to answer your enquiry, investigate reported errors and improve the Field Handbook.
Do not send passwords, API keys, confidential client drawings, restricted site information or other material you are not authorized to disclose.
04
Data collected by platform or third-party services
Google Play and the Android operating environment may process account, device, diagnostic, installation or update information under Google's own terms and privacy policies. AccessRA's Google Play Data Safety declaration must match the exact Field Handbook build distributed through Google Play, including any third-party SDK that may transmit user or device data.
If a future Field Handbook release introduces analytics, crash reporting, cloud synchronization, user accounts, location, camera access or another feature that changes data handling, this policy and the Play Data Safety declaration will be updated before that handling is relied upon.
05
How AccessRA uses information
Information received by AccessRA is used only for legitimate purposes such as providing support, responding to technical feedback, correcting application defects, maintaining service security and improving Field Handbook features. AccessRA does not sell Field Handbook personal information.
07
Security
AccessRA uses reasonable technical and organizational safeguards for information under its control. Local Field Handbook records are also affected by the security of your Android device, including your screen lock, device access, backups and operating-system configuration. No electronic storage or transmission method can be guaranteed to be completely secure.
08
Retention and deletion
Local calibration records remain on the device until you delete them through the application, clear the app's storage or remove the application, subject to any device or platform backup behaviour you have enabled.
Support correspondence is retained only as long as reasonably necessary to handle the enquiry, maintain an appropriate technical/support record, meet legal obligations or resolve disputes. You may request deletion of personal information you previously sent to AccessRA by contacting handbook@accessra.com. AccessRA may retain limited information where a legal, security or legitimate recordkeeping obligation requires it.
09
Accounts
The current Field Handbook local-record workflow does not require an AccessRA user account. If a future release allows users to create an account or synchronize records with AccessRA servers, AccessRA will provide an in-app and web-accessible account-deletion process before that account feature is released.
10
Children
AccessRA Field Handbook is designed for engineering, technical training and industrial field work. It is not directed to children.
11
Changes to this policy
This policy may be updated when Field Handbook features, data handling, legal requirements or third-party services change. The effective/updated date on this page will identify the current published version.
12