ArbaEdge
Privacy
ArbaEdge
Privacy
This platform is operated by ArbaLabs and provided to you through your organisation's customer portal. This Privacy Policy describes how ArbaLabs handles information processed through the ArbaEdge platform. We are committed to protecting your privacy and handling any information we receive with care.
Your files are not uploaded to ArbaLabs. When you record or check a file, its SHA-256 fingerprint is computed in your browser, and the fingerprint is sent together with the details described below.
Each verification record stores the fingerprint, the module it was made in, the organisation and account it belongs to, the time it was recorded, and the details sent with it: for a recorded document, the file’s name and size and your own reference; for a check made on an organisation’s verification portal, the checked file’s name and whether it matched — the check is kept in that organisation’s records, where the organisation can see it; for an AE-PX1 alert, the kind of alert, the reading that triggered it (for example a temperature) and the device’s label; for an AE-PX1 inference record, the model file’s name and size, the hashes of the model file, the camera frame and the detection result, the objects the browser’s detector reported with their positions and confidence, the device’s label and the time of capture. The camera image itself is never sent. A record made with an API key also notes which key made it.
We also process account and organisation information: the organisation’s name, industry, contact email and manager’s name, the email address of each account, and the passwords, access codes and API keys used to sign in or record, which are stored only as one-way hashes. AE-PX1 projects you create, including any member names you add, are stored with your organisation or account. Within an organisation, its people see each other’s email address and role and which account made each of the organisation’s records, and its administrators also see a list of who invited, removed or changed the role of whom, with the time; none of them is shown a network (IP) address.
To protect accounts, ArbaLabs records each account sign-in attempt with the email address used, the network (IP) address, the time and whether it succeeded, and logs portal and verification-portal sign-ins and other security-relevant actions with the network address and time.
This platform does not use advertising cookies, analytics cookies, or behavioural tracking technologies. Signing in sets session cookies that page scripts cannot read: for an account, a 15-minute session cookie and a renewal cookie that expires 7 days after it was last used; for a portal, a 12-hour session cookie; for a verification portal, a 2-hour session cookie. Your browser’s storage also keeps a sign-in hint, which is not a credential, your theme and language preferences, and a working copy of your AE-PX1 projects.
Fingerprints and the details recorded with them are used solely for integrity verification — comparing them against golden baselines, recording them and answering checks. Account information is used to manage your portal access and communicate service updates.
We do not use your information for marketing purposes without explicit consent, and we do not sell or share your information with third parties for their own commercial purposes.
Verification records hold the fingerprint and the details listed above, never the file itself. They are kept in an append-only sequence, each sealed together with the one before it, and whoever creates a record receives a signed receipt for it. If a record is ever removed, or its seal rewritten, its receipt stops matching our records. Anyone who has the same file can check whether it has been recorded, and when, without seeing its file name, your reference or your organisation; on your organisation’s public verification page they can check whether your organisation recorded it. File names and references are stored as they are sent, so choose them with that in mind.
ArbaLabs does not sell, rent, or share your personal information with third parties, except where required by law.
Verification records are retained for the duration of your organisation’s agreement with ArbaLabs. You may request deletion of your verification records at any time by contacting ArbaLabs; note that removing a record breaks the sequence linking the records that follow it.
ArbaLabs implements reasonable technical and organisational measures to protect information processed through this platform, including encrypted connections, access controls, and secure server infrastructure.
Depending on your location, you may have rights regarding your personal information, including the right to access, correct, or request deletion of information we hold about you. To exercise any of these rights, please contact ArbaLabs directly.
ArbaLabs may update this Privacy Policy from time to time. The date at the top of this page reflects when the policy was last revised. Continued use of this platform following any changes constitutes your acceptance of the revised policy.
If you have questions about this Privacy Policy or how ArbaLabs handles your information, please contact us at info@arbalabs.com.