Privacy Policy for Glenn

Name: GLENN
Rating: 4.8 (15000 reviews)
Author: GLENN Esports

Effective Date: 5 August 2026 Last Updated: 5 August 2026

Glenn (“Glenn,” “we,” “us,” or “our”) is a social and esports platform operated by Anjali Sharma.

This Privacy Policy explains how we collect, use, store, disclose, and protect information when you use:

The Glenn mobile application;
The Glenn website;
Tournament, social, messaging, community, profile, rewards, merchandise, and related features;
Any other service that links to this Privacy Policy.

The Glenn Android application may be identified by the package name com.absolute.glenn.

By creating an account or using Glenn, you acknowledge that your information will be handled as described in this Privacy Policy. Where applicable law requires consent, we will request consent separately.

1. Who We Are

Glenn is a social esports platform that allows users to create profiles, discover players, interact with the community, publish content, communicate with other users, join tournaments, build teams, and use other esports-related services.

Developer or operator: Anjali Sharma Brand: Glenn / Glenn Esports Country of operation: India Website: https://glennesports.app Privacy email: glennesports7gmail.com Support email: glennesports7gmail.com

2. Scope of This Privacy Policy

This Privacy Policy applies to information processed through Glenn’s application, website, backend systems, official support channels, and related services.

It does not govern independent websites, applications, payment services, delivery services, or other third-party services that have their own privacy policies.

3. Information We Collect

The information we collect depends on the Glenn features you use, the permissions you provide, and the information you choose to submit.

3.1 Account and Authentication Information

When you create or access a Glenn account, we may collect:

Email address;
Display name;
Username;
User ID or account identifier;
Phone number, where requested;
Login method;
Authentication records;
Google account information provided through Google Sign-In;
Account creation and last-login timestamps;
Account status and verification information.

Passwords used for email authentication are handled through our authentication provider. We do not intend to store users’ readable or plain-text passwords.

3.2 Profile Information

Information added to a Glenn profile may include:

Profile photograph or avatar;
Profile biography;
Name or display name;
Username;
Gender or pronouns, where voluntarily provided;
City, state, region, or country;
Preferred language;
In-game name or IGN;
Free Fire UID or other game identifiers;
Game profile information;
Team, guild, organisation, or roster information;
Player role, experience, rank, statistics, achievements, or availability;
Social links provided by the user;
Other profile information voluntarily entered by the user.

Some profile information may be visible to other users or publicly accessible, depending on the feature and privacy settings available.

3.3 User-Generated Content

Glenn is a social platform. We may collect and store content that users create, submit, publish, upload, or share, including:

Posts;
Captions and descriptions;
Comments and replies;
Tournament descriptions;
Team or guild descriptions;
Images and other media;
Profile content;
Polls or community submissions;
Reports and feedback;
Tournament screenshots;
Results, score submissions, or match evidence;
Other content voluntarily created through the Service.

Content published through public or community features may be viewed, copied, shared, reported, or interacted with by other users.

You should not publish private, confidential, financial, identity, medical, or highly sensitive information in public posts, comments, profiles, or other public fields.

3.4 Messages and Communications

If you use Glenn’s messaging features, we may process:

Direct messages;
Group messages;
World or community chat messages;
Message attachments;
Message timestamps;
Sender and recipient identifiers;
Delivery, read, moderation, and reporting status;
Support messages sent to Glenn;
Communications with tournament organisers or administrators.

Private messages are not intended to be publicly visible. However, they are stored and processed to provide messaging functionality and may be accessed where reasonably necessary for:

Investigating user reports;
Preventing abuse or fraud;
Enforcing community rules;
Providing support;
Protecting users;
Complying with legal obligations.

Unless Glenn explicitly states otherwise within the application, users should not assume that messages are protected by end-to-end encryption.

3.5 Social and App Interactions

We may collect actions performed through Glenn, including:

Likes and reactions;
Follows and unfollows;
Shares and reposts;
Saves and favourites;
Profile visits, where the feature records them;
Post or content views, where recorded;
Search activity;
Tournament joins and registrations;
Match check-ins;
Team invitations and requests;
Reward claims;
Reports and blocks;
Content moderation actions;
Notification interactions;
Other actions needed to operate social or tournament features.

