Gjej Bej

Privacy Policy

Last updated: 2026-09-09

This policy explains how Hanxhelo Spahiu handles personal data when you use the Gjej Bej mobile app and gjej-bej.al. It covers accounts, community events and related support. The service is launching in Albania.

1. Who is responsible

Hanxhelo Spahiu is the individual responsible for personal data processed for Gjej Bej in Albania. Gjej Bej is a service name, not a registered company. Contact gjejbej@gmail.com for privacy and support. A public correspondence address has not yet been provided.

2. Information we handle

Account and profile: your account identifier, email, name, profile photo, chosen interests, language, phone number and phone-verification status. Depending on your sign-in method, we also handle authentication tokens, verification requests and password-authentication records. Apple or Google may provide an identifier, name, email or profile image according to your choices with that provider.

Community activity: event titles, descriptions, photos, categories, dates, meeting points and coordinates; events you create, save or join; attendance requests, approval status and ratings when you use those features. Event admission amounts are event information, not card-payment details.

Device and service information: push-notification tokens and preferences, device/platform information used to deliver notifications, and technical connection information such as IP addresses and request/error logs processed by our hosting and service providers.

Support: the email address, messages, attachments and account or event details you choose to send us. Do not send passwords, sign-in codes, identity documents or sensitive information unless we specifically explain why it is needed and how to provide it safely.

We record your account ID, the version and language of accepted terms, the client used and the server time of acceptance. This records the service agreement; it does not authorise optional tracking or marketing. The receipt is kept with your account and removed when the account record is deleted.

3. Location, photos and permissions

If you allow location access, the app can use your current location to centre the map and help you find activities. You can decline or revoke location permission in your device settings. A meeting point you choose for an event is stored with that event; it is different from your device's live location.

Google Maps loads automatically in map views on iOS, Android and web when configured. Google receives map areas and connection data such as IP addresses even without GPS permission. Nominatim/OpenStreetMap handles place searches and names for selected points, receiving the query or coordinates and connection data. Device location permission is a separate choice.

When you choose a profile photo or event image, the selected media is uploaded for that feature. The app may request photo-library access. It does not upload your entire photo library. You can manage permissions in device settings. Avoid images containing private information or people who have not agreed to be shown.

4. Why we use information

We use account and activity information to sign you in, verify contact details, maintain your profile, display events, process participation requests, show saved and created plans, and provide support. Selected interests help order relevant events and places; you can change those interests.

We use technical information to operate the service, troubleshoot failures, protect accounts and investigate misuse. We use push tokens to deliver event or account notifications when enabled. Essential verification emails and SMS messages support sign-in and phone verification.

Account access, profile changes and event participation use information needed to provide the service you request (performance of the service contract). Security and abuse prevention rely on legitimate interests, balanced against your rights; legally required disclosures rely on the relevant legal obligation. Optional location access and consent-based features require a separate choice. Terms acceptance is not consent to marketing. You can withdraw a consent-based choice without affecting earlier lawful processing.

5. What other people can see

Public events and their displayed organizer names can be viewed by visitors. Private events are visible to the organizer, approved participants and signed-in recipients who accepted a still-valid invitation. Invitations can be forwarded: anyone with the link may accept until expiry or revocation. Revocation does not remove already approved participants. New event photos use protected storage and access checks; avatars and legacy public photos remain public. Copies already received cannot be recalled.

When you join an event, your participation information may be visible to the organiser and, according to the event's settings, other participants. Anonymous attendance changes how you appear to others; it does not make your account or activity anonymous to the service.

The contact feature shares verified phone numbers between an organiser and approved participants for event coordination. When you choose Call, SMS or WhatsApp, your device opens that service and its own privacy rules apply. Recipients may keep information they receive, and we cannot recall copies or screenshots they have made.

6. Service providers and disclosures

We use Supabase for authentication, database and media storage; application/API hosting services for the website and backend; email and SMS delivery providers for verification; and Expo, Apple and Google services where needed for sign-in or push delivery. Map services and external image hosts receive connection data when their content is loaded.

