What information AgProve handles, and why.

The public website

The website at agprove.org is a static company website. It has no visitor accounts, contact form, analytics, advertising, tracking pixels or non-essential cookies. Its only script is machine-readable company information that does not run in your browser.

The Contact link opens your own email application. The website does not receive what you type. If you email AgProve, we use the contact details and information you choose to send to answer your enquiry and manage any resulting trial-service relationship.

Cloudflare delivers the website and necessarily processes ordinary web requests, such as the requested page, IP address, browser details and request time, to deliver and protect the service.

The AgProve Trial Manager

The Sign in link opens the authenticated Trial Manager at trials.agprove.org. The application records agricultural trial work and makes permitted records available to AgProve staff and authorised client users.

Depending on a person's work and access, the application handles:

• account email, name, sign-in identity, organisation membership, role and assigned access;
• trial plans, sites, treatments, operations, assessments, notes, photographs and files;
• an audit history showing who changed a record and when; and
• personal notification and calendar settings.

This information is used to plan and perform trials, coordinate authorised work, maintain an auditable record, synchronise work between devices and provide trial evidence to the relevant client. The application applies organisation, client, site and role-based permissions before presenting hosted records.

Hosted account and trial information is kept in AgProve's Supabase project in Ireland. The application can also keep an offline working copy in IndexedDB on the device used to sign in. Encrypted recovery copies are stored separately through Cloudflare's storage service.

Google account and Calendar information

Google sign-in

If you choose Continue with Google, AgProve receives the basic Google identity information needed to sign you in: your account identifier, email address and basic profile. It is used to establish your Trial Manager account and session and to match an invitation or existing membership. Google sign-in does not by itself grant Calendar access.

Optional Google Calendar connection

Calendar access starts only when a signed-in person separately chooses to connect a Google Calendar. The requested permission depends on the sync mode they select: read-only access for an inbound connection, or Calendar read-and-write access when they ask AgProve to publish or synchronise trial dates.

For that user-facing calendar feature, AgProve can:

• read the calendars available to the connected account and use the primary calendar, or another usable calendar if no primary calendar is available;
• read event identifiers, titles, dates or times, all-day status and Google event links in the relevant synchronisation window;
• show imported personal calendar entries beside permitted trial dates in that person's own Trial Manager calendar; and
• create, update or remove AgProve trial events in the connected Google Calendar when the selected mode allows writing.

Storage and sharing of Google data

AgProve stores connection details and the imported event fields listed above in the hosted Trial Manager database. The continuing Google permission is held server-side in Supabase Vault; it is not placed in the browser or shown to other Trial Manager users. Google data is exchanged with Google and AgProve's hosting provider only to operate, secure and support the calendar feature requested by the user.

AgProve does not sell Google user data, use it for advertising or credit decisions, give it to data brokers, or use it to train a general-purpose artificial-intelligence or machine-learning model. AgProve's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting

A person can disconnect their calendar from the Trial Manager. The disconnect process revokes AgProve's Google permission, deletes the stored refresh token and removes copied external-calendar entries from AgProve. Events that AgProve previously wrote to the Google Calendar remain there and can be removed in Google Calendar.

Services involved

AgProve uses Cloudflare for the public website, DNS and encrypted recovery storage; Supabase for Trial Manager authentication, database, file storage and server functions; and Zoho for AgProve email. Google or Microsoft is involved only when a person chooses the corresponding sign-in or calendar service.

Your choices and questions

You do not have to connect a personal calendar to use the Trial Manager. You can disconnect a connected calendar in the application and can withdraw AgProve access from your Google Account permissions.

To ask what personal information AgProve holds about you, request a correction or deletion where applicable, or raise a privacy concern, email contact@agprove.org.