Syntoks Русская версия

Syntoks Privacy Policy

Version dated 2 November 2026

1. Data Operator and Scope

The personal data operator is ООО «СИНТОКС» (Syntoks LLC), Russian Taxpayer Identification Number (INN) 7806619871, Primary State Registration Number (OGRN) 1247800049529, Tax Registration Reason Code (KPP) 780601001.

Address: Apartment 52, Building 2, 1 Yakornaya Street, Saint Petersburg, 195027, Russia.

Contact for personal data matters: support@syntoks.com. Written requests may also be sent to the operator's address.

This Policy describes how Syntoks handles users' data relating to accounts, public synths, private correspondence, wallets and Web3 transactions, as well as data relating to people who contact support. The Policy page is https://syntoks.com/privacy; the English version is at https://syntoks.com/en/privacy.

The service is intended for people aged 18 or older. This age requirement does not mean that every user's identity is verified using documents. The initial release operates on the Ethereum Sepolia test network; account information, correspondence and uploaded files nevertheless remain real user data.

2. Data and Purposes of Processing

PurposeInformation processed
Account creation and sign-inGoogle identifier and email address, or Apple identifier and email address (a private Apple relay address if the user chose “Hide My Email”), or an external wallet address; sign-in events and session information
Profile and participation in the serviceUsername, first name, last name and date of birth; photos, interests, profile description and social media links supplied by the user; roles and participation in synths; list of blocked users; version and time of acceptance of the Community Guidelines
Communication and publishingMessages in synths and private chats, files, cover images, reactions, polls and votes, synth settings and prices
Built-in walletPublic address, data used to generate the key, the encrypted key and server-side means of decrypting it
External wallet connection and sign-in verificationAddress, network, one-time message, nonce, issue, expiry and use times, and association with the account; the signature is used for verification
Executing and recording transactionsSender and recipient addresses, asset, amount, fee, transaction hash and status, information about NFTs, listings, bids and account associations
App operation and securityIP address, browser or app information, operating system, session tokens, request events and times
NotificationsPush token, sender's name, message text, synth name, wallet and NFT events
Analytics and diagnosticsInstallation identifier, device model, operating system, app version, language, country, app launch, session and screen events, errors and diagnostic records
Requests and complaintsRequester's contact information, the content of the request, relevant materials and information about how it is handled; for an in-app report — who reported, whom, the reason and a copy of the reported message text; a report flag on the reported user's account

The registration form asks for a first name, last name, username and date of birth. Data comes from the user, their actions in the app, sign-in methods, services used and the public blockchain network.

Uploaded photos and files retain their original metadata, which may include the location where a photo was taken. Location information may therefore be included in a file even if the app does not separately request access to geolocation.

Posts may contain information about health, beliefs and other sensitive matters. Do not post another person's personal data without an appropriate basis. Posting data does not, by itself, authorise every subsequent use of it.

The device's operating system performs biometric checks. Syntoks receives the result of the check, rather than a facial or fingerprint biometric template. User-uploaded photos may nevertheless contain images of people.

Syntoks does not display advertising or send advertising mailings. Firebase Analytics is used for statistics. The Android build includes permission to access the advertising identifier; the existence of that permission does not, by itself, establish that the identifier is actually collected.

3. Processing Methods and Grounds

Processing is automated and also involves staff when handling requests. Depending on the process, operations include collection, recording, storage, updating, retrieval, use, provision of access, blocking, deletion and destruction.

The applicable ground depends on the purpose: processing necessary to perform the agreement with the user, a statutory obligation, or separate consent where required. This Policy is not consent to any and all actions involving data and does not create a legal ground where none exists. Acceptance of the user agreement alone cannot justify optional processing.

Consent to processing and, where applicable, to the dissemination of personal data is obtained separately. Withdrawal of consent does not end processing for which an independent lawful ground remains.

4. Public Information and Private Correspondence

All synths are public. Synth cards may be accessible without signing in and may include the name, description, cover image, owner's information, prices and donation recipient address. Synth messages and public profile fields are accessible to signed-in users. Email addresses, dates of birth and Google and Apple identifiers are not public profile fields.

Private messages are displayed to the participants and processed by the server. There is no end-to-end encryption. Message text and the sender's name are transmitted to push notification providers and may remain in notifications that have already been delivered.

In the current implementation, files, including attachments to private correspondence, can be accessed without authentication by anyone who has a direct link. A link does not guarantee confidentiality. This limitation does not constitute consent to public dissemination of the content and does not remove the operator's data protection obligations.

5. Wallets and the Public Blockchain

The built-in wallet is custodial: the platform has the means to decrypt the key and signs transactions on the server. During creation, the recovery phrase is transmitted to the server to generate the key; the server does not retain the phrase itself afterwards. The phrase provided to the user does not enable standard recovery of the built-in wallet in an external app. Key export is not available.

When MetaMask or Trust Wallet is connected, the private key of the external wallet remains with the user. Syntoks processes the address, connection details, signature requests and transactions, but does not receive the external wallet's private key.

Addresses, amounts, transactions, approvals and information about contracts and NFTs are published on Sepolia. A link to an image is published for a synth token. The app does not write correspondence text or profile identifiers to the blockchain; IPFS is not used. A donation recipient address may be associated with the owner's name on a public synth card.