These interactions may be used to display counts, maintain relationships between accounts, operate social features, prevent misuse, and, where implemented, recommend relevant content.

3.6 Tournament and Esports Information

When users participate in tournaments or related activities, we may collect:

Tournament registration information;
Team name and roster;
Player names, usernames, game IDs, and in-game names;
Match attendance and check-in status;
Results, scores, standings, and rankings;
Match screenshots or evidence;
Room participation records;
Disqualification or rule-enforcement records;
Prize eligibility;
Communications with organisers;
Payment or payout details where prizes are distributed;
Information needed to investigate disputes or rule violations.

Tournament results, team names, player names, rankings, and similar competitive information may be publicly displayed.

3.7 Location Information

Depending on the features used and permissions granted, Glenn may collect:

Approximate location;
Precise device location;
Manually selected city, state, region, or country;
Location coordinates required for nearby-player, discovery, or map features.

Device-based location is collected only when the relevant permission has been granted and a feature requiring location is used.

Users may withdraw location permission at any time through their device settings. Some nearby-player, discovery, map, and other location-based features may not function correctly without location access.

If a user grants location permission and uses Glenn's nearby-player or location-based features, their location may automatically be used to make their profile discoverable to nearby users. Glenn may display an approximate area, distance, or nearby status based on the user's device location. Glenn does not intentionally display exact GPS coordinates or a full residential address to other users.

Users will also be able to disable location visibility through an in-app privacy setting. This control is planned to be available by the public production release of Glenn. Disabling location visibility or revoking location permission may prevent nearby-player and other location-based features from functioning.

3.8 Payment and Payout Information

Where Glenn provides prize distribution, withdrawals, purchases, tournament payments, rewards, or related financial functionality, we may collect:

UPI ID;
Account holder name;
Bank account details, where required;
Payment or transaction reference;
Withdrawal amount;
Payout status;
Payment screenshots or confirmation;
Information needed to investigate failed or disputed payments.

Payment information is generally optional and is collected only when a user uses a feature that requires payment or payout processing.

Glenn does not intend to collect full payment-card numbers, CVV codes, internet-banking passwords, UPI PINs, or OTPs. Users should never send such credentials through posts, messages, forms, or support channels.

Banks, UPI applications, payment processors, and financial institutions may independently process information under their own privacy policies.

3.9 Shipping and Delivery Information

When a user orders merchandise, receives a physical prize, or requests postal delivery, we may collect:

Recipient name;
Phone number;
Postal address;
City, state, postal code, and country;
Order information;
Delivery instructions;
Shipment status and tracking details.

This information is optional unless the user requests a physical delivery.

Shipping information may be provided to postal services, courier companies, merchandise suppliers, or fulfilment providers solely as necessary to complete the requested delivery.

3.10 Device and Technical Information

Glenn and its service providers may process technical information such as:

Device or installation identifiers;
OneSignal subscription or push-notification identifier;
Operating system and version;
Device model;
Application version;
Device language;
Country, region, or time zone inferred from device settings or network information;
Internet Protocol address;
Push-notification permission status;
Network and connection information;
Login and security events;
Session timestamps;
Basic usage and session information;
Server request information.

We use this information to operate the application, send notifications, maintain compatibility, secure accounts, investigate abuse, and diagnose technical problems.

3.11 Diagnostics and Error Information

Glenn may automatically create or store diagnostic records when an error occurs, including:

Failed API request information;
Error messages;
Response or status codes;
Time and date of the error;
Affected feature or screen;
App version;
Device or account identifier related to the request;
Technical debugging information;
Exception information, where available.

These records may be stored in our Supabase database or backend systems.

We use diagnostic information to identify technical failures, fix bugs, prevent repeated errors, investigate security problems, and improve application reliability.

We aim to avoid storing passwords, payment credentials, private message content, or unnecessary sensitive data in diagnostic logs.

3.12 Push-Notification Information

Glenn uses OneSignal to provide push notifications.

Depending on configuration and permissions, notification-related information may include:

