01Operator and scope
비엔비에셋 주식회사 (the “Company”) operates TradeOps AI, a B2B service for post-trade operations. This policy distinguishes information used for accounts, inquiries and service administration from customer business data.
The Company is responsible for personal information processed for its own account administration, contracts and inquiries. It processes customer business email and documents under lawful customer instructions and processing agreements. Actual contracts and data flows determine controller, processor and subprocessor responsibilities.
| Item | Details |
|---|---|
| Registered operator | 비엔비에셋 주식회사 |
| Representative | 김복기 |
| Business registration number | 333-87-02438 |
| Business and postal address | 서울특별시 서대문구 신촌로 25, 2층 2127호(창천동) (Room 2127, 2nd floor, 25 Sinchon-ro, Seodaemun-gu, Seoul, Republic of Korea) |
| Contact | ayden@bnbcompany.io · +82-2-6672-3905 |
02Purposes and lawful bases
We process information to issue accounts, verify users and organizations, manage roles, protect sessions and prevent misuse; organize authorized email, attachments and documents as evidence for trades, vessels, deliveries, payments and settlements; produce extraction, classification and matching candidates through enabled AI; maintain review and change history; provide support and administer contracts; and meet legal duties or protect rights.
Account, organization and access information is necessary for contract performance and security. Optional connections and AI processing operate within customer-selected scope, lawful instructions and any required consent. Inquiries are processed to answer the person who provided contact details. Each purpose requires an applicable lawful basis. A customer contract or account-owner OAuth consent does not authorize every use of correspondents’ or document subjects’ information. Customers must obtain appropriate authority, notices and consent; the Company remains responsible for its own obligations.
03Information and collection methods
| Category | Information | Source and use |
|---|---|---|
| Accounts and organizations | Name/display name, login email, organization, user/role identifiers, password verification hash, account state | Customer administrators or users; authentication and access control |
| Connections | Verified provider account identifiers/display information, consent/connection state, access and refresh tokens, one-time OAuth validation information | Google/Microsoft OAuth; we do not request provider passwords |
| Message ID/version, subject, sender email, received time, text body, hash, change/deletion markers and synchronization state | APIs within the configured account, folders and period | |
| Attachments/documents | Filename, type, size, content, hash/version, processing/quarantine state; content may include contacts, signatures or trade information | Attachments and authorized uploads |
| Business/AI results | Trade/assignee information, notes, work state, source references, extraction/classification/matching candidates, review/change history | Customer input, connected data and enabled analysis |
| Security/operations | IP-based access-limit information; request identifiers, timestamps, paths/results and audit actor/organization references | Authentication and processing; source content, authorization codes, tokens and secrets are not logged |
| Inquiries | Company, name, email, message and, where applicable, receipt/consent timestamps and version | The public website opens an email inquiry. The consent-based four-field intake is used only in environments where it is provided |
Actual content varies with customer materials. Customers should limit collection to necessary business information and avoid unnecessary sensitive or unique identification information, using redaction where appropriate. We apply data minimization.
04Google and Microsoft mail connections
| Provider | Permissions | Purpose |
|---|---|---|
| Google Gmail | gmail.readonly, openid, email; offline access | Read mail/attachments, verify the connected account and maintain the authorized connection |
| Microsoft Graph | Mail.Read, offline_access, openid, profile, email | Read mail/attachments, maintain access and verify identity |
Mail connections are read-based. We do not request mail-send, source modification or deletion permissions. Provider permission grants may cover more than the configured folders and dates; internal collection settings do not narrow the underlying OAuth grant.
Connection consent is separate from TradeOps AI login. Before enabling collection or AI, customers confirm the account, folders, period, storage purpose, analysis scope and processing environment. Refusing optional consent limits the affected connection or analysis; other available functions remain subject to the contract. Provider verification, administrator approval and actual collection are separate steps.
05AI processing and Limited Use
AI runs in a self-hosted Docker inference environment managed by the Company or Customer. Processing starts only for adopted models and analysis profiles that are enabled within the customer-authorized scope. Only necessary source text, document information and business context are submitted. Source data is not sent to external AI services.
Extracted values, classifications and matching candidates are not approvals or confirmed facts. A responsible user reviews source evidence and conditions. Results and source references are business records. Temporary inputs and caches are cleaned after processing. Operational error logs must not contain source content, authorization codes, tokens or secrets.
TradeOps AI’s use and transfer to other apps of information received from Google APIs adheres to the Google API Services User Data Policy, including Limited Use requirements, and applicable Google Workspace user-data policies.
These restrictions cover original and derived data. We do not use it for advertising, sale, creditworthiness or lending eligibility, or training/improving generalized AI/ML models or models shared with other customers. Microsoft data is used minimally for explicitly authorized email extraction/classification purposes.
Routine staff or contractor reading of source data is prohibited. Access is limited and recorded for affirmative user consent to specific materials, permitted security investigation or legal duties. Changes to processing, model operation or external processors require prior notice and any required contracts or consent.
06Disclosure and processors
We do not sell personal information or disclose it for advertising, another customer’s use or a third party’s independent purposes. Legally required disclosure or separately lawful processing is limited to necessary scope and applicable notice/consent.
| Processing | Operator and scope |
|---|---|
| Service, support and AI inference | 비엔비에셋 주식회사 processes directly. Source data is not transmitted to an external AI provider. |
| Optional cloud database | Amazon Web Services (AWS) RDS in the Seoul region is used only in customer environments that enable it. Processing, subprocessors, retention/deletion and access conditions are specified before activation. |
| Google/Microsoft | Provide the customer-selected mail service and OAuth connection. Their own account/mail processing follows their policies and customer contracts. |
New processors, support tools or storage are activated only after their purpose, data, location, access, retention, required agreements and notices are established. Outsourcing terms address purpose limits, safeguards, subcontracting supervision and return/deletion.
07International transfers
Company-managed AI is self-hosted and does not transmit data abroad to external AI services. The selected AWS RDS database region is Seoul. This does not mean that Google/Microsoft processing, provider support access or every customer environment uses the same location.
Before activating international storage, backup, support access or a new external processing environment, we individually disclose the recipient/contact, country, information, timing/method, purpose, retention, lawful basis, refusal procedure and affected features, and complete necessary consent, contractual and legal steps. Policy publication or OAuth consent does not substitute for these steps.
Customers may refuse or request cessation through ayden@bnbcompany.io · +82-2-6672-3905 or their administrator. The affected connection or analysis may become unavailable; remaining functions or alternatives are explained within the contract.
08Retention and destruction
Information is destroyed when its purpose ends, its period expires or a lawful deletion request is verified. During an active contract, source versions and evidence/change records remain consistent; immutable ledgers are not arbitrarily deleted in part. Accounts, connections and new collection/analysis are blocked immediately at termination. Contract-end deletion is a controlled operator process that verifies export scope and legally retained records, not an immediate automatic bulk-delete promise.
| Information | Retention and deletion |
|---|---|
| Accounts, contracts, source business data and derived results | While necessary for the active contract. Request export within 30 days after termination. Operational copies and related derived data are cleared within 30 days of contract termination. Unnecessary data is destroyed without undue delay; a limited export opportunity authorized or requested by the Customer lasts no more than 30 days from termination. |
| Audit/business history | Kept as necessary during the contract for evidence, permissions and disputes; subject to the same termination process. Daily historical snapshots necessary for an active contract have a maximum 365-day period; query snapshots remain valid for 15 minutes. These maxima do not justify retaining personal information for terminated accounts. |
| Security/access metadata | An operational minimum of one year, or longer where legally required. Delete after the purpose ends; do not log source content or secrets. |
| Backups | Rotate out within 90 days of contract termination. Restrict ordinary access and reapply deletion requests if restored. |
| OAuth tokens and one-time authentication | Remove usable tokens and stop new collection on disconnection. Clean one-time state/PKCE according to use/expiry; do not restore usable tokens from ordinary backups. |
| Inquiries | Delete public email inquiries within 30 days after the response is complete. Consent-based local four-field intake expires/is cleaned 30 days after receipt. Explain any separate contractual, dispute or legally required retention. |
For legally required or ongoing-dispute retention, explain the items, basis, period and restricted access to the requester and prohibit unrelated use. Delete electronic files in a manner appropriate to preventing recovery/reproduction; securely shred printed materials. Confirm database, object-version, derived-data and backup deletion separately.
09Disconnection and deletion requests
| Action | Effect |
|---|---|
| Disconnect in TradeOps AI | Removes usable app tokens, stops new collection and cancels related queued/running work. It does not delete already stored sources. |
| Revoke Google/Microsoft access | Revoke provider permissions separately from deletion of Company-held copies. |
| Request stored-data deletion | Specify account, organization and scope. We verify authority and distinguish source/derived data, backups and legally retained records. |
| Close an account/terminate | Access termination, export and deletion follow the contract and this policy. Disconnection alone does not end the contract. |
Manage provider permissions through Google connections, Microsoft personal-account consent or Microsoft organizational apps; administrator involvement may be required.
Deleting provider mail may produce synchronization deletion markers; retained source versions and audit history are not thereby physically erased. Request export, deletion or withdrawal through ayden@bnbcompany.io · +82-2-6672-3905. We verify minimum identity/authorization, coordinate with the customer administrator, acknowledge by the next business day and handle applicable statutory deadlines, restrictions and appeal procedures.
10Your rights
Data subjects may exercise applicable rights of access, correction/deletion, processing restriction and consent withdrawal, directly or through lawful representatives. We verify only necessary identity/authority and explain legal restrictions and appeal routes.
We cooperate with customer controllers for requests concerning correspondents or other people in business data; this does not remove our own responsibilities. AI supports human review. If decisions with significant legal effects are fully automated in future, applicable explanation/refusal rights and procedures will be separately disclosed.
Send requests to ayden@bnbcompany.io · +82-2-6672-3905 or the Company postal address. Privacy officer 김복기 (Representative) coordinates with customer administrators, acknowledges by the next business day and provides outcomes or grounds for limitation within applicable legal deadlines. Do not send sensitive source data, passwords or tokens in ordinary email.
12Safeguards
We apply organization, role and assignment-based access controls, session/CSRF checks, OAuth state/PKCE/callback validation, server-side AES-GCM encryption of connection tokens and source version/hash verification. HTTPS transmission, separate key/secret management, minimum access and access records are operational requirements.
Storage encryption and access controls for databases, files and backups are checked and applied per customer environment. We do not claim identical safeguards or completed security certification for every environment. Support access to sources requires specific customer authorization or lawful security/legal need, with limited scope and records.
Suspected incidents are reported to the privacy officer; access restriction, evidence preservation, impact assessment and recovery follow. Notifications to customers, subjects and authorities follow applicable legal requirements and deadlines. Processor supervision and staff training are maintained.
13Privacy officer and contact
| Item | Details |
|---|---|
| Privacy officer | 김복기 (Representative) |
| Company | 비엔비에셋 주식회사 |
| ayden@bnbcompany.io | |
| Telephone | +82-2-6672-3905 |
| Postal address | 서울특별시 서대문구 신촌로 25, 2층 2127호(창천동) |
Use these contacts for rights, disconnection, deletion, export and security inquiries. Official resources for privacy complaints and mediation include KISA Privacy Infringement Reporting and the Personal Information Dispute Mediation Committee.
14Changes to this policy
This initial policy takes effect on October 12, 2026. Ordinary changes are announced seven days in advance; material changes to purpose, information, periods, processors or transfers are announced 30 days in advance through the website or customer administrator contacts. Necessary separate consent or legal procedures cannot be replaced by publication or continued use. Urgent legal/security changes are explained without undue delay.
Previous versions and change details may be requested from the Company, and this page will provide history when changes occur. See the Terms of Service for service arrangements.