Aviya · Legal

Privacy Policy

Effective date: 18 October 2026

Aviya respects your privacy and is committed to handling personal information responsibly, securely and transparently.

This Privacy Policy explains how Aviya collects, uses, stores and shares personal information when you use the Aviya mobile application, our websites, account services, communications and related services.

1. Who we are

Aviya is operated by Saul Gibson (Private) Limited (“Aviya”, “we”, “us” or “our”).

For the purposes of applicable data protection law, Saul Gibson (Private) Limited is responsible for determining how and why personal information covered by this Privacy Policy is processed.

Privacy contact: legal@aviya.africa

2. Information we collect

The information we collect depends on how you use Aviya and which features you choose to use.

Account and profile information

When you create a Aviya account, we collect information including your:

name;
email address;
date of birth; and
sex.

Date of birth and sex are required to complete a Aviya account profile.

We use them to understand who uses Aviya.

You may also choose to provide:

a profile photograph;
your country; and
a contact phone number.

Your contact phone number is optional and is not verified. It is not used to sign in to or recover your Aviya account. Aviya does not currently use it to send automated SMS messages.

Google sign-in

If you choose to sign in with Google, Google provides our authentication service with your name, email address, Google account identifier and a link to your Google profile picture.

Aviya uses your name and email address to create or connect your Aviya account. Your name may be used to pre-fill your Aviya profile.

Aviya does not use your Google profile photograph as your Aviya profile photograph.

Farm and Batch information

When you use Aviya to manage poultry operations, we process information you choose to enter about your farm and Batches.

This may include:

farm or location names entered by you;
Batch names and dates;
bird numbers;
chick supplier information;
bird losses;
bird weights and observations;
feed and supply records;
sales and financial records;
planned selling information; and
other operational records you choose to maintain in Aviya.

Aviya does not use your phone’s device location to determine your farm location.

Some farming information may relate primarily to a farming operation rather than to an individual. It may nevertheless constitute personal information where it can reasonably be associated with an identifiable person.

Shared Batches and team information

Where multiple people participate in a shared Batch, we process information about:

Batch owners and team members;
invitations;
roles and permissions;
actions performed by team members;
timestamps; and
Batch activity history.

This allows Aviya to provide shared access and maintain a record of who performed particular actions.

Team Chat

If you participate in Team Chat within a shared Batch, Aviya stores the messages you send together with information such as the sender, Batch and time of the message.

Before sending your first Team Chat message, you must accept Aviya’s Chat Rules.

Batch members can report messages or members and can block another member’s messages from their own view.

Where a report is made, Aviya may process:

the reported message;
the reporter and reported account;
the relevant Batch;
the reason for the report;
the time of the report; and
actions taken by authorised Aviya support staff.

Authorised Aviya support staff may review reported content and may hide messages that breach Aviya’s rules.

When a message is hidden, it is no longer shown to members of the Batch. The message may remain on Aviya’s systems and be accessible only to specifically authorised support staff for moderation, safety and record-integrity purposes.

Chat messages are otherwise retained as part of the shared Batch record. Moderation reports, case history and staff decisions are retained for 24 months after the relevant case is closed.

Aviya may update these retention practices as moderation controls develop and will update this Privacy Policy where the change materially affects users.

Invitations

When a Batch Owner invites another person using an email address, Aviya stores that email address with the invitation.

If the invited person does not already have a Aviya account, the invitation can be accepted after that person creates an account and verifies the same email address.

Unaccepted invitations are automatically deleted approximately 30 days after they are created. If the Owner cancels an unaccepted invitation, it is deleted earlier.

When an invitation is accepted, the invited email address is removed from the invitation record and the invitation is linked to the Aviya account instead.

Aviya does not currently send invitation emails to invited people. The Batch Owner communicates the invitation separately.

Environment sensors

If Aviya has linked a supported temperature and humidity sensor to your account, Aviya stores:

the sensor identifier linked to your account;
the most recent temperature reading;
the most recent humidity reading;
the time of that reading; and
the sensor’s online status where available.

The readings are obtained through the sensor manufacturer’s cloud service.

Aviya stores only the most recent sensor reading. Each new reading replaces the previous one; Aviya does not currently retain a history of sensor readings.

