VeriCheck App Privacy Policy

Last updated: October 25, 2026

VeriCheck is owned and provided by Verify Diagnostics Inc. This policy applies to the VeriCheck iPhone and iPad application and its related sign-in, account approval, support, optional encrypted cloud-backup services, and optional integrations with Google Drive and Veriport.

Provider: Verify Diagnostics Inc.

Address: 122 Commerce Park Dr., Unit D, Barrie, Ontario L4N 8W8, Canada

1. Who this policy covers and our respective roles

VeriCheck helps professional collectors document drug-test collections, review image-assisted readings from compatible test cups, record results and signatures, and create reports.

In this policy, “Verify,” “we,” “us” and “our” mean Verify Diagnostics Inc.; “App” means VeriCheck; “Customer” means the organization or self-employed business using the App; “User” means its authorized collector or other authorized user; and “Donor” means a person being tested.

We are responsible for personal information used for our own account administration, approval, security and support activities. For donor and collection records, we provide the App and related services on the Customer’s behalf. The Customer determines the lawful testing purposes, information collected, authorized recipients and appropriate retention. Each party remains responsible for the privacy and security obligations applicable to its activities.

This policy does not replace the Customer’s donor-facing notice, a legally required consent or authorization, or a required health-information or data-processing agreement. Accepting app terms does not create donor consent.

Veriport is a separate application operated by Veriport Inc. Connecting it is optional. Verify Diagnostics Inc. remains the provider of VeriCheck. A connection to Veriport or Google Drive authorizes only the integration described and enabled by the Customer; using one service does not automatically authorize disclosure to the other. The handling of information delivered to an external account is explained in sections 4.2 and 4.3.

The Verify Diagnostics Business & Website Privacy Policy covers visits to our public marketing websites and ordinary business interactions. It does not expand the uses of App information permitted by this policy. The VeriCheck App Terms & Conditions address the separate software agreement; their risk-allocation provisions do not waive mandatory privacy rights or our own legal duties.

2. Collection records, device storage and permissions

Information entered or captured in the App

The App handles information supplied by Users and Donors or created during the collection workflow:

Category	Examples	Purpose
Collection and test records	Client and donor details, identification information, collection site, test device, dates, test details, cup readings or manually entered results, comments and report numbers	Document the collection, assist review of screening results and prepare reports
Images and attachments	Cup photographs, identification or face photographs, and attached files	Document the test device and collection, support image-assisted cup reading and retain relevant supporting material
Signatures and consent records	Donor and collector signatures, the consent statement retained with a signed record, and recorded refusal status	Document the collection and the consent or refusal information entered
Reports and revisions	Generated PDFs and saved revisions	Produce reports and maintain the saved record history
Configuration	Clients, test devices, collection sites, company profile and logo, collector profile, consent wording and preferences	Configure and operate the Customer’s collection workflow

Collect only information necessary and legally authorized for the relevant testing activity. Photographs and signatures are used for the collection-related purposes described here; this policy does not authorize unrelated identification, advertising or model-training uses.

Local storage and automated assistance

Saved records are kept in the App’s private storage on the User’s iPhone or iPad. The App uses iOS data-protection features; protection also depends on the device passcode, operating-system security and access controls. Saved records remain locally whether cloud backup is on or off. An unfinished test is not a saved record until it is saved.

The cup-reading feature uses test-cup images to assist the collector. A collector must verify proposed readings against the actual device and its instructions before saving or reporting results. The App does not make an employment, medical or legal decision about a Donor. A preliminary screen is not a diagnosis or a determination of impairment.

Permissions and copies outside the App

The App requests camera access for test-cup and collection-documentation photographs. Features using photos or files access material through the selections or permissions you authorize. You can manage permissions in iOS Settings. Refusing or withdrawing a permission may prevent the associated feature from working; it does not automatically delete existing records or backups.

Reports or files that you export, share or save outside the App are separate copies. This includes PDFs saved to a connected Google Drive account and records sent through an authorized Veriport integration. Their recipients, protection, location and retention depend on the choices and services used. A copy in another application or a separate device backup is not governed by VeriCheck’s cloud-backup location controls. The Customer is responsible for authorized exports and for applicable handling of those independent copies. Sections 4.2, 4.3, 5 and 9 explain these distinctions.