Push subscription identifier;
Device or installation identifier;
Push token;
Notification permission status;
Device operating system;
Application version;
Language, country, and time zone;
Notification delivery and interaction information;
Session or usage metadata processed by the notification service;
Glenn account identifier linked to a notification subscription.

Push notifications may include:

Message alerts;
Tournament reminders;
Match-room or check-in information;
Security alerts;
Account updates;
Product or feature announcements;
Community announcements;
Other service-related communications.

Users can disable push notifications through the device settings. Certain important information may still be displayed inside the application.

Promotional notifications will only be sent where permitted by applicable law and platform rules.

3.13 Customer Support and Feedback

When users contact us, we may collect:

Name;
Email address;
Phone number;
Glenn username or account ID;
Message content;
Screenshots;
Device and app information;
Details of the issue;
Records of our response.

We use this information to respond to requests, investigate complaints, resolve technical problems, and improve the Service.

3.14 Information in Free-Text Fields

Glenn contains profile bios, posts, comments, messages, support forms, tournament descriptions, and other free-text fields.

Users may voluntarily place additional personal information in these fields that Glenn did not specifically request. The exact information received may therefore depend on what a user chooses to write or upload.

We do not encourage users to submit unnecessary sensitive information. This section does not give Glenn unlimited permission to intentionally collect undisclosed categories of personal information.

3.15 New Features and Additional Information

Glenn may introduce new features over time.

Before intentionally collecting a materially different category of personal information or using existing information for a materially different purpose, we will take reasonable steps to:

Update this Privacy Policy;
Provide an appropriate notice;
Request device permission or consent where required;
Update relevant app-store disclosures;
Provide choices or controls where reasonably available.

A new feature may be unavailable unless the information required for that feature is provided.

4. How We Collect Information

We collect information:

4.1 Directly From Users

For example, when users:

Create an account;
Complete a profile;
Publish content;
Send messages;
Join a tournament;
Submit results;
Request a withdrawal;
Order merchandise;
Contact support;
Report another user.

4.2 Automatically Through the Application

For example, through:

Application requests;
Authentication events;
Device information;
Push-notification services;
Error and diagnostic logs;
Security logs;
Social and feature interactions.

4.3 Through Permissions

Certain information is collected only after users grant device permissions, such as:

Location;
Camera;
Photos or media;
Notifications.

Users can manage permissions through their device settings.

4.4 Through Third-Party Services

We may receive information from services used to operate Glenn, such as authentication providers, database providers, notification providers, storage providers, hosting providers, payment services, and delivery providers.

5. How We Use Information

We may use information to:

5.1 Provide App Functionality

Create and maintain accounts;
Authenticate users;
Display profiles;
Publish posts and comments;
Deliver messages;
Manage follows, likes, saves, and other interactions;
Operate tournaments;
Maintain rankings and results;
Provide nearby-player or location features;
Process merchandise orders and deliveries;
Distribute prizes or payouts.

5.2 Manage Accounts

Verify login attempts;
Recover accounts;
Update profile information;
Maintain account settings;
Process account-deletion requests;
Communicate account-related information.

5.3 Send Communications

Deliver push notifications;
Send tournament alerts;
Notify users about messages and community activity;
Provide security and account notices;
Respond to support requests;
Announce important service changes.

5.4 Protect Glenn and Its Users

Detect spam, fake accounts, cheating, fraud, or abuse;
Enforce tournament and community rules;
Investigate reports;
Prevent unauthorised access;
Block harmful behaviour;
Maintain evidence relating to disputes or enforcement;
Comply with applicable law.

5.5 Maintain and Improve the Service

Diagnose API failures;
Fix bugs;
Monitor technical performance;
Improve application stability;
Develop and test features;
Understand whether essential features function correctly.

5.6 Personalise the Experience

Where implemented, we may use profile details, followed accounts, social interactions, game preferences, location, or content activity to:

Show relevant players;
Recommend teams or communities;
Display local tournaments;
Rank or organise content;
Suggest relevant posts or profiles.

We will update this Privacy Policy if Glenn introduces materially different recommendation or profiling systems.

6. Public Information and Social Features

Glenn is a social platform. Information a user publishes may become visible to other users or the public.

Publicly visible information may include:

