Business Code Privacy Policy
Version 1.0 — November 4, 2026
1. Controller and scope
1.1. This Policy explains what personal data is processed when people use the Business Code mobile application (the “App”), why it is used, with whom it is shared, how long it is retained, and how Members can exercise their rights. The App is intended for people aged 18 or older.
1.2. The controller is individual entrepreneur Olesya Andreevna Dmitrieva, OGRNIP 325784700140609, INN 780719584877. Address: Apartment 5, Building 1, Structure 1, 45 Leninsky Prospekt, St. Petersburg 198511, Russia. Privacy contact: Dc-agent@yandex.ru.
1.3. The App is published on the App Store under AnikinTech LLC (Georgia). Development and technical support under Russian contracts are performed by individual entrepreneur Milina Viktorovna Anikina. Actual functions and contractual responsibilities, not the name displayed in the App Store, determine who handles personal data and in what capacity.
1.4. Processing is subject to applicable law, including Russian Federal Law No. 152-FZ on Personal Data. Where mandatory privacy protections of another country apply to a Member, this Policy does not waive those protections.
2. Personal data we handle
The categories depend on the features used:
- Sign-in and account information: the email address used to receive a one-time code and code-verification records, or an Apple sign-in identifier; account identifiers, a #BC member code, registration date, language, session information, and consent records. Email and Apple are separate alternative sign-in methods; accounts are not automatically merged.
- Profile information Members provide: name, photo, company and position, industry, city, professional interests, profile description, website, onboarding answers, and visibility settings.
- Optional contact details for sharing: email, phone number, and Telegram handle. A phone number is not required to sign in. The current App does not access the device address book to discover contacts.
- Messages: direct messages and community room content, sender and recipient identifiers, timestamps, read status, deletion markers, reporting data, and blocking records.
- Requests and connections: business requests, responses, suggested introductions, connection requests, connections, blocks, and related profile characteristics.
- Events: invitations, RSVPs, event passes, and related participation information.
- AI features: Member-entered text for profile or request assistance, relevant inputs for introduction suggestions, separate AI consent records, and technical records of AI feature use. Free text may include information entered by the Member.
- Device and security data: IP address, session and device identifiers, app and operating system versions, request times, security events, operational logs, and an Apple Push Notification service (APNs) token when push notifications are enabled.
- Support and moderation: contact information, support messages, report details and associated context, and moderation outcomes.
We do not ask Members to provide health information, religious or political beliefs, biometric information, or payment details. However, a Member may enter sensitive information in free text; please do not include it in profiles, messages, or AI requests. Version 1.0 offers no purchases or paid subscriptions.
3. Purposes and legal grounds
3.1. Data is used to register and secure accounts, operate community features, display profiles according to visibility settings, suggest professional introductions, deliver messages and notifications, organize events, respond to support requests, review reports, prevent misuse, maintain the service, record consents, and comply with legal duties.
3.2. Depending on the activity, processing may be based on performance of the Terms of Use, separately obtained consent, a legal obligation, or another ground allowed under applicable law. Accepting the Terms is not a substitute for consent where consent is required.
3.3. Members select which supported profile fields are shared with other Members. Optional contact details are disclosed to a particular Member only after both agree to exchange them. Visibility inside the community does not authorize republication outside the App.
3.4. Separate informed consent is required before sending information to a third-party AI provider. Without that consent, AI-assisted features are disabled, but manual profile and request forms remain available.
3.5. The App may show editorial advertising and partner content. Members' personal data is not sold to advertisers. The App does not use IDFA to track people across other companies' apps.
4. Who can access information
4.1. Other Members can see a #BC code and the profile fields made visible to them through the Member's settings. Optional contact details are exchanged with a particular person only with mutual consent.
4.2. Community room messages are visible to its Members. Direct messages are accessible to their participants; authorized editorial personnel may access a message and limited context to investigate a report, respond to a safety issue, or meet a lawful requirement, subject to applicable access controls.
4.3. Members can report content, block another Member, and hide or delete their own messages in the interface. These actions do not automatically erase all retained records described in Section 7.
5. AI features
5.1. With separate consent, the App uses GigaChat models hosted by Cloud.ru (ООО «Облачные технологии», Cloud Technologies LLC) to help draft profiles and business requests and suggest professional introductions.
5.2. Only data needed for the selected function is sent. Text voluntarily entered by a Member can include personal or sensitive information. Do not enter other people's contact details, confidential business information, or sensitive personal data into AI requests.
5.3. AI output is advisory. Members can withdraw AI consent through Me; new requests and AI matches then stop, and related matching vectors are deleted from the active system. Technical records and backups are handled under the applicable retention periods.
6. Providers, location, and transfers
6.1. The App's primary servers and database are hosted in Russia using Timeweb Cloud. Backups use the service's protected technical infrastructure. Authorized technical service providers have access only to the data needed for their responsibilities.
6.2. The providers involved in specific functions include: individual entrepreneur Milina Viktorovna Anikina for development and support; Timeweb Cloud for infrastructure; Cloud.ru for consent-based AI functions; Apple for Sign in with Apple, push delivery, and revocation; and the Anitech/Hostinger mail infrastructure for one-time email codes when email sign-in is enabled. Each provider receives information appropriate to the feature it operates.
6.3. Sending a sign-in code requires sharing the recipient's email address and delivery information with the mail provider. Apple services may process sign-in identifiers, push tokens, and brief notification text. Direct-message bodies are not included in push notifications. Using international service providers can involve limited transfers outside Russia, subject to the procedures required by applicable law.
6.4. Member profiles are not made into publicly accessible web pages. We do not sell Member data. Information may be disclosed to public authorities only when there is a lawful basis and in the legally required manner.
7. Retention
7.1. Active account details, profiles, photos, contact details, and connections are kept while the account or relevant processing purpose exists. On account deletion these are removed from the active working system; some records with a separate legal basis or retention period may remain as described below.
7.2. Message content, including messages hidden from the user interface, may be retained for up to six calendar months from sending. Records of message transmission, participants, and timing may be retained for up to three years for service-related purposes and where applicable retention duties require it.
7.3. Consent records may be retained during the consent period and for up to three years after withdrawal, where needed to demonstrate lawful processing. Resolved complaints may be retained for up to one year after resolution; support correspondence for up to one year after closure, unless a different lawful period applies.
7.4. Encrypted backups follow a rotation cycle of up to 30 days. Restoring data from backups requires applying current account deletions and access restrictions. Certain technical information needed to retry revoking a Sign in with Apple authorization may be stored temporarily for up to 30 days.
7.5. Operational logs are kept for limited periods needed for security and troubleshooting. Records covered by the special message-retention purpose are subject to the period described in Section 7.2. Where mandatory law requires earlier deletion or longer preservation, that rule applies.
8. Member rights and consent withdrawal
8.1. Members may request access to information about how their data is processed, correction, restriction, or deletion where provided by law, and may withdraw a consent where that consent is the ground for processing. Send requests to Dc-agent@yandex.ru. To protect an account, the Operator may ask for evidence of account ownership, but will not ask for passwords or one-time sign-in codes.
8.2. Me in the App lets Members manage profile visibility, withdraw AI consent, and use Delete Account. Push notifications can be disabled in iOS settings. When an essential processing purpose cannot continue without the account, the account can be closed through the deletion feature.
8.3. After deletion, the profile is no longer visible to ordinary Members; limited messages, technical records, moderation files, consent records, and backups may remain for the periods above. Privacy requests are handled within the time limits of applicable law.
9. Security
The service uses HTTPS, access controls, server-side authorization checks, abuse-prevention measures, backups, and restricted access to operational data. No online service can promise absolute security. Keep your one-time codes private and do not share others' personal information without authorization.
10. Updates and contact
This Policy may change when features, providers, retention arrangements, or legal requirements change. The current version is available in the App and on the public privacy page linked from its App Store listing. New consent will be requested separately whenever required for the changed processing. Operator: individual entrepreneur Olesya Andreevna Dmitrieva. Mailing address: Apartment 5, Building 1, Structure 1, 45 Leninsky Prospekt, St. Petersburg 198511, Russia. Email: Dc-agent@yandex.ru.