Privacy Policy

1. Who We Are

Relay ("Relay", "we", "us", or "our") is a communication and work-collaboration application operated by:

[LEGAL ENTITY NAME]

[REGISTERED / BUSINESS ADDRESS]

Privacy contact: [PRIVACY CONTACT EMAIL]

Account deletion / privacy request page: [ACCOUNT DELETION OR PRIVACY REQUEST URL]

This Privacy Policy explains how Relay handles information when you create an account, communicate with other users, participate in companies or workspaces, use projects and tasks, make calls, upload files, create backups, or otherwise use Relay.

2. Information We Collect

A. Account and Profile Information

When you create or maintain a Relay account, we may collect:

Name
Username
Email address
Mobile number
Password and authentication credentials submitted for account access
Email verification information
Profile photo
Account identifiers
Company or workspace memberships
Roles and permissions

Relay supports profile editing for name, username, email address, mobile number, and profile image.

B. Device, Session, and Technical Information

Relay may collect or generate:

A stable app-specific device identifier
Device type
Device name or model
Operating system / platform
App version
Session identifiers
Authentication tokens
Firebase Cloud Messaging (FCM) token
Linked-device information
Network and connectivity information necessary to connect to Relay services
Notification-delivery and app-state information

This information is used for login security, session management, linked-device functionality, push notifications, compatibility, troubleshooting, and service operation.

C. Communications and Chat Information

Relay supports one-to-one chats, group chats, topic conversations, reactions, read/delivery states, reminders, forwarded content, voice notes, images, videos, documents, and other attachments.

Relay's chat system is designed to use end-to-end encryption for supported message content and supported chat attachments. Private cryptographic identity, ratchet, and pre-key material is maintained on user devices. Relay servers may still process or store encrypted message content (ciphertext) together with information needed to route and operate the service, such as:

Sender and recipient identifiers
Conversation or group identifiers
Device identifiers
Message identifiers
Delivery/read state
Timestamps
Attachment routing/storage metadata
Encryption protocol metadata
Group membership and administrative metadata

End-to-end encryption does not mean that all account, workspace, notification, task, project, leave, expense, support, or administrative information is end-to-end encrypted.

D. Calling Information

Relay supports voice and video calls using the device microphone, camera, speakers, Bluetooth audio devices, and real-time communication technology.

To provide calls, Relay may process:

Caller/callee identifiers
Call type
Call status
Call UUID or call identifier
Start/end timing and duration
Call history information
Real-time audio/video streams
Camera/microphone state
Connection and media-routing information

Audio and video streams are processed as necessary to provide the real-time call experience. The reviewed client code does not expose a normal user-facing call-recording feature, but the operator must ensure that any server-side or future recording behavior is separately disclosed before use.

E. Files, Media, Camera, and Audio

If you choose to use these features, Relay may access or process:

Photos and videos selected from your device
Camera-captured photos or video
Audio and voice recordings
Documents and other files
Shared files received from other apps
Generated thumbnails or previews
Downloaded or saved media

Files may be stored locally on your device and, where a feature requires it, uploaded to Relay services. Supported chat attachments may be encrypted before upload as part of Relay's end-to-end encrypted messaging design.

F. Company, Workspace, Project, and Task Information

If you use Relay with a company, organization, or workspace, we may process information such as:

Company/workspace identity and membership
Roles, permissions, departments, teams, or units
Project names and descriptions
Project status, dates, progress, owners, members, comments, and attachments
Task titles and descriptions
Assignees
Priority
Due dates
Reminder dates
Status and progress
Task attachments
Task voice notes
Links between tasks and source chat messages
Collaboration and invitation information

Authorized company/workspace users may have access to this information according to their permissions.

G. Leave, Expense, and Support Information

Where enabled by an organization, Relay may process:

Leave data:

Leave type
From/to dates
Reason
Supporting attachment

Expense data:

Expense category
Title
Amount
Expense date
Description
Receipt or supporting file

Support-ticket data:

Subject
Description
Category
Department
Priority
Assigned user/agent
Related record identifiers
Attachments
Status information

Because users may enter sensitive information into descriptions, reasons, receipts, documents, screenshots, or attachments, users and organizations should avoid submitting information that is not necessary for the relevant business purpose.

H. Invitations, Search, and Connections

Relay allows users to search for other Relay users using an email address or mobile number, send connection requests, and invite people to Relay.