Communications and support

If you contact Aviya, we may process messages, support requests, feedback, correspondence and other information you choose to provide.

Authorised members of Aviya’s support team can view the account information reasonably necessary to help you, investigate problems and review reports using an internal support tool.

Only staff specifically authorised by Aviya have this access.

Marketing and subscription information

If you join a waitlist, subscribe to Aviya updates or choose to receive marketing communications, we may process information such as your name, email address, subscription status and communication preferences.

Marketing from Aviya is optional.

Where a marketing option is presented during Aviya account registration, it is not selected by default. Leaving it unticked means that you have not opted in.

You can change your marketing preference later in Aviya Settings.

Aviya does not currently send marketing emails through the mobile application.

Technical information

We process limited technical information needed to operate and secure Aviya.

This may include:

network or IP address information processed by our hosting and authentication services;
request times;
application version;
device or browser information supplied with service requests;
Aviya installation identifiers associated with synchronised records; and
sign-in and security events.

Diagnostic information generated by the Aviya mobile application for local troubleshooting remains on the device unless you deliberately provide it to Aviya.

Aviya does not use your device’s location.

Aviya’s reminders, such as weekly milestones and weigh-in reminders, are generated on your phone. Notifications about activity in your shared Batches are described under Notifications below.

Notifications

If you are signed in to a Aviya account and your phone allows Aviya notifications, Aviya can notify you about activity in the shared Batches you belong to — for example, a Team Chat message, a bird loss logged by another member, an invitation, a change to your membership or role, a change of Batch ownership, or a Batch being closed or finalised. You are not notified of your own actions.

These notifications are delivered through Firebase Cloud Messaging, a service provided by Google. To deliver them, Aviya processes:

a device push token, issued by Firebase Cloud Messaging for the Aviya app on your phone;
the Aviya installation identifier, the device platform and the Aviya app version, which Aviya stores with the push token against your account;
an installation identifier that Firebase creates for the Aviya app on your phone so that notifications reach the right installation; and
your Aviya account identifier — an internal code, not your name, email address or phone number — which is included with each notification so that your phone can confirm the notification belongs to the account signed in on it. It is used only for routing and security, is not shown in the notification and does not form part of your profile.

A notification contains only what is needed to deliver it: the type of activity, the Batch it relates to and, for Team Chat messages and bird losses, the first name of the member involved (and, for a role change, the new role). Notifications do not contain the text of Team Chat messages, financial amounts or email addresses, and Aviya does not use notifications for marketing.

Aviya uses Firebase Cloud Messaging only to deliver notifications. Aviya does not use Firebase for analytics or advertising.

Your push token is linked to your account while you are signed in and your phone allows Aviya notifications, and is updated when it changes. It is unlinked when you sign out, when you turn off Aviya notifications in your phone’s settings, or when a different account signs in on the phone; the new account is linked only after it has signed in. Turning off an individual type of Aviya notification in your phone’s settings does not unlink your phone. Push tokens are deleted when you delete your Aviya account, and tokens that have not been refreshed for 60 days are removed by Aviya’s regular clean-up.

3. Local and cloud storage

Some Aviya functionality can operate locally on your device.

Information created while using Aviya offline may remain on that device until it is synchronised, deleted or the application data is removed.

When you use a Aviya account, cloud functionality, a shared Batch or another feature requiring online services, relevant information is transmitted to Aviya’s online services.

Information created offline may be transmitted later when the device reconnects and synchronisation occurs.

Aviya application data is excluded from normal Android device backup where supported by the application configuration.

4. How we use information

We use personal information where reasonably necessary to:

create and manage Aviya accounts;
authenticate users;
provide the Aviya application and account services;
maintain farm and Batch records;
enable collaboration between authorised Batch members;
synchronise information between devices;
record which authorised user performed an action;
provide Team Chat;
moderate reported content;
provide reminders and notifications;
display supported environmental sensor readings;
manage subscriptions and communication preferences;
provide customer support;
respond to enquiries and feedback;
maintain and improve Aviya;
diagnose technical problems;
prevent fraud, spam, misuse and unauthorised access;
protect Aviya and its users;
maintain necessary operational and security records; and
comply with legal and regulatory obligations.

We do not sell your personal information.

5. Our basis for processing information

Depending on the circumstances and applicable law, we may process information:

with your consent;
where processing is necessary to provide a service you have requested;
where necessary to administer your Aviya account;
where necessary to fulfil our obligations to you;
where necessary for Aviya’s legitimate interests, such as operating and securing the service, provided those interests do not improperly override your rights;
where necessary to protect the legitimate interests of other authorised users of a shared Batch; or
where necessary to comply with legal or regulatory obligations.

Where processing depends on consent, you may withdraw that consent subject to applicable law.

6. Shared Batches and visibility to other users

Aviya’s shared Batch features are designed for collaboration.

If you participate in a shared Batch, other authorised members may be able to see information such as your:

name;
profile image;
role;
messages; and
activity associated with that Batch.

Actions you perform may be recorded with your identity so authorised team members can understand what happened, who performed the action and when.

Shared Batch information is not made publicly available merely because more than one member has access to it.

7. Who we share information with

We use service providers to help operate Aviya.

Our principal service providers currently include:

Supabase, for authentication, database services, file storage and server functions. Aviya’s primary Supabase project is hosted in Frankfurt, Germany;
Google, where you use Google sign-in, for distribution of the Android application through Google Play, and for delivering Aviya app notifications through Firebase Cloud Messaging;
Cloudflare, for parts of Aviya’s web infrastructure, including Aviya account and internal support services;
Resend, for transactional and account-related email delivery; and
Tuya, where a supported environmental sensor is linked to your Aviya account.

Our public website, aviya.africa, is hosted by a website hosting provider and uses Google Analytics to understand how visitors use the site. If you join our waitlist or newsletter, your details are managed by an email marketing provider. These website services are separate from the Aviya app.

Service providers receive only the information reasonably necessary for the services they perform.

We may also disclose information:

where required by law or a lawful request from a competent authority;
where necessary to establish, exercise or defend legal rights;
where necessary to protect Aviya, its users or others from fraud, abuse or security threats; or
as part of a legitimate corporate transaction, subject to appropriate protections.

8. International processing

Some Aviya service providers process or store information outside Zimbabwe.

Where personal information is transferred internationally, we take reasonable steps to ensure that the transfer is handled in accordance with applicable data-protection requirements and that appropriate safeguards are used.

This includes providers in the European Union and the United States.

9. Marketing communications

Marketing communications from Aviya are optional.

If you choose to receive them, you may later withdraw that choice through the controls Aviya provides or by using an unsubscribe mechanism contained in the communication.

Your marketing preference is retained while your account exists and is deleted when your account is deleted.

Unsubscribing from marketing does not prevent Aviya from sending important account, security or service-related communications.

10. Cookies and browser storage

Aviya websites may use cookies or browser storage where necessary to operate websites, authenticate users, remember preferences and protect services against misuse.

The Aviya account website uses browser local storage to maintain the user’s authenticated session.

Our public website, aviya.africa, uses Google Analytics, which sets analytics cookies to help us understand how visitors use the site. Non-essential cookies are used only in line with the choices you make in our cookie banner. Messages sent through our website contact form are delivered to support@aviya.africa.

The Aviya app does not contain advertising or analytics software.

11. How long we keep information

We retain personal information only for as long as reasonably necessary for the purpose for which it was collected or where retention is otherwise permitted or required by law.

Current Aviya retention practices include:

Account and profile information: retained while your account exists, subject to the account-deletion rules below.
Batch and operational records: retained while needed to provide the relevant Batch and shared history.
Team Chat messages: retained as part of the relevant shared Batch record.
Unaccepted invitations: automatically deleted approximately 30 days after creation, or earlier if cancelled.
Closed support and moderation cases: reports, case history and staff decisions are retained for 24 months after the case is closed.
Account-deletion record: a minimal record containing the internal account identifier and deletion time is retained for 24 months.
Marketing preference: retained while the account exists and deleted with the account.
Notification registrations: a phone’s push token is kept while that phone is registered for Aviya notifications, is removed as described under Notifications in Section 2, and is deleted after 60 days without being refreshed.
Notifications waiting to be delivered: deleted after 7 days.
Hosting and authentication logs: retained for the limited periods applied by the relevant service provider.
Information stored locally on a device: may remain on that device until it is deleted, the application data is removed, or Aviya is able to apply a deletion during later synchronisation.

