Veylo Privacy Policy

Last updated: 29 October 2026.

1 Who we are and this policy

Veylo is operated by John Tawadros personally, based in Queensland, Australia (we, us or our). Contact support@joinveylo.com about privacy, access, correction, safety or deletion. Veylo is currently free, personally funded and not monetised.

This policy covers the Veylo iOS and Android apps, related websites and account-confirmation pages, support and moderation, and separate launch and early-access signup records. Some older records may use the name UniPulse. Veylo is for people aged 18 years or older based in Australia. Features and controls can differ between supported app versions and platforms.

This policy explains information handling. Accepting Terms or acknowledging a policy does not give blanket consent to every use of information. We will obtain separate consent where required by law.

2 How information is collected

We receive information when you register, sign in, edit your profile, use social features, enable permissions, submit feedback, make a report or contact us. Other people can provide information about you in messages, shared content or reports. The app and providers also generate identifiers, timestamps, delivery information and technical logs. We can derive a campus label from location or an affiliation indicator from an email domain.

Required registration fields are needed to complete the registration flow. Photos, device location, notifications, social text and support correspondence are optional, although a feature cannot work without the information it needs. Do not include unnecessary sensitive information about yourself or another person.

3 Accounts profiles and study information

We collect account email, first and last name, a password for authentication, and the requested university, campus, degree or course and year-level information. A custom course description may be provided where the catalogue is unsuitable. A student email is optional and may default to your account email. Optional study-focus information can include a major or specialisation.

Supabase handles authentication and generates account, confirmation, sign-in, session and recovery information. Passwords are not displayed as profile fields. Supported native versions store sessions using device storage, including operating-system protected storage. Confirmation and recovery links can pass through email and a hosted page before returning to the app. We retain relevant settings, onboarding information and records of the policy version actually accepted and the acceptance time.

Names, study details, approved photos and affiliation indicators can be available to eligible signed-in users under the feature's access and blocking rules. Your surname is not necessarily private, and profile information is not all limited to friends. Account and student emails are not ordinary public profile fields. Optional study focus currently uses a private account-specific feature.

A university indicator is limited information, not proof of identity, age or current enrolment or university endorsement. Selecting a university does not itself cause us to send your private account information to that university.

4 Profile photos

Optional photo submissions include an image file, storage reference, file type, status and review information. Images can contain embedded metadata, including precise location or GPS coordinates if present. Do not assume that the picker, editing or upload process strips it.

New submissions are stored privately for manual suitability review. You and authorised operators and storage or review providers can access the submission as needed. A pending submission does not replace an approved profile photo before approval. Review is not an age or identity check.

Approved photos use public image links. Someone who obtains a link can view, copy or save the image without signing into Veylo. Removing a profile reference does not necessarily remove the underlying file. Pending, rejected, replaced and older approved files can remain and require separate removal work. There is no assured automatic deletion deadline for these files. Account deletion requests include photos, but we do not promise immediate removal of every stored or cached copy. Contact us about a remaining photo or link.

5 Location status and activity

Location is optional. Depending on your selected mode and OS permissions, the app can use location for a requested check, when opening the app or for background campus detection. Background detection can run while the app is not open when permission permits.

The ordinary campus-status feature uses device coordinates locally to derive campus or zone presence. It sends derived campus or zone labels, presence, status information and timestamps to the backend rather than an ordinary trail of raw GPS coordinates. Images, messages or other content you share can separately reveal location.

We keep current status, campus or zone, activity or availability choices, optional text or emoji, and timestamps for freshness, reminders and expiry. Friends, campus, university or private audiences and other privacy controls apply to particular features. Campus or university audiences can include friends; older versions can offer different audiences. Turning off discovery does not hide every profile field. Turning off visibility is different from revoking OS permission or removing previously shared information.

Status can be stale or inaccurate. Display expiry can clear current status while timestamps and notification copies remain. Do not rely on a status as proof of someone's whereabouts, attendance or safety.

6 Social features messages notifications and local storage