Username and display name;
Profile image;
Bio;
Game IDs and in-game name;
Team or guild information;
Posts, comments, and media;
Follower and following information;
Likes or other visible interactions;
Tournament participation;
Rankings, results, and achievements.

Users should assume that public content may be:

Viewed by other people;
Screenshotted;
Copied;
Reposted;
Shared outside Glenn;
Indexed where technically applicable.

Deleting content from Glenn does not guarantee that copies independently saved or shared by other users will also be deleted.

Users are responsible for ensuring that they have permission to upload content that includes another person’s image, personal information, intellectual property, or private communications.

7. Content Moderation, Reports, and Safety

To maintain community and tournament safety, Glenn may review or process:

Reported posts;
Reported profiles;
Reported messages;
Tournament evidence;
Fraud or cheating reports;
Block and moderation records;
Content that appears to violate law or community rules.

Review may be performed by authorised Glenn administrators, moderators, organisers, or technical systems.

We may restrict, remove, preserve, or disclose content where reasonably necessary to:

Enforce our rules;
Protect users;
Investigate fraud or abuse;
Resolve tournament disputes;
Comply with valid legal requests;
Prevent serious harm.

8. How We Disclose Information

We do not sell users’ personal information.

We may disclose information in the following circumstances.

8.1 Service Providers

We use service providers to operate Glenn. Depending on the feature, these may include:

Supabase — authentication, database, realtime features, and backend infrastructure;
OneSignal — push notifications and notification-related processing;
ImageKit — image or media storage, delivery, and optimisation;
Vercel — website, API, or backend hosting;
Google Sign-In and Google Play services — authentication and Android platform services;
Postal services, couriers, suppliers, or fulfilment providers;
Banks, UPI services, or payment providers involved in requested transactions;
Security, technical-support, or infrastructure providers.

These providers may process information on our behalf according to their agreements and privacy practices.

8.2 Other Users and the Public

Information is disclosed to other users when a user:

Publishes public content;
Completes a public profile;
Sends a message;
Joins a tournament;
Joins a team or group;
Interacts with social content;
Shares information through a community feature.

8.3 User-Requested Transactions

We may disclose information when required to complete something a user requests, including:

Sending a payout;
Delivering merchandise;
Registering tournament participation;
Communicating with a team or tournament organiser;
Sharing content with a selected recipient.

8.4 Legal and Safety Reasons

We may disclose information where we reasonably believe it is necessary to:

Comply with applicable law;
Respond to a valid court order, government request, or legal process;
Investigate fraud, abuse, or security incidents;
Protect the rights, property, or safety of Glenn, users, or others;
Enforce our Terms of Service or tournament rules.

8.5 Business Changes

If Glenn is involved in a merger, acquisition, restructuring, financing, transfer, or sale of some or all of its operations, information may be transferred as part of that transaction.

Any successor will be required to process the information consistently with applicable law and the privacy commitments communicated to users.

8.6 With Consent

We may disclose information for another purpose when the user provides consent or directly instructs us to do so.

9. Third-Party Services

Glenn relies on third-party platforms and infrastructure.

These services may collect or process information according to their own privacy policies and contractual roles. Their practices are not controlled entirely by Glenn.

Current or expected service providers may include:

Supabase;
OneSignal;
ImageKit;
Vercel;
Google Sign-In;
Google Play services;
Postal or courier services;
Banks, UPI applications, or payment providers.

We may replace, remove, or add service providers as our technical infrastructure changes. If such a change materially affects how users’ personal information is processed, we will update this Privacy Policy.

10. Data Storage and International Processing

Information may be stored or processed on servers located in India or other countries where Glenn or its service providers operate infrastructure.

Data-protection laws in those locations may differ from the laws of the user’s country.

Where required, we will take reasonable steps to ensure that cross-border processing is performed using lawful safeguards and consistent with this Privacy Policy.

11. Data Security

We use reasonable technical and organisational safeguards designed to protect information, which may include:

HTTPS or TLS encryption during transmission;
Authentication controls;
Database access controls;
Role-based administrative permissions;
Supabase Row Level Security policies where implemented;
Restricted access to sensitive tables;
Logging and monitoring;
Secure credential management;
Security reviews and updates;
Backup and recovery procedures.