12. Account deletion

You can request deletion of your Aviya account:

in the Aviya application through Account › Delete account; or
through Delete your account online.

Account deletion requires verification using a code sent to the email address associated with the Aviya account.

If you own a shared Batch with other members, you must transfer ownership before deleting your account.

When your account is deleted, Aviya deletes personal account information including your profile, contact information, date of birth, sex, marketing preference, profile photograph, linked sensor information, the registrations of your phones for Aviya notifications and any notifications naming your account that are waiting to be delivered.

A Batch in which you are the only member is deleted from Aviya’s servers as part of account deletion.

Shared Batch history

Where records or messages you contributed form part of a shared Batch used by other members, the shared operational history may remain.

Aviya keeps a limited internal account number where necessary to preserve the integrity of shared Batch history relied on by other members.

After deletion, that number is no longer associated in Aviya with your name, email address, profile photograph or profile information and cannot be used to sign in to the deleted account.

Your surviving shared records are presented to other members as belonging to a Former member rather than displaying your deleted Aviya profile.

Names that were manually typed into legacy or offline records and were not technically linked to your signed-in account may remain because Aviya does not automatically identify personal information by matching names entered into free-text or legacy records.

Copies stored on phones

Aviya can only update or erase information stored locally on a device when that device reconnects to Aviya while the relevant deletion information remains available.

We cannot remotely erase a device that never reconnects.

Information already synchronised to another authorised Batch member’s phone may therefore remain locally until that device reconnects, clears its Aviya data or otherwise receives the updated shared record.

13. Security

We use technical and organisational measures designed to protect personal information against unauthorised access, accidental loss, improper alteration, unauthorised disclosure, misuse and destruction.

Personal information transmitted between Aviya applications, websites and online services is protected in transit using encrypted connections such as HTTPS/TLS.

Other safeguards include authentication, access controls, restrictions on administrative access and security controls appropriate to the information being processed.

No internet-connected system can guarantee absolute security.

Where applicable law requires notification of a personal-information breach, Aviya will make the required notifications.

14. Your privacy rights

Subject to applicable law, you may have the right to:

ask whether we hold personal information about you;
request access to personal information we hold;
request correction of inaccurate or incomplete information;
object to certain uses of your information;
withdraw consent where processing depends on consent;
object to direct marketing; and
request deletion of personal information where deletion is appropriate.

Privacy requests can be sent to:

legal@aviya.africa

We may need to verify your identity before acting on a request.

Some rights are subject to legal limitations and do not necessarily require Aviya to delete information that we have a legitimate and lawful reason to retain.

15. Children

Aviya is not designed or directed primarily to children.

We do not knowingly seek to collect personal information from children in circumstances where parental or guardian involvement is required by applicable law.

If we become aware that personal information relating to a child has been collected contrary to applicable requirements, we will take appropriate steps to address it.

16. Third-party services and links

Aviya may provide links to or integrations with independent third-party services.

Where you interact directly with an independent third party, that organisation may process information under its own terms and privacy policy.

We encourage you to review the privacy information provided by those services.

17. Privacy concerns and complaints

If you have a question or concern about how Aviya handles your personal information, contact:

legal@aviya.africa

You may also have the right to raise a complaint with the relevant data-protection authority.

In Zimbabwe, data-protection regulatory functions are exercised by the Postal and Telecommunications Regulatory Authority of Zimbabwe (POTRAZ) under applicable data-protection legislation.

18. Changes to this Privacy Policy

Aviya will continue to develop and our information practices may change.

We may update this Privacy Policy to reflect changes to:

Aviya features or services;
information we process;
technology and service providers;
legal or regulatory requirements; or
our privacy practices.

The current version and effective date will be published on aviya.africa.

Where a change materially affects how we use personal information, we will take reasonable steps to bring the change to your attention where appropriate.

19. Contact

For privacy questions, requests or concerns:

Saul Gibson (Private) Limited
Email: legal@aviya.africa