3. Accounts, Google user data and operational information

3.1 Account creation and approval

VeriCheck supports email sign-in, Google Sign-In and Sign in with Apple through its authentication arrangements. We process the email address, account identifier, chosen sign-in method and authentication information needed to establish and secure the account.

For approval, you provide your name, telephone number, company name, company telephone number and address. These details are stored in our account systems and sent to our support team through Zoho Mail for review. Account approval does not verify the legality of a Customer’s testing programme.

When Sign in with Apple is used, Apple may provide the name and email address the User authorizes, including an Apple private relay email address where selected, and an Apple account identifier for the sign-in relationship. We do not receive your Apple Account password.

Google Sign-In is optional. It allows you to authenticate with an existing Google account rather than use another supported sign-in method.

Through the basic sign-in process, VeriCheck and Firebase Authentication receive the Google identity information made available for the authorized sign-in: a unique Google account identifier, email address and verification status, and basic profile information such as your name and profile-picture URL where supplied. Authentication tokens and related credentials are processed to validate and maintain the authorized sign-in. We do not receive your Google password.

Google Sign-In alone is used for identity and account access. It does not authorize access to Gmail messages, Google Drive files, Google Calendar events, Google Contacts or Google Photos. The optional Google Drive report-export integration requires a separate choice and additional, limited Drive authorization, as described in section 4.2. VeriCheck does not request Gmail, Calendar, Contacts or Photos access for either sign-in or this Drive-export feature.

VeriCheck’s encrypted cloud-backup service uses Verify’s Google Cloud services. It is separate from exporting readable PDF reports to the User’s connected Google Drive account. Signing in with Google does not by itself enable either feature or connect Veriport.

Apart from the optional Drive authorization expressly described in section 4.2, any additional Google permissions or new uses of Google data require an appropriate explanation and any required authorization before access or use. This policy does not pre-authorize undisclosed Google permissions.

3.3 How Google user data is used, stored and disclosed

We use Google sign-in information to authenticate you, create or link your VeriCheck account, administer the authorized account, communicate about that account when necessary, provide requested support and help protect against unauthorized access or abuse. Google Sign-In does not subscribe you to unrelated marketing.

Google Firebase Authentication processes authentication information, including relevant account identifiers, credentials, IP addresses and user-agent information, for sign-in and security. Authentication processing occurs in the United States, including for Canadian Users. Account-profile copies in our regional Customer databases follow the country arrangement in section 5.

Google Cloud services process the relevant account information needed for those databases and account functions. Necessary contact and approval information may be handled by our authorized support personnel and through Zoho Mail. We do not put Google authentication tokens into ordinary approval or support emails. Additional disclosures are limited to section 7 and applicable restrictions on Google user data.

We protect this information through secure transmission, access restrictions and the provider safeguards described in section 8. Google-linked account information is retained and deleted according to section 9, including the account-deletion feature and provider deletion cycles.

3.4 Google API data, Limited Use and revoking access

VeriCheck’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. These commitments cover Google Sign-In and the optional Google Drive integration, including relevant information derived from Google API data.

We use Google API information only for the disclosed, user-facing sign-in, associated account administration and requested support, security, and authorized report-export functions. We do not sell it, supply it to data brokers or advertising platforms, use it for targeted advertising or creditworthiness decisions, or use it to train generalized artificial-intelligence or machine-learning models.

Transfers are limited to those permitted by Google’s policies: providing the disclosed user-facing feature with the User’s consent; necessary security purposes; compliance with applicable law; or a permitted business transfer after obtaining the required explicit prior consent. A general disclosure provision elsewhere in this policy does not expand those permissions.

Human access is limited to circumstances permitted by Google’s policies, such as affirmative permission to review specific information for support, necessary security investigation, legal compliance, or permitted internal use of appropriately aggregated information. Our employees and providers must observe the same restrictions. The direct-to-Drive report-export route does not deliver those PDFs to Verify’s servers or support staff.

You may remove VeriCheck’s Google access through your Google Account connections controls. Removing an authorization stops further access under that authorization; it does not delete your VeriCheck account or previously stored information. Drive PDFs remain in the connected account until removed there. Revoking an authorization that is also used for Google Sign-In may affect that sign-in method. Sections 4.2 and 9 explain how disconnection, file deletion and account deletion differ.

