Privacy policy

1. Scope of this policy

This policy describes the account, discovery, business and community services available on the Local22 website. Purposes of data processing, legal reasons and data controller information Data protection notice It is located inside. This policy is not a general express consent form.

Data controller

Torenstech Medikal ArGe Ltd. Şti.

Notification address

The address to be verified by the operator will be added.

Application channel

dorukkarlikaya@tv25.app

2. Account and access security

A secure digest of your name, email address and password appearing in the registration is processed. Your password is not clearly saved in the database. Email verification code is valid for 10 minutes. Password reset is done via a 20-minute single-use link sent to your verified address; no permanent recovery key is used.

When changing the password, user and administrator sessions are logged out. Admin login requires separate login and authentication application. Authorization checks are applied; Absolute security cannot be guaranteed for any digital service. Do not share your password, email code or renewal link with anyone.

3. What information is visible?

Your login email and password digest are not public profile fields. The business contact information, address, descriptions, listings and community content you publish appear on the relevant pages. Do not add home address, private phone number, identity document or confidential information belonging to someone else in open fields.

Business applications are reviewed by the system moderator. Being a team member in a business does not give you system administrator authority. Moderation notes and representation statements are used within the scope of authorized panel access. Having a sourced directory record does not mean that the business is a platform member or approved representative.

4. Email and external services

Transactional emails are sent via Resend for registration verification, account creation, password transactions and application updates. For these messages, your address and the necessary notification content are transferred to the service provider. Creating an account does not mean you consent to advertising or marketing messages.

The application uses Vercel and Cloudflare infrastructure. Map pages can load Google Maps or OpenStreetMap content; The external provider may receive technical request information during the connection. Representative images sourced from Unsplash are used in sample listings. Third party sites apply their own privacy rules; The application reserves the responsibility for its own transfers.

Login with Google and linking Google ID to existing account is available. Account ID and email information verified by Google are processed for login and account matching purposes; Your Google password is not given to Local22. Signing in with Google alone does not provide access to Google Calendar. Meta and Apple logins are closed. Google Places integration is not yet active.

4.1. Google Calendar connection and data usage

This section was updated according to the current technical operation on September 28, 2026. The Google Calendar link is optional; It is only open to permitted test accounts during the verification process. You can also use My Local Calendar without connecting your Google account.

You also give consent on the Google consent screen during connection. The calendar list is read for you to select calendars for which you have authoring authority. A separate Local22 Google calendar will be created upon your request. Event read and write permission is used to bi-directionally synchronize creation, editing, and deletion across calendars of your choice. While Google's permission scope can provide access to events from all calendars, Local22 only transfers calendars that you've paired and kept sync turned on.

Title, description, location, start and end time, full day information of mapped events; calendar and event IDs and synchronization status are processed on the server and stored in the Local22 database. This version does not save attendee lists as a local event venue or send invitations; It does not convey recurring series of events. Local events created from business appointments can also be transferred within the selected calendar mapping.

The Google refresh token is stored encrypted on the server; is not given to the browser. Activity data and matching records are processed through Vercel and Cloudflare for the purpose of operating the service. Selected local events are sent to Google; Changes from Google are imported into Local22. This data is not used for ad targeting, data selling, credit assessment, or general purpose AI model training. Local22's use and transfer of data from Google APIs, including limited terms of use Google API Services User Data Policy It is limited to .

You can pause each calendar synchronization individually. Removing the calendar link via Settings or My Local Calendar stops syncing and removes the stored link token; Revocation of Google access permission is also attempted. If the permission cannot be revoked, the interface directs you to manage connections in your Google account. You can also remove Google permission directly from your Google account.

Removing the link will not automatically delete your calendar or events on Google and existing local copies on Local22. Local events can also be deleted. Deleting activity on an active peering may also delete activity on the other side on the next sync. Technical deletion and matching records can be kept so that the deletion process can be applied to both parties; Requests for full data deletion are handled through the account requests process below. Synchronization works at your request and while the calendar page is visible; There is no continuous transfer when the browser is closed.

5. Storage and accounting requests

Temporary account and security data durations in the storage section is explained. Archiving content does not permanently delete data. This version does not have an automatic user button for account deletion. Deletion, correction and access requests KVKK application process It can be sent to dorukkarlikaya@tv25.app within the scope of

6. Cookies and modifications

Cookies used for session and registration Cookie policy listed in. The version and date of the policy are shown at the top of the page. Updating the text does not replace the permissions that must be obtained separately.