These providers process information needed for their services. The data they receive depends on the feature you use and the deployed configuration. Contact us to request details of the providers relevant to your account.

We may disclose information when a valid legal duty requires it, to address fraud or threats to people or the service, or in a business transfer subject to applicable data-protection requirements. We do not use the app to collect payment-card information; payments for events are arranged outside Gjej Bej.

7. Cookies and local storage

The shared web app stores gjejbej.session in session storage until sign-out or the tab session ends. Language preferences persist separately. The previous Next.js site may still have gjejbej-auth and sb-…-auth-token in local storage; see the Cookie Policy for the distinction.

We have not integrated advertising or visitor-analytics SDKs in this release. Website maps load automatically when you open a view containing a map. Device location permission is separate. This notice is not consent to advertising. The mobile app uses device storage and native map services as described in the Cookie Policy.

8. Retention and international processing

Account information is kept while needed to provide your account and related services. Event and participation records, uploaded media, support correspondence and technical logs may have different retention needs. We consider the purpose, whether an account or event remains active, security needs, legal duties and dispute-resolution requirements when deciding how long information is needed.

A deletion request is reviewed against those needs; some records may need to be retained or anonymised, and backup copies may remain until the provider's backup cycle expires. We will explain relevant retention exceptions when responding to your request. We do not promise immediate deletion from every backup.

Hosting and other providers may process data outside Albania. Applicable transfer requirements and safeguards depend on the destination and provider. You may contact us for information about the locations and safeguards applicable to your data.

9. Your choices and privacy requests

You can change available profile fields and interests in the app, leave events, and manage location, photo and notification permissions in device settings. Signing out or uninstalling does not delete your account.

To request access, correction, deletion of your account and associated personal data, restriction, portability, or to object to processing, write to gjejbej@gmail.com. Use the email associated with your account where possible and describe your request. A parent or guardian may contact us about a child's data. We may ask for proportionate information to verify authority or account ownership; do not include passwords or verification codes.

Your rights and any exceptions depend on applicable law. You may also complain to Albania's Information and Data Protection Commissioner at idp.al. Requesting help from us does not prevent you from contacting the Commissioner.

10. Children and young people

The minimum age for Gjej Bej is 12. Anyone under 18 must have a parent or legal guardian's permission and supervision when using the service or attending an event. Children below 12 must not create an account.

A minimum age in these terms is not proof of a child's age or of parental authorisation. Where the law requires parental authorisation for consent-based processing, that authorisation must be obtained and verified before the relevant processing. A child's agreement to this policy or a device permission is not a substitute.

Parents and guardians can contact gjejbej@gmail.com to ask about their child's data or request deletion. If you believe a child below the minimum age has provided information, let us know so we can investigate. Young users should not share a home address, school, private location or contact details publicly, and should involve a trusted adult before meeting anyone.

11. Security and updates

We use access controls, authentication and encrypted network connections to protect the service. No online service can guarantee absolute security. Keep your account credentials private and contact us if you suspect misuse.

We may update this policy as the service or legal requirements change. The date and version identify the current text. Material changes requiring notice or consent will be handled as required by applicable law.

Shared expenses and service messages

When the organizer enables shared expenses, approved participants can see descriptions, amounts, currency, payers, shares and recorded repayments. Leaving the event does not erase historical debts; historical names and shares remain to keep balances accurate. We do not move money or exchange currencies. Do not enter confidential financial details in descriptions.

Completed signup creates one welcome message. Join requests, decisions, cancellations and material time or location changes create inbox updates and service email, plus push when permitted and available. Disabling push does not stop necessary service email. We do not send marketing, inactivity reminders or routine expense notifications.

The configured service-email provider (current adapter: Resend) receives the destination address and message content. We retain the message and technical delivery state to prevent duplicates and resolve delivery problems. Provider acceptance does not prove that the recipient read the message.

gjejbej@gmail.com