3.5 Security, backup metadata and support

Firebase App Check and Apple App Attest process app/device attestation material and security tokens to help verify requests. Donor records are not sent as attestation material.

To administer backup, we process account and item identifiers, item types, counts and sizes, upload times and device codes. A randomly generated three-letter device code helps distinguish report numbers. Readable backup metadata does not contain donor names, test results, photographs or report contents.

We also process correspondence and information you provide when seeking support. Do not send donor records, identification images, passwords or recovery keys in ordinary support email. Contact us first when a request needs sensitive material.

Connection information, file or report identifiers and delivery-status information needed for optional integrations are distinct from the cloud-backup metadata described above. They are used for the authorized connection and transfer functions explained in sections 4.2 and 4.3, not for advertising or profiling.

The App has no advertising, behavioural tracking or product-analytics tools. Necessary authentication, security and service-operation processing still occurs. Turning off cloud backup does not turn off the account and security processing needed to operate the service, and does not disconnect an integration that you separately enabled.

4. Optional encrypted backup and integrations

These are three separate choices. Enabling one does not enable the others, and signing in or accepting this policy does not automatically connect an external account.

Feature	Purpose and destination	Important distinction
VeriCheck encrypted cloud backup	Restore saved App information using encrypted copies in Verify’s regional Google Cloud storage	Off by default; content is encrypted with the App’s backup key before upload
Google Drive report storage	Store completed report PDFs, including revisions, in a VeriCheck folder in the connected Google Drive account for convenient access and organization	Separately authorized document storage, not VeriCheck backup; PDFs travel directly from your device to Google and remain in that account until removed there
Veriport integration	Send authorized reports or collection information to the connected Veriport account for the Customer’s test-management workflow	Optional connection to Veriport Inc.’s separate application; its account arrangements govern the received copies

4.1 VeriCheck encrypted cloud backup

Backup is off until you choose to enable it

Cloud backup is optional and off by default. It is available after account approval. After you create your first report, the App prompts you to enable encrypted backup. It starts only when you affirmatively choose to enable it. Declining or dismissing the prompt leaves backup off, and you can continue creating and storing reports locally.

You can enable backup later or disable it in Settings. Creating a report, using a marketing website, signing in with Google or Apple, or accepting the App terms does not automatically enable backup.

No donor records, photographs, signatures or reports are uploaded to VeriCheck’s cloud-backup service unless backup is enabled. Account, authentication and operational information is separate, as described in section 3. Authorized report exports and integration transfers are also separate: they can occur under their own enabled settings even when VeriCheck cloud backup is off.

Before enabling backup for a Customer, you must have its authority and ensure that required Donor notices, consent and other permissions cover the intended processing and storage arrangement.

Content, encryption and visibility

Once enabled, backup includes the saved information described in section 2: existing saved records and revisions and information subsequently saved while backup remains on. It does not include unfinished tests.

Content is encrypted on the device before upload using AES-256-GCM through Apple CryptoKit. The backup service receives encrypted content, not the key needed to read it. Verify and its backup storage provider cannot decrypt that content using the information held by the backup service.

We can see the limited administrative metadata described in section 3.5. The client-side encryption promise does not apply to readable account or support information separately provided to us, to Google Drive report PDFs, or to information you authorize for processing in Veriport. Those are not files protected by the VeriCheck backup recovery key.

Recovery keys and iCloud Keychain

The backup key is kept in the device Keychain. Unless key synchronization is disabled, it can also synchronize through iCloud Keychain under the applicable App and Apple settings. This is key synchronization, not VeriCheck’s cloud storage of donor records. VeriCheck’s encrypted record-backup service uses the Google Cloud storage described in section 5, not iCloud.

The App provides a recovery key when backup starts. Protect that key and maintain an authorized organizational recovery arrangement. A person who obtains the necessary key material and access to the encrypted files may be able to read them.

If all usable key copies are lost—including the device copy, any iCloud Keychain copy and the recovery key—we cannot restore the encrypted content. Resetting the account password does not recreate the encryption key. Ordinary device backups and independent exports are separate from VeriCheck’s optional backup service.

4.2 Optional Google Drive report storage

Your choice and the reports sent