We may process:

Email addresses or mobile numbers entered for user search
Target user identifiers
Connection-request status
Group invitations
Company/workspace invitations
External invitation email addresses
Invitation tokens and related status

If a user enters the email address of a person who is not yet on Relay, the service may use that address to send a Relay invitation.

I. Notifications and Reminders

Relay uses local and remote notifications for features including:

Chat messages
Calls
Tasks and work updates
Leave/expense updates
Invitations
Message reminders
Other service events

Notification data may include identifiers and limited event information needed to display, route, or open the relevant content. Where encrypted message content is involved, Relay is designed to decrypt supported message content on the authorized device.

J. Google Account and Google Drive Backup Information

Relay offers an optional Google Drive backup feature on supported mobile devices.

If you connect a Google account, Relay may access:

Google account email address
Google display name
Google profile photo
Google authentication/authorization information needed for the connection

Relay requests Google Drive's app-specific data scope (Drive appDataFolder) for this feature. This scope is designed to allow Relay to access its own hidden application-data area rather than your general Google Drive files.

Relay can create encrypted account backups that may include:

Local Relay database data
Chat history
Message metadata
Reminders
Local media/attachments if you enable attachment backup
Backup manifest information

Relay encrypts supported backup archives before uploading them. The backup implementation reviewed uses AES-256-GCM-based encryption and account-specific or password-based key derivation depending on the backup format.

Relay may delete older Relay backup files from its own Google Drive app-data area when a newer backup is uploaded.

K. Local Storage

Relay stores certain information locally on your device, which may include:

Login/session information
User profile information
Company/workspace context
Device identity
Notification state
Local chat database
Conversation and message records
User/contact cache
Message reminders
Call history
Encryption keys and cryptographic state
Downloaded/sent media
Backup markers and settings

Sensitive cryptographic material is designed to use protected/secure device storage where supported.

3. Device Permissions

Depending on platform and feature use, Relay may request access to:

Internet and network state: to connect to Relay services.
Notifications: to show messages, calls, reminders, and work updates.
Camera: for video calls, QR/device linking, and capturing media.
Microphone: for calls and voice recordings.
Photos/videos/audio/media/files: for selecting, sending, receiving, saving, or backing up attachments.
Bluetooth: for compatible call audio devices.
Biometrics / device authentication: to confirm device ownership for security-sensitive actions such as linked-device authorization. Relay relies on the operating system's authentication result and does not receive or store your fingerprint, face template, PIN, or device-unlock secret.
Exact alarms / boot completion / wake lock: for scheduled message reminders, call handling, and reliable notification/reminder operation.
Battery optimization controls: where needed for reliable background call/notification behavior.
Foreground camera/microphone service access: while supported calling features are active.
Install-package permission on Android: the reviewed Android build declares this permission for app-update functionality. It should be retained only if the production distribution method genuinely requires it.

The reviewed Android code does not request precise location permission or Android contacts/address-book permission.

4. Firebase And Google Services

Relay integrates Google services including:

Firebase Cloud Messaging

Used to deliver push notifications and obtain an FCM device token.

Firebase Analytics

The reviewed Android build includes the Firebase Analytics SDK. Depending on Firebase configuration, Firebase may collect app-usage, device/app-instance, interaction, and technical information for analytics purposes. The operator should ensure the Google Play Data Safety form and any consent controls accurately reflect the production Firebase configuration.

Google Sign-In / Google Drive

Used only when you choose to connect Google Drive for Relay backup. Relay requests the Drive app-data scope for its own backup files.

These services are provided by Google and are also subject to Google's applicable privacy terms and policies.

5. How We Use Information

We use information to:

Create, verify, and manage Relay accounts
Authenticate users and maintain sessions
Provide one-to-one and group communications
Provide end-to-end encrypted messaging functionality
Deliver and synchronize messages
Provide voice and video calls
Manage linked devices and encryption keys
Provide notifications and reminders
Allow users to send, receive, preview, download, and save files
Provide backup and restore functionality
Provide companies/workspaces, projects, tasks, collaboration, leave, expense, support-ticket, and permission features
Process invitations and connection requests
Protect account and service security
Detect and investigate misuse, abuse, or technical problems
Maintain, troubleshoot, and improve the app
Understand app usage through analytics where enabled
Comply with legal obligations and enforce our Terms of Service