We process friend requests, friendships, blocks, group memberships and related timestamps to provide connections and access controls. These records describe your Veylo social graph; they are not a phone address-book import feature. Search terms are sent to the backend to return permitted people-search results, and request counts and timestamps can be kept for abuse control. We do not maintain a search-history list for ordinary friend searches; request counts and technical records are distinct from a history of search phrases.

Posts, comments and reactions include content, author, campus or category and timestamps. Feed audiences can extend beyond friends. Direct and group text conversations include message text, participants, group names, roles, mute or leave settings and read state. Current messaging does not provide a general attachment-upload feature.

Messages are stored and processed on our servers and are not end-to-end encrypted. Conversation participants can see the relevant messages. Authorised operators and providers can process server-held information for service operation, support, safety investigations or legal requirements.

If notifications are enabled, we process push tokens, platform, installation-related identifiers and preferences. Notification providers receive the token and payload, which can include a sender's name, message preview, status or campus information and routing identifiers. Expo passes native notifications to Apple's iOS delivery service or Google's Android delivery service. Lock-screen visibility depends on the receiving device. Muting, changing preferences or deleting content does not retract already delivered previews or other recipients' stored notification copies.

The app keeps local preferences and caches that can contain profiles, feed and chat content, previews, relationships and status. Cache expiry is not proof of physical device deletion. You can use available edit, audience, block, post-deletion, leave and mute controls. Not every comment or message has an individual deletion control; contact us about content you cannot remove. Other people may independently save, quote or screenshot information shared with them.

7 Safety moderation feedback and support

Reports can contain reporter and target information, reasons, optional details, content location and submission time. Review records can contain decisions, reasons, reviewer information and action history. We use them to assess concerns, apply our Terms, consider appeals and meet applicable requirements. Restricted operator systems and relevant hosting providers process photo reviews, reports, feedback and deletion requests.

We will not reveal a reporter's identity to the reported user without agreement unless required by law. Incident details may nevertheless allow an identity to be inferred. We may need to explain enough of an allegation for a person to respond while protecting others' privacy and safety.

Feedback and course suggestions can include text, screen or issue details and technical app, platform, OS or execution context. Email correspondence, sender details and lawful attachments are held separately from the app database. John handles requests; authorised backup assistance may access support or moderation information when needed.

Use available in-app reporting or email support@joinveylo.com, including if a target or form is unavailable. Never send passwords, sign-in codes or recovery tokens. Do not download, forward or attach child sexual abuse material; give a lawful description and content location instead.

We will provide an initial human response to safety complaints and deletion requests in less than 48 hours, including weekends. This begins or explains handling, rather than promising investigation, resolution or deletion completion within that interval. It does not delay urgent legal duties. See support and child safety.

8 Technical information websites and email lists

The app, authentication, hosting and delivery providers process IP addresses, request and error metadata, device or browser information, app and runtime versions, installation identifiers and delivery or security logs. Backend gateway and function logs can retain account-associated request information together with service-response and execution durations. We use this for reliability, troubleshooting and security.

Expo provides app-update delivery. Requests can carry a persistent installation identifier and technical version information, and can include text about a previous fatal application error. Update-request usage is also aggregated to understand app use. These activities are distinct from advertising tracking. A disabled optional app diagnostic feature does not mean that native update or backend logging stops.

Our public pages use GitHub Pages and Vercel. Loading them sends ordinary request information to the host, including IP address, requested URL and, where supplied by the browser, referrer and browser information. GitHub Pages logs visitor IP addresses for security. The main marketing homepage uses Vercel Web Analytics for visit measurement, including page URL, referrer, time, approximate location, browser/device information and a request-derived visitor identifier. The homepage filter limits its pageview events and removes URL queries and fragments; this is not a guarantee that every field, such as referrer, is removed. The legal and support pages in this publication contain no optional analytics scripts, but hosting/security logs still apply. Account-confirmation pages and restricted administration have their own authentication and operational processing.

Launch and early-access signup lists are separate from app accounts. They can contain email, signup identifier and time, requested intent, platform, source, recorded consent where actually obtained, and delivery or rate-control information. We use them for requested launch/access communications, acknowledgements, delivery and abuse prevention. Older entries do not establish fresh consent. App-account deletion does not automatically delete those separate records.