If you connect Google Drive in Settings → Integrations, VeriCheck saves a PDF copy of each completed report, including completed report revisions, to a VeriCheck folder in the Google Drive account you connect while the integration is enabled. Connecting Drive is optional and separate from Google Sign-In and VeriCheck’s encrypted cloud backup. Without that authorization, this integration does not upload reports to your Drive.

The PDF contains the Donor and test information shown on the report. Depending on the report, this can include Donor identification details, Client and collection information, test results, comments, signatures, and photographs or other supporting information included in that PDF. This feature exports report PDFs; it does not grant general access to your Drive or authorize export of unrelated local records and attachments that are not part of the report.

Google Drive is used to store completed report documents for convenient access and organization. The integration is a report-export and records-storage feature, not a backup service. It is not intended to back up or restore your VeriCheck application, database, account or device, and it does not replace the separate optional encrypted cloud-backup service described in section 4.1.

Review the connected Google account and your organization’s authority to store sensitive reports there before enabling the integration. The Customer remains responsible for its applicable record-retention, access and deletion requirements.

Limited Google permission and information used

VeriCheck requests the per-file Google Drive permission to create and manage the files and folders it makes. The integration is limited to VeriCheck-created files and folders; it does not request permission to browse your entire Drive or access unrelated existing files. It does not request full-Drive access or access to all-file metadata.

In addition to the PDF being uploaded, the integration uses the connected Google account identity and authorization credentials, and file/folder information returned by Google that is needed to create the VeriCheck folder, place and manage report PDFs, and determine transfer status. Such information can include file and folder identifiers, names and upload responses. A filename containing Donor or report details also discloses those details to Google. We do not receive your Google password.

Google API information is used only for the authorized feature and is subject to the Limited Use commitments in section 3.4. Authorizing the Drive integration does not permit unrelated analysis of Drive content or give Veriport access to your Drive authorization.

Direct transfer and separate protection

Report PDFs go directly from your device to Google. Verify’s servers do not receive those PDFs as part of the Google Drive export. Google also processes the authorization and technical information needed to accept and secure the requests.

This statement concerns the Drive-export route. Separately enabling VeriCheck cloud backup can upload encrypted App content to Verify’s backup service; separately authorizing Veriport can send information to that service. Neither separate choice changes the direct-to-Google route used for Drive exports.

The files stored in Drive are readable report PDFs. They are not encrypted with VeriCheck’s backup recovery key. Google’s storage safeguards and the permissions on the connected account govern access to them. The backup encryption and key-recovery statements in section 4.1 do not apply to these externally stored reports.

Google stores and processes the Drive files under its applicable Terms of Service, Privacy Policy and any applicable Google Workspace agreement or administrator settings. The locations and retention arrangements for those files depend on the connected Google service and account. VeriCheck’s Canada/U.S. regional backup commitment does not determine the storage country of a connected Google Drive account.

The Customer must use an appropriately authorized account and control access, sharing, retention and any additional copies made through Google Drive. People or organizations given access through that account’s permissions may be able to view the reports. Connecting Drive does not replace any required Donor notice, consent, confidentiality safeguards or health-information agreement.

Turn off, disconnect, revoke access or delete files

You can turn off Google Drive export or disconnect it at any time in Settings → Integrations. This stops new exports through that connection. You can also remove VeriCheck’s access in your Google Account connections settings.

Files already saved in Google Drive stay there when you turn off the integration, disconnect it, revoke Google access or delete your VeriCheck account. Those actions do not recall an uploaded PDF, delete the VeriCheck folder, or delete the connected Google account. Deleting a local report or a VeriCheck cloud backup also does not automatically delete its Drive copy or exported revisions.

To remove exported PDFs and revisions, use Google Drive’s file-deletion controls, including its applicable trash and retention controls, or work with your Google Workspace administrator. Google’s and the Customer’s lawful retention requirements may apply. Disconnection does not remove recipients’ separate copies or alter processing already lawfully completed. App-side connection information is handled under section 9.

4.3 Optional Veriport integration

Separate service and authorization

Veriport is a test-management application operated by Veriport Inc. It is distinct from VeriCheck, which is owned and provided by Veriport Inc. You may choose to connect a Veriport account through the App’s integration functionality for the Customer’s authorized reporting and collection-management workflow.

The integration is optional. We do not send collection records to Veriport merely because you create a VeriCheck account, use Google Sign-In, enable cloud backup or connect Google Drive. A User must have the Customer’s authority to connect the receiving Veriport account and disclose the information involved.

Information, purpose and recipients

The integration handles the report or collection information covered by the transfer you authorize. Depending on the supported action and the content authorized, this can include report PDFs and revisions, Donor and Client details, collection and test details, results, comments, signatures, and photographs or attachments included in the transferred report or record. It also involves the account, organization or report identifiers, authorization information and delivery confirmations needed to connect the accounts and carry out the authorized workflow.

The information and recipient for the supported integration action must be identified before transfer, and any required authorization must be obtained. This policy does not authorize unrestricted synchronization of your whole device, access to unrelated records in Veriport, or undisclosed two-way data exchange.

Information you authorize for delivery is received by Veriport Inc. for the connected account and may be available to the receiving organization’s authorized users according to that account’s permissions and workflow. The purposes are the authorized report transfer, association with the appropriate testing record, and the Customer’s test-management activities—not unrelated advertising, sale of Donor data or general-purpose AI training.

Storage, access and the respective responsibilities

Transferred information is intended for processing in the receiving Veriport service. It is not the unreadable, recovery-key-protected backup described in section 4.1. Do not assume that the backup decryption limitations apply to the receiving service or its authorized users.

Veriport Inc.’s handling of received information is governed by its applicable Privacy Policy, its agreement with the Customer, account permissions and applicable law. Its legal role depends on those arrangements. Verify remains responsible for the processing and disclosures it performs; referring to Veriport’s policy does not waive Verify’s own obligations.

The storage country, access, retention and deletion arrangements for information delivered to Veriport must be confirmed for the connected Veriport service. VeriCheck’s regional backup commitment does not automatically extend to Veriport’s separate systems. Customers must not authorize a transfer where the receiving arrangements do not meet applicable laws, contracts, required agreements or Donor notices.

Disconnection and records already delivered

An integration may be disconnected using the applicable connection controls; contact VeriCheck for assistance. Disconnection ends further transfers under that connection. It does not automatically recall information already delivered, delete the Veriport account, or erase records that the receiving organization must retain.

Deleting your VeriCheck account does not itself delete a separately maintained Veriport account or records already delivered there. Requests concerning those copies should be directed to the receiving organization and, as appropriate, Veriport Inc. under its applicable privacy and service arrangements. Verify will address the information it holds and cooperate with requests as required by its role and applicable law. Ending one integration does not disable a different integration that remains authorized.

5. Canadian and U.S. data storage

Canadian customers’ VeriCheck-managed regional application data and encrypted backups are stored in datacentres in Canada. U.S. customers’ corresponding data and encrypted backups are stored in datacentres in the United States.

Customer account	Location of regional application databases and encrypted backup storage
Canadian Customer	Canada
U.S. Customer	United States

This arrangement applies to the regional account profiles and backup administration metadata we maintain, and to encrypted cloud copies of saved collection records, photographs, signatures, reports and configurations. It does not mean that we have readable cloud access to encrypted record content.

The allocation follows the Customer’s designated account arrangement. Customers operating across borders or requiring a particular arrangement should contact us before using the service. A storage-country change must be arranged with us and meet applicable legal and contractual requirements; a Donor’s nationality does not by itself change an account’s storage allocation.

Processing outside the regional storage arrangement

Firebase Authentication: authentication information is processed in the United States, including for Canadian accounts.
Apple services: Sign in with Apple, App Attest and iCloud Keychain may involve processing outside the Customer’s designated country under Apple’s service arrangements.
Approval and support: Zoho Mail, support correspondence and authorized support access may involve processing outside the Customer’s designated country.
Provider operations: relevant technical, security and administrative processing may occur on providers’ wider infrastructure. This does not give our staff the key to decrypt Customer backups.
Connected Google Drive: exported PDFs, their file/folder metadata and Drive authorization processing follow the connected Google account’s service arrangements. Its storage country is not selected by VeriCheck’s regional backup setting.
Connected Veriport: information delivered to Veriport Inc. follows the storage and processing arrangements for the receiving Veriport account. Confirm those arrangements before authorizing transfer; they are not an extension of Verify’s backup-storage promise.
Local and other independent copies: device records, other exports and copies created through other services follow the device location and selected service, not VeriCheck’s regional cloud-storage controls.