6. How Information Is Shared

We may share or make information available in the following circumstances:

A. With Other Relay Users

Information you intentionally share with another person or group may be visible to the intended participants, subject to Relay's permissions and encryption design.

B. With Your Company or Workspace

If you join or use an organization on Relay, authorized administrators, managers, assignees, collaborators, or other permitted members may access company/workspace records according to their assigned permissions.

C. With Service Providers

We may use service providers to operate hosting, push notifications, analytics, email delivery, backup integrations, security, networking, and other technical services. These providers receive only the information reasonably necessary for their role.

D. With Google

If Firebase or Google Drive features are used, information is processed by Google as described above.

E. For Legal, Safety, or Security Reasons

We may disclose information where required by law or where reasonably necessary to protect users, Relay, our systems, legal rights, or public safety.

F. Business Transfers

If the operator is involved in a merger, acquisition, financing, restructuring, sale of assets, or similar transaction, information may be transferred subject to applicable law and appropriate safeguards.

7. End-To-End Encryption And Security

Relay is designed so that supported chat message content and supported chat attachments are encrypted for authorized recipient devices.

However:

Routing and service metadata may remain visible to Relay systems.
Company/workspace business data is not necessarily end-to-end encrypted.
Push-notification metadata may be processed by notification providers.
A recipient can save, copy, forward, screenshot, photograph, export, or otherwise retain content after receiving it.
Security depends on protecting your device, account credentials, recovery/backup material, and linked devices.

Relay uses local secure-storage mechanisms for cryptographic keys where supported. No system can guarantee absolute security.

8. Data Retention

We retain information for as long as reasonably necessary to:

Provide the service
Maintain accounts and workspace records
Synchronize communications
Maintain security and fraud-prevention records
Meet legal, regulatory, contractual, accounting, or dispute-resolution obligations

Local data may remain on a device until it is deleted by the app, removed by the user, cleared through operating-system controls, or removed by uninstalling the app, depending on the type of data and platform behavior.

Google Drive backups remain in the Relay app-specific Google Drive storage until replaced, deleted through Relay, removed by the user through applicable Google controls, or otherwise removed under Google's retention rules.

Some information may need to be retained after an account-deletion request when required by law, for fraud/security purposes, or to preserve records that an organization is legally required to keep. Where this applies, retained data should be limited to what is necessary.

9. Account And Data Deletion

The reviewed Relay client supports account creation but does not currently contain a complete user-facing account-deletion flow.

Until the application is updated, users may request deletion by contacting:

[PRIVACY CONTACT EMAIL]

or visiting:

[ACCOUNT DELETION OR PRIVACY REQUEST URL]

A deletion request should cover the user's account and personal data associated with that account, subject to any data that must legally be retained.

IMPORTANT FOR THE OPERATOR: Before App Store / Google Play publication, implement and expose the deletion workflow required by the applicable store rules. Do not publish a privacy policy that claims an in-app deletion button exists until that feature actually exists.

10. Your Choices And Rights

Depending on your location, you may have rights to:

Access personal information
Correct inaccurate information
Request deletion
Request a copy of information
Object to or restrict certain processing
Withdraw consent where processing is based on consent
Disconnect Google Drive
Revoke device permissions through operating-system settings
Manage notification permissions
Remove or revoke linked devices

To exercise privacy rights, contact:

[PRIVACY CONTACT EMAIL]

We may need to verify your identity before completing a privacy request.

11. Organization-Controlled Information

If you use Relay through a company or organization, that organization may independently determine how some workplace information is collected, used, retained, and disclosed. The organization may have its own privacy notices, employment policies, records-retention rules, or legal obligations.

For questions about organization-controlled records such as leave requests, expense claims, projects, tasks, or workplace support tickets, you may also need to contact the relevant organization administrator.

12. Children

Relay is designed for communication and work-collaboration use and is not intended to be used by children in violation of applicable law. If local law requires parental or guardian consent for a minor to use the service, the account should not be created or used without the required consent.

13. International Data Processing

Relay and its service providers may process information in countries other than the country where you live. Where required, the operator must use appropriate legal safeguards for cross-border transfers.

14. Changes To This Privacy Policy

We may update this Privacy Policy when Relay features, legal requirements, service providers, or data practices change. We will update the effective date and provide additional notice where required.

15. Contact Us

For questions, privacy requests, or complaints: