Skip to content
Reelay
Code scanningIncident resolutionPricingDocumentation
Sign inGet started
Code scanningIncident resolutionPricingDocumentationSign in
Back to home

REELAY LEGAL

Privacy Policy

How Reelay collects, uses, stores, and processes information across its services.

Effective date
18 October 2026
Version
Initial version

On this page

  1. 01Introduction
  2. 02Our Role in Processing Personal Information
  3. 03Information We Collect
  4. 04Sources of Information
  5. 05How We Use Information
  6. 06Legal Bases for Processing
  7. 07AI Services and External Processing
  8. 08Service Providers and Disclosures
  9. 09International Data Transfers
  10. 10Enterprise Self-Hosted Agent
  11. 11Cookies and Browser Storage
  12. 12Information Security
  13. 13Data Retention and Deletion
  14. 14Individual Privacy Rights
  15. 15Customer Responsibilities for Personal Information
  16. 16Children's Privacy and Sensitive Information
  17. 17Automated Analysis and AI-Generated Results
  18. 18Communications and Preferences
  19. 19Changes to This Privacy Policy
  20. 20Complaints and Contact
Terms of Service
On this page 1. Introduction
  1. 01Introduction
  2. 02Our Role in Processing Personal Information
  3. 03Information We Collect
  4. 04Sources of Information
  5. 05How We Use Information
  6. 06Legal Bases for Processing
  7. 07AI Services and External Processing
  8. 08Service Providers and Disclosures
  9. 09International Data Transfers
  10. 10Enterprise Self-Hosted Agent
  11. 11Cookies and Browser Storage
  12. 12Information Security
  13. 13Data Retention and Deletion
  14. 14Individual Privacy Rights
  15. 15Customer Responsibilities for Personal Information
  16. 16Children's Privacy and Sensitive Information
  17. 17Automated Analysis and AI-Generated Results
  18. 18Communications and Preferences
  19. 19Changes to This Privacy Policy
  20. 20Complaints and Contact

1. Introduction

REELAY COMPUTER TECHNOLOGY LTD ("Reelay", "we", "us", or "our") is a company incorporated in Nigeria and based in Lagos, Nigeria.

This Privacy Policy explains how personal information is collected, used, disclosed, stored, and otherwise processed in connection with Reelay's websites, applications, software development kits ("SDKs"), application monitoring tools, artificial intelligence-assisted diagnostics, integrations, and related services (collectively, the "Services").

Reelay provides software tools to businesses for monitoring application errors and performance, investigating incidents, analysing source code, assessing dependencies and security findings, and supporting engineering workflows.

This Privacy Policy applies to:

  • Individuals who register for or administer Reelay accounts.
  • Employees and other authorised users of customer workspaces.
  • Individuals whose information appears in telemetry, logs, browser replay data, source code, or other materials processed through the Services.
  • Individuals contacting Reelay for support or commercial enquiries.
  • Individuals subscribing to service-status communications.
  • Visitors to Reelay websites and applications.

Certain data-processing activities are determined by Reelay's business customers. Where Reelay processes personal information on a customer's instructions, additional contractual privacy terms may apply.

Contact: privacy@usereelay.com

Postal address: Festac Town, Lagos, Nigeria

2. Our Role in Processing Personal Information

Reelay processes different types of information for different purposes.

For account administration, billing, business communications, authentication, security, and the management of its own operations, Reelay generally determines the purposes and means of processing.

When a business customer configures Reelay to collect telemetry, record browser sessions, analyse application errors, or process source code on its behalf, that customer generally determines why the information is processed and what is submitted. Reelay processes that information to provide the requested Services, subject to applicable agreements and instructions.

The precise legal classification of each party, including whether it acts as a controller, processor, or equivalent, depends on the activity and applicable law.

For account administration and its own business operations, Reelay acts as a controller or equivalent under applicable law. For personal information processed on a business customer’s instructions, Reelay acts as a processor or equivalent. Contact privacy@usereelay.com to discuss the data-processing terms required for your use of the Services. Required processing agreements must be in place before the relevant processing begins.

3. Information We Collect

The categories of information processed depend on which Services are used, how customers configure them, and which integrations are enabled.

3.1 Account and authentication information

Reelay processes account and authentication information, which may include:

  • Names and email addresses.
  • Password hashes and authentication credentials.
  • Multi-factor authentication information and protected recovery credentials.
  • Account activation and status information.
  • Authentication tokens and session records.
  • Login timestamps and device or browser information.

We use this information to administer accounts, verify identities, control access, support authentication and account recovery, and investigate security issues.

3.2 Workspace and organisational information

Reelay processes information associated with customer workspaces, including workspace names, membership records, roles, permissions, invitations, team structures, ownership, on-call schedules, incident assignments, and escalation histories.

This information supports workspace collaboration, access management, incident coordination, and accountability.

3.3 Device, connection, and technical information

When individuals access the Services, Reelay may process technical information such as:

  • IP addresses.
  • Device identifiers.
  • Browser and operating-system information.
  • User-agent information.
  • Login and session timestamps.
  • Location information or coordinates where supplied through relevant network or edge headers.

We use this information for authentication, session management, security, troubleshooting, and relevant service operations.

3.4 Application errors, logs, and telemetry

Customers may configure the Services to submit information relating to application errors, incidents, and software operations.

Depending on the SDK, integration, and configuration, this may include:

  • Error and exception messages.
  • Stack traces and source-file references.
  • Request methods, URLs, response status codes, and selected headers.
  • Transaction and trace identifiers.
  • Session identifiers.
  • Breadcrumbs, events, logs, and traces.
  • Incident descriptions, investigation notes, and resolution history.
  • Custom information deliberately submitted by customers.

These materials may contain personal information, confidential information, or information relating to individuals who do not have Reelay accounts.

Customers are responsible for assessing and configuring the information their applications submit.

3.5 Browser session replay

Where browser session replay is enabled, Reelay's browser SDK can record technical information representing activity within a customer's application.

Recorded information may include:

  • Document Object Model (DOM) snapshots and changes.
  • User interactions and input-related events.
  • Mouse and scrolling events.
  • Timing information.
  • Certain presentation information, including styles.
  • Information linking replay sessions to application errors.

Session replay reconstructs browser interactions from recorded application data. It is not conventional camera-based video recording.

The browser SDK supports input-value masking, default text masking, and other filtering or redaction mechanisms. Customers may configure certain masking behaviours.

These mechanisms do not guarantee that every item of personal, confidential, or sensitive information is excluded from collected data.

The browser SDK enables replay by default unless the customer disables it. Replay captures may be buffered before relevant clips are submitted in connection with captured errors.

Customers must assess the lawfulness of session recording, provide required notices, obtain applicable consent, and configure appropriate privacy protections before deploying the SDK.

3.6 Performance and profiling information

Reelay may process application performance data, including:

  • Application transactions and spans.
  • Browser and resource performance measurements.
  • Web performance indicators.
  • Execution timing.
  • Profiling information involving functions, files, and source locations.

This information supports application performance monitoring, troubleshooting, and technical diagnostics.

3.7 Source code, repositories, and scanning data

When customers enable source-aware diagnostics, scanning, or repository integrations, Reelay may process:

  • Repository identifiers and metadata.
  • Branch and commit information.
  • Source-code archives, snippets, and source maps.
  • Dependency and software licence information.
  • Security and code-analysis findings.
  • Suggested changes and patches.
  • Authorised validation-command outputs.
  • Information required for authorised repository changes or pull requests.

Source repositories can contain personal information or confidential material. Customers are responsible for ensuring that they have the authority to connect and submit these resources.

3.8 AI-assisted processing information

Reelay provides AI-assisted functionality for activities such as investigation, technical explanation, code analysis, generating suggested patches, and incident analysis.

Depending on the enabled feature, processed information may include:

  • Error and incident evidence.
  • Relevant source-code context.
  • Investigation prompts and tool instructions.
  • Generated explanations, reports, and proposed changes.
  • Investigation steps, tool arguments, file paths, and selected diagnostic excerpts.
  • Model identifiers, token or usage measurements, and cost information.
  • Submitted feedback, including ratings and comments where supported.

Reelay does not use customer code, telemetry, prompts, or generated results to train AI models or for product evaluation or improvement.

Processing necessary to produce an analysis requested by a customer, maintain service functionality, administer usage, or meet legitimate security and legal obligations is distinct from training or evaluating models.

Third-party or customer-selected AI services may have separate contractual terms and data practices. Their applicability must be assessed based on actual configuration.

3.9 Integrations and credentials

Where customers connect supported external services, Reelay may process integration identifiers, account details, authorisation information, routing settings, and protected credential references.

Relevant integrations implemented in the software include GitHub, Slack, and Microsoft Teams, subject to customer configuration.

Reelay uses this information to establish authorised connections, exchange information requested through integrations, deliver notifications, and execute enabled workflows.

3.10 Billing and commercial information

For billing and account administration, Reelay may process:

  • Billing names and email addresses.
  • Subscription plans and entitlements.
  • Payment references.
  • Transaction amounts and currency.
  • Usage and billing ledgers.
  • Payment authorisation references.
  • Limited payment-method information returned by an enabled payment provider, such as card brand, last four digits, expiry, or bank details.

Reelay uses Paystack for payment processing.

Reelay does not represent that payment information is processed exclusively within Reelay-controlled infrastructure.

3.11 Sales, support, status, and communications information

Reelay may process contact names, email addresses, telephone information provided in enquiries, expected usage, contractual enquiries, support correspondence, communication delivery results, and related business records.

Where an individual subscribes to status-page notifications, Reelay may process their email address, subscription preferences, verification records, and unsubscribe information.

3.12 Security and audit information

Reelay processes audit and security information, including actor identifiers, account activity, administrative actions, associated IP addresses or user agents where captured, access-related events, and records relevant to operational accountability.

4. Sources of Information

We receive information:

  1. Directly from individuals who register, contact us, or use the Services.
  2. From business customers and authorised workspace administrators.
  3. Automatically through the websites, applications, SDKs, and technical systems used to provide the Services.
  4. Through customer-authorised integrations and external services.
  5. From applications, repositories, infrastructure, and systems that customers configure Reelay to monitor or analyse.
  6. Through payment providers and business communications.

Reelay does not independently determine every category of customer-submitted information.

5. How We Use Information

We process information for the following purposes, as relevant:

  • Providing and operating the Services.
  • Creating and managing accounts and workspaces.
  • Authenticating users and controlling permissions.
  • Capturing and investigating customer-submitted technical incidents.
  • Conducting requested AI-assisted analysis and code diagnostics.
  • Operating configured integrations.
  • Administering subscriptions, usage entitlements, and billing.
  • Communicating about accounts, incidents, security, and service operations.
  • Responding to enquiries and support requests.
  • Identifying abuse, investigating suspicious activity, and protecting our systems.
  • Maintaining operational and compliance records.
  • Meeting applicable legal obligations.
  • Establishing, exercising, or defending legal claims where permitted.

Personal information submitted by customers for technical processing is not repurposed for AI training or product evaluation/improvement.

6. Legal Bases for Processing

Where applicable law requires a legal basis, processing must be supported by an appropriate basis determined for the specific activity.

For processing that Reelay determines, the applicable bases and purposes include:

  • Contractual necessity: Processing required to deliver requested Services or administer customer agreements.
  • Legitimate interests: Processing reasonably necessary for security, fraud prevention, service administration, and related legitimate business purposes, subject to applicable balancing requirements.
  • Legal obligations: Processing required by applicable law, including relevant accounting, regulatory, and legal obligations.
  • Consent: Processing that requires an individual's valid consent under applicable law.

Where Reelay acts on a business customer's instructions, that customer is responsible for identifying the lawful basis for the processing it determines, including collection through its applications.

Accepting Reelay's Terms of Service does not, by itself, constitute consent to every personal-data processing activity.

7. AI Services and External Processing

Reelay uses Amazon Web Services (AWS), including Amazon Bedrock, for hosted AI processing. Hosted infrastructure is located in AWS’s Ireland Region. AWS AI processing is routed through the United States, and cross-region inference can process requests in other supported AWS Regions.

Reelay uses Voyage AI in the United States for source-code embeddings and indexing. Relevant source-code chunks and search queries may be sent to Voyage AI for these purposes.

Data-processing locations can differ between storage, AI inference, email delivery, network traffic handling, and customer-selected integrations. Reelay does not promise that all information remains within a single country or AWS Region.

Information sent to an external provider is subject to the applicable service configuration, contractual arrangements, and the provider’s relevant data practices. Customers may contact privacy@usereelay.com for information about the providers and processing arrangements relevant to their use of the Services.

Reelay does not use customer code, telemetry, prompts, or generated results for AI training or product evaluation or improvement.

8. Service Providers and Disclosures

Reelay uses the following service providers in production to operate enabled Services:

  • Amazon Web Services (AWS): Hosting, storage, infrastructure, Amazon Bedrock AI processing, and Amazon Simple Email Service (SES) email delivery. The information processed depends on the relevant service and customer configuration.
  • Paystack: Payment processing, including billing contact details, transaction information, and payment authorisation references.
  • Cloudflare: Website and application delivery, network traffic handling, and related hosting or security services, according to the deployed configuration.
  • Voyage AI: Source-code embeddings and indexing, including relevant source-code chunks and search queries.

Customer-authorised integrations may also exchange information with GitHub, Slack, Microsoft Teams, and other customer-selected external services. An independently selected integration provider may have a different legal role from a service provider processing information on Reelay's behalf.

Information is disclosed as necessary to provide enabled features, operate the Services, or perform authorised customer instructions. The data received by each provider depends on the feature, configuration, and applicable agreement.

Data disclosed through a customer-authorised integration may be subject to the recipient's separate terms and privacy practices.

Reelay may also disclose information where required by applicable law or a valid legal process, or where lawfully necessary to protect rights, investigate abuse, or address security incidents. If Reelay is involved in a merger, acquisition, restructuring, or sale of its business, relevant information may be transferred as part of that transaction, subject to applicable law, confidentiality obligations, and required notices.

9. International Data Transfers

Reelay is incorporated in Nigeria and serves business customers internationally. Hosted infrastructure in Ireland, AI processing in the United States and other supported AWS Regions, Voyage AI processing in the United States, and enabled provider or integration services can involve transfers outside Nigeria or the individual’s country.

International transfers are subject to applicable data-protection law. Where a transfer requires a lawful transfer basis, contractual safeguards, an assessment, or another protection, the required arrangement must be established before that transfer takes place.

Contact privacy@usereelay.com for information about the transfer arrangements applicable to your data. This Privacy Policy does not itself replace a required Data Processing Agreement or international-transfer agreement.

10. Enterprise Self-Hosted Agent

Certain Enterprise configurations allow customers to operate a Reelay agent within their own infrastructure.

In the implemented Enterprise agent privacy mode:

  • Supported application telemetry and operational content are routed to the customer-operated agent.
  • Relevant hosted ingestion and operational routes are restricted while the applicable privacy setting is enabled.
  • Operational evidence, analyses, replay information, and reports are stored within the customer-side environment.
  • The customer configures relevant local infrastructure and supported external credentials.
  • Reelay's cloud control plane continues to process information required for identity, workspace administration, licensing, connectivity, usage accounting, and service coordination.

This control-plane information can include identifiers, agent connectivity details, job status, heartbeat information, subscription data, and aggregate usage or cost measurements.

Self-hosted agent mode is not equivalent to a fully offline deployment of every Reelay component.

Customer-configured external providers may still receive information processed by the agent.

Enabling self-hosted privacy mode does not automatically migrate or delete information previously stored in Reelay's hosted environment.

Customers are responsible for appropriate security, access management, backups, data handling, and retention within their self-hosted environments, subject to the applicable agreements.

11. Cookies and Browser Storage

Reelay uses browser storage and authentication technologies to support account access and application functionality.

The Services use:

  • Authentication cookies supporting refresh sessions.
  • Browser local storage for dashboard authentication state.
  • Browser storage for certain interface preferences.
  • Local storage of pending browser SDK error submissions in supported configurations.
  • Additional authentication and access mechanisms for certain administrative or restricted status-page functions.

Authentication refresh sessions have a configured default lifetime of 30 days and may end earlier through logout, revocation, or security controls. Preferences and SDK records may have different lifetimes depending on their function and configuration.

Reelay uses these technologies for authentication, interface preferences, and SDK operation. Reelay does not use analytics, advertising, or marketing cookies. Browser settings can be used to clear stored data or restrict storage, although doing so may affect service functionality.

Customers deploying Reelay's browser SDK are responsible for assessing whether session recording, local storage, or other technologies require disclosure or consent in their own applications.

12. Information Security

Reelay uses security mechanisms such as password hashing, protected authentication secrets, role- and permission-based access controls, encrypted credential storage, scoped access grants, and audit records.

Encryption is configured for relevant hosted storage and managed-secret resources. Access is limited according to roles, permissions, and operational need. Suspected security incidents may be reported to security@usereelay.com for investigation and response. Reelay will provide incident notices where required by applicable law or an applicable agreement.

These measures are intended to reduce the risk of unauthorised access, disclosure, modification, or loss.

However, no technical or organisational measure eliminates all security risks.

Reelay does not guarantee absolute security, nor does it represent that every category of information is end-to-end encrypted.

13. Data Retention and Deletion

Reelay's retention policy is to keep customer information until the customer or an authorised individual requests deletion, subject to any shorter applicable service-retention settings and applicable legal requirements. Personal information must not be retained longer than necessary for the lawful purposes for which it is processed.

Deletion requests may be sent to privacy@usereelay.com. Reelay may verify the requester's identity and authority to request deletion before acting. Requests concerning information processed on a business customer's instructions may require that customer's authorisation.

Reelay deletes the requested information immediately once the request has been verified and authorised. This policy includes active service records, backups, snapshots, and copies held by service providers on Reelay's behalf, except information that applicable law requires Reelay to retain. Any lawfully retained information must be limited to the relevant purpose and period.

A customer operating a self-hosted agent remains responsible for deleting information in infrastructure and external services it independently controls, with Reelay providing assistance as required by the applicable agreement.

14. Individual Privacy Rights

Depending on applicable law, individuals may have rights relating to their personal information, including rights to:

  • Request access to personal information.
  • Request correction of inaccurate information.
  • Request deletion in applicable circumstances.
  • Object to or request restrictions on certain processing.
  • Request data portability where legally available.
  • Withdraw consent where processing is based on consent.
  • Lodge a complaint with a competent data protection authority.

These rights may be subject to legal conditions and exceptions.

Requests relating to information processed by Reelay on behalf of a business customer may need to be directed to that business, which determines the relevant processing purposes.

Individuals may contact privacy@usereelay.com about privacy requests. This mailbox is monitored, and Reelay responds within seven days. An initial response may request information needed to verify identity, clarify the request, or explain its handling. Any applicable legal deadline for completing a request continues to apply.

Reelay may need to verify a requester's identity and determine the applicable legal obligations before acting on a request.

15. Customer Responsibilities for Personal Information

Business customers control how they configure SDKs, integrations, monitored applications, repository connections, and other data-submission features.

Customers are responsible, to the extent required by applicable law and their contracts, for:

  • Providing appropriate notices to affected individuals.
  • Establishing a lawful basis for information collection and processing.
  • Obtaining consent where required.
  • Configuring recording, masking, filtering, and access settings appropriately.
  • Avoiding unnecessary submission of sensitive information.
  • Ensuring they have the authority to submit third-party data, source code, and other protected materials.
  • Managing the privacy and security of their self-hosted environments.

These responsibilities do not remove obligations that independently apply to Reelay.

16. Children's Privacy and Sensitive Information

Reelay's Services are intended for business use. Reelay does not set a separate minimum user age. Applicable requirements for legal capacity, valid consent, and any required parent or guardian involvement continue to apply.

However, technical information submitted through a customer's application may include information relating to children or other vulnerable individuals, depending on the customer's application and configuration.

The Services may also process sensitive or confidential information contained in submitted logs, browser events, source code, or other technical materials.

Customers may submit sensitive or regulated information only where they have a lawful basis and have arranged any special contractual, security, or handling requirements applicable to that information. This includes health information, payment-card information, and other protected data. Availability of a feature does not by itself establish compliance with a particular regulated-data standard.

Customers whose applications involve children or other vulnerable individuals must provide required notices, obtain any legally required parent or guardian consent, and configure appropriate safeguards before collection. Reelay’s lack of a separate minimum account age does not remove these requirements.

17. Automated Analysis and AI-Generated Results

Reelay uses automated tools and AI-assisted processes to generate technical analyses, recommendations, and other results in response to enabled customer workflows.

These outputs may contain inaccuracies and are intended to support customer review and decision-making. Reelay’s AI features advise engineers; they do not make automated decisions that produce legal or similarly significant effects on individuals.

18. Communications and Preferences

Reelay may send communications relating to account administration, workspace invitations, authentication, incidents, billing, service changes, and security.

Individuals subscribing to status updates may use available unsubscribe functionality.

Reelay does not send marketing emails. Operational, account, billing, incident, and security messages may still be sent as necessary to provide the Services.

19. Changes to This Privacy Policy

Reelay may update this Privacy Policy to reflect changes in its Services, data-processing practices, or legal obligations.

Updated versions will identify their effective date and will be published on this Privacy Policy page. Reelay provides at least 30 days’ advance notice of material changes by email or an appropriate in-service notice, except where an earlier change is required by law or necessary to address an urgent security issue. Any exception remains subject to applicable legal notice and consent requirements.

Where applicable law requires additional notice or consent, the necessary requirements must be satisfied before relevant changes take effect.

20. Complaints and Contact

Individuals may contact Reelay with questions, requests, or concerns regarding personal information at:

REELAY COMPUTER TECHNOLOGY LTD
Lagos, Nigeria
Email: privacy@usereelay.com
Postal Address: Festac Town, Lagos, Nigeria

Individuals may also have the right to complain to a competent data protection authority, depending on applicable law.

In Nigeria, the competent privacy regulator is the Nigeria Data Protection Commission (NDPC), which can be contacted through its official website at https://ndpc.gov.ng. Individuals elsewhere may contact the competent authority in their jurisdiction. Privacy enquiries are coordinated through privacy@usereelay.com; no named Data Protection Officer or external representative is currently appointed.

End of privacy policy.

Back to top ↑
Also readTerms of Service
Reelay

Resolve production errors at the snap of your fingers.

Code scanningDocumentationSelf-hostingContactPrivacy PolicyTerms of Service
© 2026 Reelay