Information processed in another jurisdiction may be subject to that jurisdiction’s laws and lawful government-access requirements. We apply appropriate contractual and other safeguards and meet applicable cross-border requirements. Contact our Privacy Officer for information about providers and processing locations relevant to your account.

Customers must have a lawful basis for each collection, use and disclosure and obtain meaningful, express consent for sensitive information where required. Donors should receive understandable information about the testing purpose, information collected, recipients, retention, relevant backup, integration and storage arrangements, and their rights. Collect only necessary, legally authorized information.

Before enabling Google Drive export or Veriport transfers, the Customer must ensure that its notices and legal authority cover the receiving service and organization, the sensitive information involved, any relevant cross-border processing, and the separate retention of delivered copies. A User’s Google authorization or approval of an integration is not, by itself, the Donor’s consent or proof that the Customer may disclose the record.

The App’s signature feature records the wording presented with a signed collection record. A signature alone does not establish valid consent, and a collector’s acceptance of software terms is not consent from the Donor. The Customer must maintain accurate consent wording appropriate to its programme and applicable law.

For signed records, the App retains the statement shown with the signature. If a Donor refuses to sign, the App records the refusal but does not retain that consent wording. The Customer must separately preserve any notice, refusal or alternative authority it needs to document. A refusal to sign is not automatically consent or a legally defined refusal to test.

The App is intended for authorized professional and organizational Users, not children under 13. Information about a minor may only be entered by an authorized Customer where the applicable authority, notice, consent and safeguards are in place. We do not invite children to create professional accounts.

This policy does not itself make a testing programme HIPAA-compliant or satisfy every provincial or state health-information requirement. Do not use services for a purpose requiring an agreement or safeguards that have not been put in place. Encryption and regional storage do not remove legal duties that otherwise apply.

7. Service providers and disclosures

Providers used to operate VeriCheck

Provider	Relevant services	Information and purpose
Google	Firebase Authentication	Sign-in and account information, authentication credentials and relevant technical information for authentication and account security
Google	Firestore, Cloud Storage and Cloud Functions	Regional account information, backup metadata and encrypted backup content, as required for account administration, storage, restoration and service operations
Google and Apple	Firebase App Check and Apple App Attest	Attestation material and security tokens used to verify app/device integrity
Apple	Sign in with Apple and iCloud Keychain	Authorized sign-in information and optional synchronization of backup keys, respectively
Zoho	Zoho Mail	Necessary account-approval and support correspondence

For information processed on our behalf, we require contractual and other appropriate safeguards providing protection no less than that described in this policy and required by applicable law and Apple’s applicable privacy requirements. We limit provider access and use to the authorized services. Their access does not permit unrelated use of donor records or override restrictions on Google user data. Providers may separately process information in their own account or platform relationships under their own notices; that does not authorize Verify to expand its uses.

Services you choose to connect

Optional recipient	Information and purpose	Applicable distinction
Google Drive, in the account you connect	Report PDFs including revisions, account authorization and the file/folder information needed for the authorized export	PDFs are sent directly from your device to Google; Google’s account terms and controls apply to received copies
Veriport Inc., for the account you connect	Authorized report/collection information and the connection and delivery information necessary for the enabled workflow	A separate receiving application; its applicable Customer agreement, privacy notice and access controls apply

These are Customer-authorized integrations, not automatically enabled recipients of all App records. They are distinct from providers we engage to operate VeriCheck’s own account and backup services. The respective obligations depend on the actual processing role and agreements. Sections 4.2 and 4.3 explain the choices, data and consequences, and restrictions on Google API data continue to apply.

Customer-directed and legally required disclosures

A User may export or share a report with a recipient the Customer authorizes. The Customer is responsible for lawful recipient selection and disclosure. Do not interpret the ability to export as permission to disclose a Donor’s information to anyone.

We may disclose information on lawful, authorized Customer instructions; with valid consent; where legally required; or as otherwise permitted for an appropriate security or legal purpose, subject to this policy and applicable platform restrictions. A lawful request could require account information, metadata or encrypted files. It does not give us the ability to decrypt files for which we lack a key.

If a corporate transaction affects App information, applicable confidentiality, purpose, notice and consent requirements continue to apply. Any additional restrictions on transfer of Google user data also continue to apply; required prior consent must be obtained before a restricted transfer.