Resend handles authentication and requested signup emails, including addresses, content and delivery information. Depending on the sending configuration, email systems can also produce open or click measurements; we do not promise all email paths are free of such measurement. This is different from using information for cross-company advertising. You can ask us about a sending path, withdraw requested launch messages through an available unsubscribe link or contact support. We will honour applicable withdrawals within the time required by law. An appropriately limited suppression record can be needed to respect an opt-out; necessary security or account-service messages may still be sent.

9 Purposes and automated processing

We use information to create and secure accounts, provide chosen features and audiences, deliver messages and notifications, support recovery and deletion, review photos and reports, handle complaints and appeals, improve reference information and diagnose reliability. University/account information can also tailor an existing feature, such as the My university feed view.

Rule-based processes can screen submitted text, derive affiliation indicators, estimate campus presence, apply audience and interaction rules, limit repeated requests, choose permitted notification recipients and stop displaying expired content. They use the text, account/study information, device-derived location, relationships, settings, request history and timestamps described above. Rules can reject a submission or prevent an action you intended; they can make mistakes. Email support to request review or correction.

Photo suitability and report assessment involve human judgment. Rule-based text screening is not a Veylo-operated generative-AI moderation service. Providers can perform their own security and abuse-detection processing. A record of an action, a queued request or an expired display is not proof that a human response, a sanction or complete disposal occurred. This policy does not promise automatic complaint reminders or automatic retention cleanup.

We do not sell personal information, serve advertising in the Veylo app or use Veylo app information for cross-company advertising tracking. This does not mean that providers receive no information or that technical/website analytics do not occur. We will obtain required permission before marketing and provide an appropriate way to stop it.

10 Sensitive information and information about others

Ordinary registration does not require health, racial or ethnic origin, religion, political views, sexual orientation or similar sensitive information. Messages, images, statuses, reports and support correspondence can nevertheless reveal it. Only provide relevant information you can lawfully share. Another user's acceptance of Terms is not consent on behalf of a person described in their content.

We will explain a particular request for sensitive information and obtain consent where required or rely on a specific lawful exception. Unexpected information will be assessed for whether it can lawfully be kept, used or should be removed or de-identified.

11 Providers recipients and overseas processing

Information is shared with the relevant users or audience and providers needed to host, operate, secure and support Veylo. Authorised operators and advisers can access information for a relevant service, safety, technical or legal purpose.

Some processing therefore occurs outside Australia. Primary database regions do not identify every log, backup, support or subprocessor location. Wider provider lists do not mean Veylo uses every listed service. We do not claim every provider's ancillary location is known. Contact us for information about a particular service.

We will take steps required by applicable law when choosing providers or disclosing information overseas. Acknowledging this policy is not permission to avoid those obligations. We can disclose limited relevant information where law requires it or where law permits and it is reasonably necessary to address a serious safety concern, investigate unlawful activity or protect legal rights. We will assess scope and basis. We may also disclose at your request or with valid consent. An operational transfer requires appropriate safeguards and notice and does not authorise unrelated new uses.

12 Security and breaches

We use authentication, access controls, HTTPS communications and separation of private review material from approved public photos. These measures do not make public photo links private or messages end-to-end encrypted. We take reasonable steps to protect information against misuse, interference, loss and unauthorised access, modification or disclosure. No online system is completely secure.

We will assess suspected breaches and notify people and authorities when applicable law requires it. Contact support promptly about suspected account or information compromise. Do not send a password or reusable authentication credential.

13 Account deletion and other removal requests

Open Profile > Settings > Delete account and follow the account-ownership and confirmation steps shown. If that route is unavailable, you cannot sign in or need help with separate records, email support@joinveylo.com. Use the account email where possible; a sender address alone is not proof of authority. We may need proportionate ownership checks before acting. Do not send unsolicited identity documents or authentication secrets. A request can be made without explaining why you are leaving.