No application, database, network, or transmission system can be guaranteed to be completely secure.

Users are responsible for:

Protecting their password and device;
Not sharing login credentials or OTPs;
Using a strong password;
Logging out from shared devices;
Informing us about suspected unauthorised access.

Users should never send UPI PINs, passwords, OTPs, card CVVs, or similar secret credentials to Glenn or another user.

12. Data Retention

We retain information only for as long as reasonably necessary for the purposes described in this Privacy Policy, including providing the Service, resolving disputes, preventing fraud, maintaining security, and complying with legal obligations.

Retention may depend on the type of information.

12.1 Account and Profile Information

Account and profile information is generally retained while the account remains active and until the account is deleted.

12.2 User Content

Posts, comments, media, and other content may remain until:

The user deletes the content;
The account is deleted;
Glenn removes the content;
The content is no longer needed for the Service.

Content copied or shared independently by another user may remain outside Glenn’s control.

12.3 Messages

Messages may be retained to provide conversation history and operate messaging features.

When an account is deleted, we will delete or irreversibly de-identify associated message data where required and technically feasible, subject to another user’s rights, legal obligations, security needs, and valid dispute records.

12.4 Tournament Records

Results, rankings, rule-enforcement records, transaction records, and tournament evidence may be retained where needed to maintain competition history, investigate disputes, prevent repeated abuse, or fulfil legal and financial obligations.

12.5 Payment and Delivery Records

Payment, payout, transaction, shipping, and delivery records may be retained for accounting, dispute resolution, fraud prevention, and compliance with applicable law.

12.6 Diagnostics and Security Logs

API error records, diagnostics, authentication logs, and security logs may be retained for a limited period necessary to diagnose problems, prevent abuse, and maintain security.

12.7 Backups

Deleted information may remain temporarily in restricted backups until the backups are overwritten or securely deleted according to our normal backup cycle.

12.8 Required Retention

We may retain limited information after account deletion where reasonably necessary for:

Legal compliance;
Fraud prevention;
Security;
Dispute resolution;
Enforcement of agreements;
Financial or transaction records.

Where possible, retained information will be restricted, minimised, or de-identified and will not be used for unrelated purposes.

13. Account and Data Deletion

Users may request deletion of their Glenn account and associated data.

13.1 Delete Through the App

The account-deletion option is currently not available in app

13.2 Delete Through the Website

Users who cannot access the application may request account deletion through:

Account deletion page: https://www.glennesports.app/delete-account

The external deletion page must allow a user to submit a request without requiring the application to be reinstalled.

13.3 Delete by Email

Users may also contact:

Email: glennesports7@gmail.com

The request should include sufficient information to locate and verify the account, such as the registered email address or Glenn username.

Do not send passwords, OTPs, UPI PINs, or other secret credentials.

13.4 Verification

We may need to verify that the person submitting the request owns or is authorised to act for the account.

Verification is used to prevent an unauthorised person from deleting another user’s account.

13.5 What Is Deleted

Subject to applicable law and legitimate retention requirements, account deletion may include deletion or irreversible de-identification of:

Account information;
Profile information;
Posts and comments;
Social relationships and interactions;
Messages associated with the account;
Location information;
Notification identifiers;
Payment or payout information not required to be retained;
Other data connected to the account.

13.6 Processing Time

We will process verified deletion requests without unreasonable delay and within any period required by applicable law.

Some information may remain temporarily in backups or be retained where legally required, as explained in the Data Retention section.

14. User Choices and Rights

Depending on location and applicable law, users may have the right to:

Access personal information;
Receive information about how it is processed;
Correct inaccurate information;
Update profile details;
Delete content;
Request account and data deletion;
Withdraw consent;
Restrict or object to certain processing;
Request a copy or summary of personal information;
Submit a complaint or grievance;
Nominate another person to exercise applicable rights where legally available.

Users may exercise available in-app controls or contact us using the details in the Contact section.

We may request reasonable verification before completing a privacy request.

Some requests may be limited where information must be retained for security, legal, financial, or dispute-resolution reasons.

15. Permission Controls

Users can control certain data collection through their device settings.

