Privacy Policy
TalkorX is only for users aged 18 and over.
This policy explains which personal data we process when you use the TalkorX app, talkorx.com and support channels, why, with whom we share it, how long we keep it and your rights. The controller is “NEUTRON TECH” LLC (“we”). Our notice under Turkish Personal Data Protection Law No. 6698 is also available on the KVKK Information Notice page.
At a glance
- We do not sell your data, show ads or track you across apps and websites. We do not use product analytics, advertising or automatic crash reporting; notification SDK service diagnostics are explained below.
- Messages and shared media are stored on our servers for delivery and device syncing. They are encrypted in transit, but TalkorX does not offer end-to-end encryption.
- Your phone number is not shown in your profile. Contacts, location, camera, microphone and photos are accessed only with your permission and for the relevant feature.
- Privacy settings let you choose who sees what, block people and delete your account in the app.
1. What data do we process?
Account and profile
- Your phone number (your account identifier).
- Your profile name, optional about text and profile photo.
- Privacy settings (last seen, profile photo, about text, who can add you to groups and read receipts), notification settings and app language.
Phone verification
We send a one-time SMS code to your number at sign-in. Our server keeps only its verification hash, not the code itself. On Android, we may fill the code from SMS with your consent; the app does not request permission to read your SMS messages.
Messages and shared content
- Text, photos, video, voice notes, documents, stickers, contact cards and locations you send; replies, edits, reactions, stars and pins.
- Delivery, read and played status; chat settings (mute, archive, pin and disappearing-message timer).
- Media technical information: file name, type, size, dimensions, duration, thumbnail, blurred preview and voice-note waveform.
- Photos and video are usually sent as the original selected file. Metadata such as capture location may be stored with the file and reach recipients. On iPhone, HEIC photos and MOV videos are converted when sent and this information is removed.
- Group names, descriptions, photos, members, roles and invitation links.
Contacts (optional)
If you grant access to your contacts, we send the phone numbers and names of the contacts you permit us to access to our server. This includes numbers of people who do not yet use TalkorX; these numbers are stored on our server for matching. Numbers are used to find TalkorX users and show them with the names you saved; people who join later are matched to their saved entries. With limited access on iOS, only the contacts you share are read.
Sync starts immediately after the first contact permission. When upgrading to this version, automatic sync is also enabled once on this device for accounts that previously granted contact permission. New or renamed contacts are synced while the app is in the foreground. You can turn off “Automatically sync contacts” in Settings > Privacy; your choice to turn it off is preserved across later app openings and permission changes. This preference belongs to the account on this device; after app data is cleared or the app is installed on another device, automatic sync may start again with a new permission.
Pulling down to refresh the People list reads contacts once and sends changes even when automatic sync is off. If the required access is missing, the permission flow is shown; without granting permission, you can still refresh the contact list already stored on the server. We do not write to your device's address book. Contacts removed from your address book are not deleted automatically; you are asked first.
Calls
- Call records: caller and recipient, voice or video, start, connection and end times, and end reason. Records appear in the chat and Calls tab.
- Call audio and video pass through a media server on our own servers and are not recorded. Connecting sends technical information such as device model, OS version and network type to the media server.
- Incoming-call notifications contain only call identifiers; the caller’s name is not sent to the notification provider.
- Call technical logs (optional): If you turn on “Send call logs to the server” in Settings > Help > Call diagnostics, the app sends the following technical information to our servers during calls so that we can fix problems: when the connection was set up, lost and re-established; connection-quality measurements (latency, jitter, packet loss, bitrate, video resolution, codec, and whether the connection is direct or goes through a relay server); the duration and error codes of server requests; microphone and camera state and permissions; the chosen audio output and the names the operating system shows for audio output devices (for example a Bluetooth headset’s name, which may be a name you gave the device); app version, OS version, device model and how far your device clock is from ours. This option is off by default; your phone does not send these logs unless you turn it on, and you can turn it off again at any time (see Your choices and rights). Regardless of this setting, our servers record state changes for every call (ringing, answered, connected, ended and why), joins and leaves on the media server, and call-notification delivery results. These logs contain no call audio, video or message content.
Location (only when shared)
- When sending a location: latitude, longitude and, if selected, place name and address are stored as part of the message.
- When sharing live location: you start sharing and choose 15 minutes, 1 hour or 8 hours. During that share, your location may also be sent to chat participants while the app is in the background or after you leave the chat. You can stop sharing at any time; it ends when your chosen duration expires.
- Live location updates are not written to the database. Only the latest point is kept in temporary memory and is deleted when sharing ends, no later than the end of your chosen duration (at most 8 hours). Recipients see the latest point and how long ago it was updated. The starting point is stored as part of the message, like a normal location, until the message is deleted.
- A record without coordinates stores who shared, in which chat, and when sharing started and ended. It remains while the message exists; routine cleanup deletes it once the message is deleted and 90 days have passed since sharing started. Device and session information in this record is removed immediately when you stop sharing, or within a few minutes after expiry.
Activity information
Online, typing and voice-recording status is kept in temporary memory for a few seconds, at most 90 seconds, to show chat participants. Last-seen visibility follows your privacy settings.
Device and technical information
- Device platform (iOS or Android), notification tokens (including incoming-call tokens on iPhone), notification language, last activity and sync times.
- Session information: session-key hash, expiry and last use.
- We do not store IP addresses in our database. To limit abuse and excessive requests, your IP is used briefly, mostly hashed (at most 1 hour). Web-server access logs contain time, method, status and processing duration, not IP, URL, query, request body or tokens. Logs rotate daily; at most 14 full archives and the active log are kept. Cloudflare’s own connection processing is described below.
Bots and link previews
- Selections and input from bot-card buttons or forms are sent to the bot’s owner.
- For shared links, we keep the URL, page title, description, site name and a small image for the preview card. This record does not identify who shared the link.
Reports
Reporting a message, person or group stores your report and a copy of the content: that message; the person’s profile name, about text, photo and last 5 messages in your chat; or the group name, description, photo and last 5 messages from other members. Copies include text, location or contact-card content and attachment records. If someone reports you, copies of your messages visible to them are kept in the same way, even if you later delete the message, until review ends. Only authorised staff read reports; the reported party is not informed.
Support correspondence
We process your email, correspondence and shared information to resolve your request. Mail to [email protected] is forwarded by Cloudflare Email Routing to our Google Gmail support inbox. Addresses, subject, content and attachments are processed by Cloudflare and Google in delivery. Do not share sign-in codes with support; the separate deletion code cannot be used to sign in.
Website visits
Marketing and legal pages do not require an account. They contain no advertising or product-analytics scripts. Cloudflare provides HTTPS and page delivery, and Google Fonts provides fonts; these services receive IP and connection information. Provider processing is detailed below. Your website language preference is stored only in your browser’s local storage to remember your choice.
2. What do we not collect?
- We do not collect advertising IDs or ask for tracking permission.
- We do not use Google Analytics, advertising or Crashlytics. Firebase notification SDKs process installation IDs, notification tokens, device and app information. They may also send SDK version, platform information and technical diagnostics to Google. These service metrics are part of the notification SDKs even with Google Analytics disabled.
- We cannot access Face ID, Touch ID or fingerprint data; your OS handles screen-lock authentication and only reports the result to the app.
- Local call diagnostic reports in the app stay on your device unless you share them with us. Call technical logs are separate and described above.
- We read the clipboard only when you tap “Paste”.
3. Data kept on your device
The app keeps a message copy in an encrypted local database for speed; its key is in secure device storage and is not transferred to another device. Downloaded media uses a cache of up to 5 GB, with old items removed automatically. The screen-lock PIN is stored only as a hash in secure storage. Signing out deletes local messages, media cache and diagnostics; pending messages and drafts remain locally for use only if you sign back into the same account.
4. Why do we use data?
- To create your account, verify your number and maintain a secure session.
- To deliver messages, media and calls; sync messages across devices; and send notifications.
- To find TalkorX users in your contacts, only if requested.
- To apply privacy settings, blocks and chat preferences.
- To secure the service and prevent and investigate spam, fraud and abuse.
- To diagnose call connection and quality problems and improve calls.
- To answer support requests.
- To comply with legal obligations and protect our rights.
We do not use your data for advertising, profiling or automated decisions affecting you.
5. What do other users see?
- Chat participants see the messages and media you send there. New group members see only messages after joining by default; administrators can choose to share earlier history when adding them.
- People you chat with see your profile name. Photo, about text and last seen are visible to everyone, only your contacts or nobody, depending on privacy settings.
- Your phone number is not shown in profiles or group member lists. Someone who knows it and saves it as a contact can find you on TalkorX.
- Disable read receipts in Settings > Privacy.
- Blocked people cannot see private profile details, send you direct messages or call you.
6. With whom do we share data?
We do not sell data. We share it only in the following circumstances:
| Recipient | Data shared | Purpose |
|---|---|---|
| Prelude Verify | Phone number, language and technical verification records | Send and verify sign-in codes by SMS |
| Twilio Inc. (USA) | Phone number and SMS text containing the verification code | Send request-specific account-deletion codes and sign-in codes when the fallback is in use |
| Google LLC – Firebase Cloud Messaging (USA) | Notification token and content. With message previews on (default), sender name, group name and up to the first 240 message characters; installation ID, device/OS/app information and SDK technical diagnostics | Deliver notifications to Android and iPhone and operate the SDK service |
| Apple Inc. – Apple Push Notification service (USA) | Notification token and content (as above); only call identifiers for incoming calls | Deliver iPhone notifications and incoming calls |
| Apple Inc. – Apple Maps (iPhone only) | Coordinates shown on the map and place searches when choosing a location | Display maps, find nearby places and addresses |
| Cloudflare, Inc. (USA) and Google LLC – Gmail (USA) | Support email sender and recipient addresses, subject, content and attachments | Deliver [email protected] emails to the Gmail support inbox and answer them |
| Cloudflare, Inc. (USA) | IP address, connection and HTTP request information when accessing the website | HTTPS, security and content delivery for talkorx.com and www.talkorx.com |
| Leaseweb (Netherlands) | All data stored on our servers | Server and storage infrastructure |
| Google LLC – Google Fonts (USA) | IP and HTTP request information when loading website fonts | Deliver the website’s Plus Jakarta Sans font to the browser |
| Group bot owners | Bot-card interactions; group messages if the administrator permits reading | Operate the bot added to your group |
- Notification previews: Turning off “Show message previews” in Settings > Notifications leaves only “TalkorX” in notifications; names and message content are not sent to Google or Apple. View-once notifications show only the media type.
- Link previews: Our server visits shared pages to prepare previews. Sites see our server’s IP, not yours.
- Open in maps: Tapping a location opens Apple Maps on iPhone or Google Maps on Android; those apps have their own privacy policies.
- Legal requirements: We may share information on lawful requests from competent authorities and as required by law. We report child-abuse content to authorities.
- Company changes: In a merger, transfer or sale, data may pass to a new owner subject to this policy; we announce it beforehand.
7. International transfers
Our app servers are on Leaseweb infrastructure in the Netherlands. SMS, notification, map, website and support-email providers (Prelude, Twilio, Google, Apple, Cloudflare) may process data outside Türkiye, including the USA. Countries in the table identify provider headquarters or verified server locations, not exclusive processing locations. We use these providers under their service and data processing terms, which contain commitments on the protection of personal data. The standard-contract and notification process under KVKK Article 9 is ongoing for each provider; see our KVKK Information Notice.
8. How long do we keep data?
| Data | Retention period |
|---|---|
| Messages and media | No time limit; stays on the server until deletion or the disappearing timer expires. Account deletion does not delete messages sent to others (see below). |
| “Delete for me”, clear or delete chat | Removes only your view; messages remain on the server for other participants. |
| “Delete for everyone” | Available within 1 hour after sending (no time limit for group administrators). Text and attachments are deleted immediately; a content-free “deleted” marker remains. |
| Disappearing messages | Deleted with attachments after the selected interval (60 seconds to 90 days). |
| View-once media | Shown once; the file remains on the server until message deletion or its disappearing timer expires. |
| Call records | No time limit. Deleting call history hides the record only from you; it remains for the other party. |
| Call technical logs | 30 days, then deleted automatically. If you delete your account, logs linked to your devices are deleted sooner. |
| Imported contacts | Until you remove them in the app or delete your account. |
| Reports and copied content | Until review ends; deleted 90 days after report closure. |
| Link previews | No time limit; does not identify who shared the link. |
| Verification codes | Sign-in and separate deletion codes expire after 5 minutes; deleted 1 day after expiry. Deletion codes are single-use, limited to 5 attempts and the target account. |
| Sessions | Your session does not end merely because time has passed or a device is inactive. It ends when you sign out, revoke the device’s access, delete your account or it is revoked for security reasons. A revoked session record is deleted by routine cleanup after 1 day. |
| Device records and notification tokens | A device is not automatically signed out for inactivity. Notification tokens are deleted when its access is revoked. Routine cleanup deletes the revoked device record 90 days after revocation once no related session, notification or call records remain; device records required by call records remain while those records exist. |
| Sync records | 30 days after delivery to your devices. |
| Notification delivery records | 7 days (no message content). |
| Bot interactions | Form input is deleted after 7 days; interaction records after 90 days. |
| Unsent uploads | Files not attached to a message are deleted after 24 hours. |
| Latest live location point | Only in temporary memory until sharing ends; at most the chosen duration (15 minutes, 1 hour or 8 hours). |
| Starting live location point | Part of the message; kept until the message is deleted. |
| Live location sharing record without coordinates | Kept while the message exists. Routine cleanup deletes it once the message is deleted and 90 days have passed since sharing started. Device and session information is removed immediately on stopping, or within a few minutes after expiry. |
| Typing and online status | At most 90 seconds, only in temporary memory. |
| Web-server access logs | Daily rotation; up to 14 full archives and the active file. Archives may have an older calendar age on days with no traffic. |
| Backups | 14 days; deleted data is also removed from backups by the end of this period. |
| Support correspondence and KVKK requests | Until resolution; closed correspondence is reviewed regularly and removed unless an ongoing dispute or legal retention requirement applies. Automatic mailbox deletion is not yet configured. |
When you delete your account
Deleted or closed immediately:
- Phone number, about text, photo and notification settings.
- All sessions and device records; notification and call tokens.
- Pending verification codes.
Deleted shortly afterwards in the background:
- You are removed from all chats and groups; group ownership passes to another member.
- Imported contacts, blocks, call-history preferences, bot interactions and unsent uploads.
- Call technical logs sent by or linked to your devices.
- Bots and app integrations are suspended and their secret keys deleted.
- Other people’s contact entries are unlinked from your account.
What remains:
- A group photo you uploaded that an active group continues using.
- Previously sent messages and media remain visible to others; they show a deleted account instead of your name. To remove them, use “Delete for everyone” before deleting your account.
- Reactions, read receipts and call records.
- Reports made by you or about you and their copied content, for the periods above.
- Copies on other people’s devices.
- Your phone number saved voluntarily in others’ contacts (no longer matched to your account).
Registering again with the same number creates a new, empty account with no access to old messages.
9. Security
- API, sync and file connections use TLS. Voice and video calls use WebRTC transport encryption and pass through the media server.
- Session keys, verification codes and view-once permissions are stored only as hashes; only the service itself can access server files.
- Local message copies use an encrypted database; you can also protect the app with screen lock.
- TalkorX does not use end-to-end encryption. Messages and media are stored on our servers without it; authorised staff access them only as needed to operate the service, investigate security incidents and comply with legal obligations.
- We notify the Turkish Personal Data Protection Board and affected users of a data breach as required by KVKK.
10. Your choices and rights
- Privacy settings: Manage last seen, photo, about text, group invitations and read receipts in Settings > Privacy.
- Permissions: Revoke contact, location, camera, microphone, photo and notification permissions in device settings at any time.
- Contacts: Turn off automatic sync in Settings > Privacy and remove imported contacts in the app.
- Notifications: Turn off message previews in Settings > Notifications.
- Account deletion: Settings > Account > Delete account. Without app access, use the support page.
- Call technical logs: Sending these logs from your phone is off by default. Turn “Send call logs to the server” on in Settings > Help > Call diagnostics, and off again at any time; when you turn it off, logs not yet sent are discarded. The state records our servers keep for the call itself (above) are kept regardless of this setting.
- KVKK rights: See our KVKK Information Notice for access, correction, deletion and other rights.
11. Children
TalkorX is not for under-18s. We delete accounts if we learn that a child below this age has registered. Tell us through support if you know of such a case.
12. Changes
We may update this policy as the service or law changes. Important changes are announced in the app or on this page before taking effect. The current version is always on this page.
13. Contact
“NEUTRON TECH” LLC (Ukraine)
Company registration number (EDRPOU): 43847224
15 Chervonopilska Street, Kyiv, 04123, Ukraine
Support: [email protected]
Personal data requests: [email protected]