Deleting an account does not delete records from the independently operating blockchain. A public address associated with an identifiable person may be their personal data. The network's deletion limitations do not release the operator from obligations relating to data and account associations under its control.

6. Services and Recipients

The following services are used to provide Syntoks features:

ServicePurpose and information
Server hosting and S3 storageDatabase, files with metadata, logs and backups; the specific server hosting provider has not been identified, and the technical domain associates the S3 storage with FirstVDS
Google Firebase AuthenticationGoogle sign-in: Google profile data, UID and sign-in events; the provider's dataset is broader than the data held on the Syntoks server
Apple (Sign in with Apple)Sign-in in the iOS app: Apple provides the user identifier and email address, or a private Apple relay address at the user's choice; the Syntoks server verifies the sign-in token signature using Apple's public keys
Google Firebase Cloud Messaging and Apple APNsNotifications: push token, sender's name and message text, synth, wallet and NFT events
Google Firebase AnalyticsDevice and app usage statistics
Google Firebase CrashlyticsError reports and app diagnostic records
Google Firebase Remote ConfigConfiguration retrieval and installation identifier
Reown / WalletConnectConnection to an external wallet: address, network, IP address and signature requests
Alchemy and InfuraNetwork nodes: addresses, signed transactions, balance and status queries
MetaMask and Trust WalletOperation of the user's wallet app and confirmation of actions
TermsFeed, if the user opens the previous Policy linkBrowser network information when the page is opened
Etherscan, when its link is openedBrowser information and the explorer page being opened

Firebase and Reown communicate directly with the device. Notification text and node queries are also transmitted from the server. Diagnostic records in the current implementation may contain message text and session information; including this information is not, in itself, a separate necessary processing purpose.

CoinGecko is used by the server for exchange rates; transmission of account data to it has not been established. AI services and external facial or voice recognition are not used in the implementation described here.

Staff and contractors with administrative access may technically be able to access the database, messages and copies. Depending on their contracts and activities, providers may act as processors acting on the operator's instructions or as independent personal data operators. Naming a brand in the table does not mean that all of its products receive all Syntoks data.

7. Processing Locations and Cross-Border Transfers

According to the operator, the primary database is located in Russia. The countries where the replica, files, logs and backups are located, and where external providers actually process data, have not been fully established. Syntoks therefore does not claim that all data is stored exclusively in Russia.

Interaction with Google, Apple, Reown and the other listed providers may involve cross-border data flows. The operator has not reported other transfers outside this service map. This does not mean that cross-border processing through the named services is absent.

Cross-border transfers require separate compliance with statutory conditions; this Policy does not replace required notifications and assessments of recipients. The country in which a brand is registered does not automatically determine where data is processed.

8. Retention

The current implementation retains data as follows:

The absence of configured deletion is not an independent lawful ground for indefinite retention. Retention must be determined by the purpose and applicable ground; information cannot be kept solely because technical deletion has not been implemented.

9. Account Deletion and Its Consequences

Account deletion can be requested in the app through Profile → Edit Profile → Delete Account.

Deleting an account deletes the profile, built-in wallet keys, messages and some associated records. Deleting an owner's account may delete the synths they created, together with other participants' messages. S3 files, sessions, wallet sign-in records, the Firebase Authentication record and backups remain; voter identifiers may remain in poll data. Account deletion is therefore not equivalent to complete destruction of all personal data.

Deleting built-in wallet keys may cause the user to lose access to assets. Before deletion, users must consider access to remaining balances and pending transactions; recovery is not guaranteed. Account deletion does not destroy the user's external wallet.

Copies saved by other people, delivered notifications and public blockchain records may remain independently of Syntoks. These limitations do not override requirements to delete data under the operator's control where lawful grounds for deletion exist.

10. Requests and Rights

For data-related matters, contact support@syntoks.com or write to the operator's address. Users have the right to obtain information about processing, request correction, blocking or destruction where there are grounds to do so, withdraw consent, and contact Roskomnadzor or a court.

To establish the connection with an account, provide its identifier or other circumstances relevant to the request. Any additional information requested must be proportionate to the request. Do not send passwords, seed phrases or private keys to support.

Different types of requests are handled within the statutory time limits applicable to them. This Policy does not establish a single deadline for all requests or restrict mandatory rights. Account deletion, withdrawal of consent and a request for destruction of data are different actions; one does not replace consideration of another.

11. Protection and Policy Updates

The implementation uses server-side encryption of built-in wallet secrets and secure device storage facilities. End-to-end encryption of correspondence is not provided. Not all categories of data and copies are encrypted; the access and retention limitations described here do not relieve the operator of its personal data protection obligations.

Policy updates are published with a version designation. A change to the text does not, by itself, create a ground for new processing purposes or transfers. Where separate consent is required, publishing a new version does not replace it.

12. Company Details

ООО «СИНТОКС» / Syntoks LLC.

INN (Russian Taxpayer Identification Number) 7806619871 · OGRN (Primary State Registration Number) 1247800049529 · KPP (Tax Registration Reason Code) 780601001.

Apartment 52, Building 2, 1 Yakornaya Street, Saint Petersburg, 195027, Russia.

support@syntoks.com · https://syntoks.com