We will give an initial human response to deletion requests in less than 48 hours, including weekends. Completion may need checks, work across systems or review of a specific lawful retention requirement. We will explain relevant next steps and remaining work unless law prevents that explanation. Uninstalling or signing out is not account deletion. See account deletion.

14 Retention remaining copies and backups

Information is kept for relevant service purposes, your choices and particular lawful safety, legal or operational needs. Where it is no longer needed and no applicable requirement justifies retention, we will take reasonable steps to delete it or make it no longer reasonably identifiable. There is no universal legal retention period or all-copy erasure deadline for every category.

A deletion request covers the sign-in account, profile, status, friendships and memberships, authored posts, comments and sent messages, settings, notifications, push tokens and photos. Processing can fail, be incomplete or require separate work. A confirmation message, missing profile, unavailable image link or administrative status is not proof that every step or physical/provider copy has been erased.

These distinctions remain important:

• Photos: a removed profile reference or completed review does not necessarily remove public images, private originals, rejected or replaced files, caches or other copies. Pending files do not have an assured automatic deletion deadline.
• Shared and delivered material: other participants' content, shared group information, recipients' notification text and independently saved screenshots or copies can remain. We cannot automatically recall independent copies.
• Safety and operational information: reports by others, moderation reasons, feedback, course suggestions, device context, installation records and necessary request/verification/action history can require separate review. Free text and linkable identifiers are not anonymous simply because an account link is removed.
• Separate services: support correspondence, signup lists, mail delivery/security records, provider logs, device caches, exports and backups have separate lifecycles. Some remaining records have no automatic expiry and need individual review.

A particular law, order or lawful preservation requirement can require specified information to be kept. Limited information can also be necessary for a lawful complaint investigation, appeal, serious recurrence prevention or legal claim. We will assess necessity, restrict access and review continued need. This does not justify keeping an entire account indefinitely or assigning a blanket multi-year safety period.

Mailbox deletion, recoverable folders, synced/exported copies and provider backups can differ. We cannot give a verified universal date for erasure of all provider/recovery copies. A backup is not a general exemption from privacy obligations. Copies within our control remain subject to the steps required by applicable law when no longer needed, including addressing deletion and withdrawal choices if information is restored. Contact us to request review of a remaining photo, record or correspondence.

15 Access correction and privacy complaints

You can edit available profile/settings fields or email support for access, correction or review of information you cannot remove yourself. We may need reasonable identity checks and enough detail to locate it. We respond within a reasonable period and any applicable legal timeframe. There is no charge to make an access/correction request or correct information. We will explain any lawful reasonable access charge before proceeding.

If law permits or requires a limit, including to protect another person's privacy or an investigation, we will explain a refusal and complaint options to the extent permitted. Where appropriate you can ask us to record that you dispute accuracy.

For a privacy complaint, explain what happened and the outcome sought. We will consider it fairly and communicate the outcome and next steps. The less-than-48-hour initial response applies to safety complaints and deletion requests, not resolution of every privacy matter. You may contact the Office of the Australian Information Commissioner, which can advise whether it has jurisdiction. Other consumer, safety and legal options remain available. We do not claim an exemption from applicable privacy duties merely because the service is personally funded.

16 Age eligibility and younger people

Veylo is for people aged 18 or older based in Australia. Ordinary registration does not collect date of birth or provide government-ID or selfie age verification. A store rating, Terms acceptance, university indicator or reviewed profile photo is not independent proof of age.

Report a suspected under-18 account through the app or support email. We will review the concern, take appropriate steps to restrict or close an ineligible account and address information that should no longer be held. A safety concern can require separate lawful handling after account closure. Our child safety standards apply to content and conduct even though children are not eligible users.

If a different age-assurance process is introduced, we will explain its information, providers, purposes and safeguards before collecting through it and comply with applicable requirements.

17 Updates and contact

We will update the date on this policy when practices change and give appropriate notice of material changes. New processing requiring consent will be addressed separately from accepting Terms. This page does not certify that a new policy version has been accepted by an existing account.

Contact John Tawadros at support@joinveylo.com. See Terms, support and appeals, account deletion and child safety.