15.1 Location

Location permission can be disabled through Android settings. Location-based features may stop working.

15.2 Notifications

Push notifications can be disabled through device settings. Users may still receive necessary in-app notices.

15.3 Camera, Photos, and Media

Camera or media access can be disabled. Users may then be unable to upload profile photos, posts, screenshots, or message attachments.

15.4 Profile and Public Content

Users may edit or remove profile information and content through available application controls.

16. Children and Teenage Users

Glenn is intended for users who are at least 13 years old.

However, the age at which a person can independently consent to processing of personal data may be higher under the laws of their country. In India, additional legal requirements may apply to users under 18.

Where applicable law requires parent or guardian authorisation, a user may use Glenn only after the required valid consent or authorisation has been obtained.

Users should not create an account if:

They are below the minimum permitted age;
They are unable to provide valid consent;
Required parent or guardian consent has not been obtained.

Parents or guardians who believe that a child has provided personal information without the required permission may contact us at glennesports7@gmail.com.

After reasonable verification, we will take appropriate steps, which may include restricting or deleting the account and associated information.

We do not knowingly use children’s personal information for behavioural advertising.

17. Advertising and Marketing

Glenn does not currently use personal information for third-party targeted advertising.

If advertising or marketing SDKs are introduced in the future, we will update:

This Privacy Policy;
Applicable consent controls;
Google Play Data Safety disclosures;
Any required in-app disclosures.

We may send communications about Glenn features, tournaments, events, or services where permitted. Users may disable optional promotional notifications through available settings or device controls.

Service, security, transaction, and account notices may still be sent where necessary.

18. Data Breaches

If we become aware of a personal-data breach, we will take reasonable steps to:

Investigate the incident;
Limit unauthorised access;
Protect affected systems;
Preserve relevant evidence;
Notify affected users or authorities where required by applicable law;
Take steps intended to prevent recurrence.

Notification may be sent through the application, email, push notification, website notice, or another appropriate communication method.

19. Third-Party Links and External Platforms

Glenn may contain links to:

Social-media platforms;
Tournament websites;
Gaming services;
Payment applications;
Courier tracking pages;
Sponsor or partner websites;
Other external services.

We are not responsible for the privacy, security, availability, or content of independent third-party services.

Users should review the privacy policies of those services before submitting information.

20. Changes to This Privacy Policy

We may modify this Privacy Policy at any time to reflect:

New features;
Changes in data practices;
Changes in service providers;
Security improvements;
Legal or regulatory requirements;
Business or operational changes.

The updated policy will show a revised “Last Updated” date.

The updated version may become effective when it is published, unless a later effective date is stated.

For material changes, we may provide notice through:

An in-app notice;
A website notice;
Email;
Push notification;
Another reasonable communication method.

Where applicable law requires fresh consent before a materially new use of personal information, we will request that consent.

Continued use of Glenn after an updated policy becomes effective constitutes acknowledgement of the updated policy to the extent permitted by applicable law. It does not override consent requirements or other rights provided by law.

Users are encouraged to review this Privacy Policy periodically.

21. Grievance and Complaint Process

Users may submit privacy concerns, grievances, or complaints using the contact details below.

Privacy or grievance contact: Anjali Sharma Email: glennesports7@gmail.com

Please include:

The registered email address or Glenn username;
A description of the request or complaint;
Relevant screenshots or reference information, where appropriate.

Do not include passwords, OTPs, UPI PINs, CVVs, or other secret credentials.

We will review and respond within a reasonable period and within any period required by applicable law.

22. Contact Us

Questions about this Privacy Policy or Glenn’s handling of personal information may be sent to:

Glenn / Glenn Esports Operator: Anjali Sharma Privacy email: glennesports7@gmail.com Support email: glennesports7@gmail.com Website: https://www.glennesports.app Account deletion page: https://www.glennesports.app/delete-account

23. Summary of Important Choices

Users can:

Edit profile information through Glenn;
Delete posts or other content where controls are available;
Disable location permission;
Disable push notifications;
Block or report users;
Request access or correction;
Request permanent account deletion through the app or website;
Contact Glenn about privacy concerns.

This summary does not replace the full Privacy Policy above.