We do not sell or rent App personal information, disclose it for cross-context behavioural advertising or targeted advertising, or use donor records for marketing. We do not use donor records or Google user data to train generalized artificial-intelligence or machine-learning models.

8. Safeguards and security incidents

Our safeguards include iOS data-protection features for local storage, encrypted network transmission for service communications, provider access controls and encryption protections, and client-side encryption for cloud-backup content as described above. Authorized access to readable account information is limited to appropriate service, support, security and legal purposes.

The Customer must also protect its devices, passcodes, sign-in accounts, recovery keys, personnel access, connected-service accounts and exported reports. Integration authorization credentials must be protected and used only for the authorized service. Review the access permissions of connected Google Drive and Veriport accounts, especially when personnel or responsibilities change.

Encryption does not prevent access by someone who has obtained an unlocked device or the necessary credentials and keys, and the backup recovery key does not control already exported PDFs or delivered Veriport records. No system can guarantee absolute security. These limitations do not reduce our own legal or contractual security duties.

If we become aware of an actual or reasonably suspected compromise of Customer personal information in our services, we notify the affected Customer without undue delay and provide reasonably available information to support its response. We also make notifications and reports to individuals, regulators or others where required. Encryption is considered in assessing an incident; it does not automatically remove notification duties.

Report suspected account or information compromise to [email protected]. Do not include passwords, recovery keys or unnecessary Donor information in the initial email.

9. Retention and deletion

What we retain

Information	Retention approach
Local saved records and files	Remain on the device until removed; the Customer must apply lawful retention and deletion requirements
Encrypted cloud backups and saved historical versions	Remain until the cloud backup or account is deleted; local editing or deletion does not necessarily erase earlier backed-up versions
Account, approval and Google/Apple-linked sign-in information	Retained to administer the account until account deletion, subject to limited legally required retention and provider deletion cycles
Backup metadata and relevant operational information	Retained as needed to operate and protect the service, then deleted or appropriately de-identified, subject to the deletion and legal-retention provisions below
Approval and support correspondence	Retained for the account or request; associated personal information is included in account-deletion handling unless legally required to be retained or preserved
Integration authorizations, connection details and delivery metadata handled by the App or Verify	Used for the authorized connection and transfer functions; disconnection ends use of that connection, and information held by us is included in account-deletion handling, subject to the limited retention described below
PDFs and revisions already exported to Google Drive	Remain in the connected Drive account after disconnection or VeriCheck account deletion until removed there, subject to Google’s and the Customer’s applicable controls and retention requirements
Records already delivered to Veriport	Managed under the receiving organization’s and Veriport Inc.’s applicable arrangements; disconnecting VeriCheck or deleting its account does not automatically delete those received records
Limited deletion-processing records	An account identifier and deletion dates may be kept for up to 30 days to complete and verify deletion; identifying details are removed when no longer needed for that process, unless legally required to be preserved

Turning backup off and deleting a backup

Turning off VeriCheck cloud backup in Settings stops new uploads to that backup service. It does not delete existing backups. Delete Cloud Backup removes the account’s cloud backups from availability through the service when the operation completes and initiates their deletion. The account and local records remain. Re-enabling backup can upload remaining local records again.

These backup controls do not disable Google Drive export, disconnect Veriport or delete copies held by either service. Manage each integration separately using its connection controls; Google Drive controls are in Settings → Integrations.

Earlier backed-up revisions may continue to exist until the cloud backup or account is deleted. Customers needing deletion of a particular Donor record must account for those revisions and contact us where the available controls do not meet the applicable requirement. Do not use backup for a record that cannot be handled lawfully under the available controls.

Delete your account in the App

Use the in-app Delete Account feature to initiate permanent account deletion. Email or telephone contact is not required to start through that feature. We may require proportionate identity verification and confirmation to prevent unauthorized or accidental deletion.

Account deletion removes the sign-in account, regional account profile, encrypted backups and other associated personal information held by us, including relevant approval and support information, except information we are legally required to retain or preserve. This is different from signing out, uninstalling the App, disabling the account or deleting only a backup.

If completion requires additional processing time, we explain the expected completion time and confirm completion. Contact [email protected] if you cannot access the App or need assistance. Deleting a VeriCheck account ends use of integrations through that account and includes associated integration information held by Verify in the deletion described above. It does not delete your Google, Apple or separately maintained Veriport account. You may also revoke the external service’s authorization through that service’s account controls.

Account deletion does not erase report PDFs or revisions already saved in Google Drive, records already delivered to Veriport, Customer records remaining on devices, or other independently held copies. Those copies remain subject to the Customer’s and recipients’ applicable duties. Use Google Drive’s controls for its copies and the receiving organization’s/Veriport’s process for records held in Veriport. Verify will assist as required by its role and applicable law. Preserve records you are legally required to retain before requesting deletion.

Deletion timing and lawful exceptions

Removing data from availability through the App is not instantaneous physical erasure from every provider system. Deletion propagates through active systems, recovery periods and provider backups. Google’s published deletion processes for relevant Cloud and Firebase services can take up to approximately 180 days after the applicable provider deletion is initiated. This is a provider-system deletion period, not a promise that every account-deletion step takes 180 days or permission to keep using deleted information.

The provider-deletion period above concerns Verify-managed service data; it is not a retention or deletion promise for your independent Google Drive files or Veriport records. Their handling is described in sections 4.2 and 4.3.

Residual copies remain protected during deletion and are not used for ordinary service or marketing purposes. Legally required retention or preservation, such as mandatory incident records or a binding preservation obligation, may require particular information to be held longer. We restrict that information to the required purpose and delete or appropriately de-identify it when the requirement ends.

Deleting the App alone does not delete the account, cloud backup, Keychain items or independent copies. Removing Google authorization alone also does not perform account deletion. Without an available backup and a usable key, deleted local records may be unrecoverable.

10. Your choices and privacy rights

You can view and update your account and Company Profile in the App, manage device permissions in iOS Settings, enable or disable VeriCheck backup, delete a cloud backup and initiate account deletion. You can enable, turn off or disconnect Google Drive export in Settings → Integrations and manage an optional Veriport connection through its available integration controls. You can also remove Google authorization through your Google Account controls as described in section 3.4.

For already delivered copies, use the connected Google Drive account’s deletion controls or contact the receiving organization and Veriport Inc., as appropriate. Disconnecting a service and deleting the information it already received are different actions.

Depending on the applicable law, individuals may have rights to access information, receive a copy, correct inaccuracies, request deletion, withdraw consent, restrict or object to specified processing, or appeal a privacy decision. Rights are subject to applicable conditions and lawful exceptions. The App does not sell personal information or use it for targeted advertising.

For Donor collection records, contact the organization that collected the test, including when that organization has exported the report to Google Drive or sent it to Veriport. If you contact Verify, we will help direct the request and cooperate as required. We handle requests for information for which we are directly responsible. We cannot obtain readable collection content from an encrypted backup without the necessary key; that technical limitation does not cancel an individual’s legal rights or our duty to assist appropriately.

Send a request to our Privacy Officer at VeriCheck by post or by telephone using section 11. An authorized representative may act where permitted. We may verify identity or authority proportionately, without requesting unnecessary sensitive information. We respond within the legally required period and explain any permitted extension, refusal and available appeal. Where a right of appeal applies, use the subject “Privacy appeal” to request review.

We do not unlawfully discriminate against someone for exercising privacy rights. Withdrawal of consent may affect a feature that requires the information but does not invalidate earlier lawful processing or remove a mandatory retention obligation. You may complain to the Office of the Privacy Commissioner of Canada, an applicable provincial privacy authority or a competent U.S. regulator. No Ontario governing-law clause in a separate contract removes mandatory privacy rights in another applicable jurisdiction.

11. Changes and contact

We update the date above when this policy changes. Material changes are brought to Users’ attention through the App or account contact details. Before materially changing the use of personal information or requesting additional Google data, we provide notice and obtain any consent or authorization required by applicable law and platform rules. Continued use alone does not replace required consent.

Privacy Officer — Verify Diagnostics Inc.

122 Commerce Park Dr., Unit D

Barrie, Ontario L4N 8W8, Canada

Telephone: +1 705-812-4957 or 1-866-446-2953.

Connected-service information: Google Privacy Policy · Google Terms of Service · Google API Services User Data Policy · Veriport · Veriport Privacy Policy.