Updated: 2026-11-05 · 2026-11-05.1

Effective date: 2026-11-05

Privacy Policy

How Aroundify handles your information on the website, iOS and Android.

Who is responsible

Halil Burak Yılmaz operates Aroundify and is responsible for the personal data described here. Contact support@aroundify.app for privacy questions and rights requests. Aroundify is the product name, not a separate company.

What we collect and when

When you register or sign in, we receive your account identifier, email and authentication information from your chosen email, Google or Apple sign-in method. We process the profile fields and photos you submit, your selected language and preferences, and the content and relationships you create: messages, check-ins, events, comments, stories, traces, connections, business interactions, game activity and coupons. Notification providers process device tokens. Requests to our hosting, database, maps and media providers also disclose connection information such as IP address; analytics SDKs can collect device, app-instance and usage information automatically.

Purposes and legal grounds

We use account and feature data to provide the service you request, including authentication, discovery, messaging, events, games and coupons (performance of the service contract; GDPR Article 6(1)(b), KVKK Article 5(2)(c) where applicable). We process proportionate security, abuse-prevention, moderation and support data for legitimate interests, subject to your rights (GDPR Article 6(1)(f), KVKK Article 5(2)(f)). A specific legal obligation can require limited processing (GDPR Article 6(1)(c), KVKK Article 5(2)(ç)). Establishing, exercising or defending legal claims may rely on legitimate interests (GDPR Article 6(1)(f)) or KVKK Article 5(2)(e), where applicable. Optional processing that legally requires consent must use a separate choice; reading this notice or granting an operating-system permission is not blanket consent. We do not treat every feature as consent-based. Required account information enables sign-in; optional profile fields can be omitted. Without location access, location-dependent features may be limited. We use recent-location and relationship patterns for suggestions; these are not decisions producing legal or similarly significant effects.

Location, visibility and history

We request device location for nearby discovery or use a location you select. Obtaining a location, sharing a check-in on the map and storing check-in history are different activities. A visible check-in shares its selected location with the intended audience; ending its visibility does not itself erase its history. Recent retained locations support nearby notifications and suggestions. You can delete any history record, including the newest ten, or clear the history in settings. This does not end an active check-in or reverse game ownership. A coordinate-free processing receipt prevents a delayed event from recreating deleted history and is removed with the account. Public event and business locations can be visible to visitors as well as signed-in users, according to the selected audience.

Who can see information and service providers

Public social fields, chosen photos and content are shown according to the feature and audience; real-name profile details are limited to authorized friends. Account email, notification settings and private account fields are not part of the public profile. Conversations are limited to authorized participants. Message text is encrypted using server-managed keys: Aroundify servers can read it; this is not end-to-end encryption. Authorized personnel may process data for support, security or moderation. Firebase/Google Cloud provide authentication, database, Storage, hosting, analytics and notification services; Google/Apple handle selected sign-in methods, maps providers handle map requests, and external font/avatar services receive requests where used. Some providers may process data outside Türkiye or the EEA. Provider regions and applicable transfer arrangements must be confirmed for the relevant service; a European Functions region does not mean all data remains in Europe. We do not promise that an unverified contractual safeguard exists.

Analytics and choices

Usage analytics is off by default. Signed-in users can enable or disable it under Settings → Manage Analytics. The choice is stored privately with a preference version and update time and synced across devices. Measurement starts only after the account preference is confirmed by the server. Events can be associated with your Firebase account ID. Turning analytics off or signing out stops future app events and clears the analytics identity and available local analytics data; it does not delete data previously sent to Google. Google Analytics 4 and Firebase Analytics measure screen and feature use. Message text, email, real name, precise coordinates and search text are not intentionally sent as custom event fields. Public pages do not collect analytics. Operating-system location and notification permissions are separate from this choice.

Retention, local copies and deletion

Account and feature records remain for their operational purpose until you delete them or the applicable expiry/cleanup runs. Traces have a 72-hour application expiry; visibility expiry is distinct from immediate removal of backups or files. You can delete check-in history and your account through settings. Account deletion removes owned account/content/media and cleans related records; owned game areas become unowned. Other users retain independent data and coupon history; active coupons from a removed business are cancelled and the deleted operator identity is removed. Incomplete deletion keeps minimal retry progress. A temporary UID/expiry barrier prevents old login tokens from recreating data for 65 minutes after authentication deletion and is then eligible for scheduled cleanup. Local messages, search indexes and synchronization data are account-scoped and cleared at sign-out/account change; a legacy per-account device key is retained for reading old ECDH messages until account deletion. Offline devices detect deletion on reconnect. Provider backups, soft-deleted objects, technical logs and independently held support records follow separate retention processes; their exact periods are not confirmed here. We do not promise immediate deletion of every offline, in-flight or backup copy.

Your rights and requests

Write to support@aroundify.app to request access, correction, deletion, restriction, objection, portability or consent withdrawal where applicable. Include enough account information to identify the request; do not send your password. We may ask for proportionate identity verification. Under KVKK Article 11 you may ask about processing, purposes, recipients, correction/erasure and related notifications and other applicable rights. For GDPR rights you may also complain to a competent data-protection supervisory authority; Türkiye-related complaints may be addressed to the KVKK through the applicable process. Aroundify is for adults aged 18 or older. Rights requests, consent choices and acceptance of service terms are distinct.

Version and changes

This page identifies its content version and revision date. Material changes will be reflected in the published notice and relevant collection screens. A future company becoming the operator will require an updated controller notice, not a retrospective change to earlier facts.