What we collect, and what we refuse to.

This policy explains how Digital Socket LLC, a limited liability company formed in Delaware, United States, trading as Transglot ("Transglot", "we", "us") collects, uses, discloses and safeguards personal data when you visit the website or use the localization platform, including the editor, AI translation, the in-context editor, the REST API, the command line interface, webhooks, the delivery bundle and the marketplace connectors (together, the "Service"). It applies to visitors, to people who hold a login, to the members of an Account or a workspace and to anyone who writes to us. The capitalised terms it uses, such as User, Account, Account Owner and Billing Member, have the meanings the Terms of Service give them. It does not apply to a third party site or system you reach through a connector, which has its own policy. Using the Service means this policy applies to you.

We are the controller of the personal data we decide the purposes for: your login, your Account and workspace memberships, billing records, support conversations, marketing contacts and the operational telemetry we need to run and secure the platform. We are a processor of the personal data that happens to sit inside Customer Content, because you decide what strings to send us and why. The Data Processing Addendum governs that second role, is incorporated into the Terms of Service, and applies without anything being signed. Where a right below is one you have against a controller, exercise it against us for the first category and against the person or company that holds the Account for the second.

Login details: name, email address and a hashed password. Account details: the Account’s name, the role you hold on it, and the workspaces and roles you are given. Profile details you choose to add, such as a display name, a locale preference and a notification preference. Billing details when you subscribe: the billing contact, the billing email, the billing address, the billing country and tax identifiers, plus a payment method token held by our payment processor. We never see or store a full card number. Support and sales correspondence: whatever you write to us, plus the address you write from. Program applications: what you submit on the open source application form or the Founding Partner enquiry. Content you post inside a workspace: comments, review notes, assignments and glossary entries, which carry your name inside that workspace. A mobile number, if you choose to confirm one to unlock welcome words. We send it to our text message provider to check that it is a mobile line and to deliver a code, and we keep only a one-way fingerprint of it.

Operational telemetry: IP address, user agent, referring page, the pages and screens you open, the API endpoints you call, request identifiers, timings, queue and run outcomes, quality gate results, error traces and rate limit decisions. Usage accounting: word counts, locale counts, run counts and token counts, which is what meters your allowance. Security records: sign-in attempts and their outcome, second-factor enrolment events, token creation and revocation, role and permission changes, and SSO or SCIM events. Audit events carry the actor, the action, the target, the time and the IP address. Signup integrity signals: when you sign up, sign in (with a password or a social provider), create an Account or create a workspace, we read the network range your request came from and the random token in the tg_device cookie the Cookie Policy describes, and we store a keyed hash of each, never the address or the token itself. The pair is stored on the Account from sign-up until its welcome words are decided, with a keyed hash of the network the Account was created from. When welcome words are given, we record a keyed hash of that network and, for an address at a non-webmail email domain, of that domain, with the time of the grant, so that too many grants from one domain within 30 days or from one network within 24 hours are held for review. Where welcome words were given to an Account from a pair, the pair is also linked to a keyed hash of that Account Owner’s email address, and it is refreshed when an Owner of that Account signs in from it. We use these pairs only to refuse or review a sign-up that repeats one that already received a free allowance. Metering records counts, never the body of a request.

Customer Content is whatever you put into a project: translation keys, source strings, translations, glossaries, style guides, comments, screenshots captured by the in-context editor and the files you import. It may contain personal data, because a product string can. You decide what goes in, and the Acceptable Use Policy asks you not to submit payment card data, government identifiers, credentials or special category personal data as translatable content. We process what is in there on your instructions, under the Data Processing Addendum, and we do not go looking through it except where a report, a legal obligation or a security incident requires it.

If you sign in with a federated identity provider or with single sign-on, that provider sends us the identifiers and attributes needed to create or match your login, typically a subject identifier, an email address and a name. If you connect a repository, storage bucket, content platform or chat workspace, that system sends us the files, entries and identifiers the connector needs, using the access you granted. With optional-tracking permission, a Founding Partner link records a referral token so the partner can receive attribution; refusing does not prevent the link from opening its destination. If you permit optional tracking and arrive from a Google ad, we record the click identifier Google appended to the link, the campaign labels it carried and the page you landed on, and at that moment none of it names anybody; if you go on to sign up, it is attached to your login, which is how a signup is credited to the campaign that won it. Our payment processor sends us the status of a charge, the last four digits of a card and its expiry, a hashed fingerprint of the card, the billing country, and the tax identifiers you give it.

We use essential cookies for sign-in, security and the preferences described in the Cookie Policy. Optional analytics, session recording, affiliate attribution and advertising require a current affirmative choice everywhere, including California, the rest of the United States, the European Economic Area, the United Kingdom and Switzerland. Before acceptance, and on pages loaded with refusal or a Global Privacy Control signal, Google Analytics, Google Ads and Smartlook remain unloaded, so no cookieless measurement pings are sent through those tags. Withdrawal stops new optional events and reloads the page without those tags; it cannot recall data already sent or cancel a request already in flight. On transglot.ai, permission allows analytics, Smartlook session recording and Google advertising personalisation, including remarketing. Smartlook does not record what you type into forms and does not run inside the product. On app.transglot.ai, permission allows analytics and conversion measurement, while advertising personalisation remains disabled. Nothing placed in a project is shared for advertising. The Privacy choices and Do Not Sell or Share My Personal Information links open controls on both hosts without requiring a login. Accept and Reject optional tracking are available together. We remember the choice across our subdomains for 180 days. A Global Privacy Control signal overrides an earlier acceptance. All core features work when optional tracking is refused. The Cookie Policy explains storage, withdrawal and the limits of a browser-specific choice.

Where the GDPR or the UK GDPR applies, we rely on: performance of a contract, to create and run your login and your Account, provide the Service, meter usage, take payment and give support; legitimate interests, to secure the platform, prevent fraud and abuse, including a browser check on sign-up and workspace forms and a one-time phone check before the second part of the welcome words, or before all of them for an address at an email relay or forwarding service, to stop the same person collecting a second free allowance, trial or launch price, using the signup integrity signals, card fingerprints and identity records described in clauses 04, 06 and 15, debug and improve the Service, keep records of what happened, measure aggregate demand and send service-related messages, balanced against your interests each time; legal obligation, to keep tax and accounting records, answer lawful requests and meet regulatory duties; and consent for optional analytics, session recording and advertising in every region, and for optional marketing email where we request it, and which you can withdraw at any time without affecting what came before. Where we act as processor, the legal basis is the one the holder of the Account relies on.

We do not ask for special category personal data (health, genetic, biometric identification, racial or ethnic origin, political opinions, religious beliefs, trade union membership, sex life or sexual orientation) and the Service is not designed to hold it. We do not knowingly collect it about you as a controller. If you place it inside Customer Content you do so as controller, on your own legal basis, and you should tell us first so we can tell you honestly whether the platform is appropriate for it. Under California law we do not collect sensitive personal information for the purpose of inferring characteristics about anyone.

A translation run sends source strings and their surrounding context, in structured batches, to the AI subprocessors disclosed by category and region in our Trust Center and in the Subprocessors document, and named in the list we furnish on request under a non-disclosure agreement. That list is the authoritative record of who can process your content and in which region, and it is enforced rather than aspirational: an automated test fails our build if a translation engine becomes reachable without a disclosure row, so we cannot route your text to a vendor we have not told you about. An exact-match translation memory hit is resolved inside our own systems and is never sent to a subprocessor. A near-match hit is different, because finding one means embedding the source string first: that lookup sends the string to the embeddings subprocessor, and it runs only on a project that has turned semantic translation memory on, which is off by default. We do not use your content to train models, on any plan, and our AI subprocessors are called for inference only under commercial terms.

सेवा स्वयमेव संचालिता अस्ति: सा अनुवादं करोति, गुणवत्तायाः मूल्याङ्कनं करोति, शब्दकोशस्य तथा स्थानधारक-नियमान् प्रयुङ्क्ते, च यदि पङ्क्तिः तेषाम् उल्लङ्घनं करोति तर्हि सा तस्याः निराकरणं कर्तुं शक्नोति। एते निर्णयाः पाठखण्डस्य विषये भवन्ति न तु व्यक्तिस्य विषये, तथा च एतेषां कस्यचित् अपि व्यक्तिगतं वा कानूनीयं वा महत्त्वपूर्णं परिणामः न भवति। वयं युष्मद्विषये निर्णयार्थं प्रोफाइलिङ्ग् इत्यस्य उपयोगं न कुर्वन्ति, तथा च वयं युष्माकं ऋण-मूल्याङ्कनं न कुर्वन्ति। स्वचालितपरीक्षाभिः पञ्जीकरणं बाधितुं शक्यम्: क्षणिक-ईमेल-सेवासु स्थितं पत्रावलोकनं निरस्तं भवति, ब्राउज़र-परीक्षा पृच्छति यत् किं कश्चित् व्यक्तिः रूपं पूरयति, तथा च यस्याः संजालिकायाः तथा ब्राउज़रस्य उपयोगेन पूर्वमेव स्वागतसन्देशाः प्राप्तवत्याः खातायाः समानसंजालिकातः पञ्जीकरणं निरस्तं भवति वा पुनरावलोकनाय रक्षितं भवति। स्वागतसन्देशाः, परीक्षणकालाः तथा प्रारम्भिकमूल्यानि अपि स्वयमेव दीयन्ते, एकदा प्रतिखातं तथा एकदा प्रतिव्यक्ति, ईमेल-पत्रावलोकनं, दूरभाषसङ्ख्या तथा कार्डम्। यदि एतासु परीक्षासु काचिद् युष्मान् अवारितवती अस्ति तथा च युष्मते तत् त्रुटिपूर्णम् इति भासते, तर्हि अस्मान् लिखतु तथा च कश्चित् व्यक्तिः तस्य पुनरावलोकनं करिष्यति। दुर्व्यवहारस्य तथा वञ्चनायाः सूचनाः निलम्बनं जनयितुं शक्नुवन्ति, तथा च स्वीकार्योपयोगनीतिः मानवीयं अपीलं प्रदाति।

Other members of the workspaces you belong to, according to their role and their project access, which is why a comment you write carries your name inside that workspace, and the Account Owners, who have access to every workspace on the Account. The service providers that run the platform on our behalf, under written terms and confidentiality obligations, in the categories set out in the Subprocessors document: AI translation, cloud hosting and database, object storage, email delivery, payment processing and support messaging. With your permission, Smartlook records how pages on this website are used, as described in clause 07, on our behalf and with storage in the European Union; it never sees the product. Two providers act on the security of sign-up and logins rather than on your content, so they are named here: Cloudflare runs the browser check (Turnstile) on sign-up and workspace forms and receives your IP address, browser signals and the page’s site key, under its Turnstile privacy addendum; Twilio receives the mobile number you confirm, to check its line type and send the code. The tools our team uses for internal communication. The endpoints you yourself register: webhooks, connectors and storage destinations receive exactly the events and content you subscribe them to, and once delivered that data is in your hands. Professional advisers under duties of confidence. Anyone a valid legal obligation requires, where we will narrow the request and tell you unless we are legally barred from doing so. A successor, if the business is acquired or reorganised, subject to this policy continuing to apply. When optional tracking is permitted, Google receives the website measurement and the conversion measurement described in clause 07 as an independent controller for its own advertising products, rather than as a provider acting on our instructions: which pages you opened, which ad brought you here, and, when you sign up or pay, a SHA-256 hash of your email address and, where a billing address gives us them, of your first and last name, alongside the postal code and the two letter country in the clear because Google will not accept those hashed. A SHA-256 hash is a one way digest that Google can match against its own records; it is pseudonymous personal information, not anonymous data. Enhanced conversions are sent only when configured and permission is current; the unhashed email address is not sent with them. We do not sell personal data for money. The disclosure to Google is sharing for cross-context behavioural advertising under United States state law, and clause 24 sets out what you can do about it. Nothing you place in a project is part of any of this.

वर्तमान उप-प्रक्रियाकार प्रकटीकरण, उद्देश्येन, क्षेत्रेण च सह यत् अन्तर्गतं प्रत्येकं वर्गः नियुक्तः भवति, तत् विश्वासकेन्द्रे प्रकाशितं भवति तथा उप-प्रक्रियाकारदस्तावेजे सङ्क्षिप्तं क्रियते; तेषां वर्गाणां पश्चात् स्थिताः नामितविक्रेतारः गोपनीयतासमझौते अधीनं अनुरोधेन प्राप्यन्ते, यदा privacy@transglot.ai इति पत्रिकायां लिखितम्। नूतन उप-प्रक्रियाकारः ग्राहकस्य वैयक्तिकदत्तांशान् संसाधयितुं आरभते इति पूर्वमेव वयं ईमेलद्वारा सूचनां ददामः, तथा दत्तांशसंसाधनअनुबन्धः युष्माकं युक्तियुक्तदत्तांशरक्षणहेतुना विरोधस्य अधिकारं प्रददाति। केचन प्रविष्टयः सदैव सक्रियाः न भवन्ति अपि तु सापेक्षाः भवन्ति: केचन केवलं वेतनयोजनेषु नियुक्ताः भवन्ति, तथा केचन केवलं यदा परियोजना वैकल्पिकलक्षणं सक्रियं करोति तदा नियुक्ताः भवन्ति।

वयं मञ्चं एकस्मिन्य् एव मेघक्षेत्रे चालयामः, यत् वितरणसमये निर्धारितं भवति, तथा वयं केचन उप-प्रक्रियाकाराः संयुक्तराज्ये तथा एकस्मिन् वैकल्पिकभाषान्तरयन्त्रे सिङ्गापुरे दत्तांशान् संसाधयन्ति। अद्य प्रतिपरियोजनाक्षेत्रनिर्धारणं नास्ति तथा वयं तत् न विक्रीणामः। यदा वैयक्तिकदत्तांशाः संयुक्तराज्यम्, यूरोपीयआर्थिकक्षेत्रं वा स्विट्जरल्याण्डं त्यजन्ति, तदा वयं लागूप्राप्ते कानूने मान्यताप्राप्त सुरक्षाव्यवस्थासु निर्भराः भवामः, मुख्यतया यूरोपीयआयोगस्य मानकसंविदाखण्डेषु ब्रिटिशअन्तर्राष्ट्रीयदत्तांशस्थानान्तरणअनुबन्धेन सह यत्र ब्रिटिश GDPR लागू भवति तथा स्विसअनुकूलनेन सह यत्र स्विसकानूनः लागू भवति, दत्तांशसंसाधनअनुबन्धे वर्णितानाम् पूरकउपायानां सह। किसीचित् उप-प्रक्रियाकाराय अवलम्बितस्य स्थानान्तरणयन्त्रस्य प्रतिः अनुरोधेन उपलभ्या। खण्डे ०७ स्थिता विश्लेषणविज्ञापनदत्तांशाः संयुक्तराज्ये गूगल् प्राप्नुवन्ति, यत्र गूगल् तस्य स्वतन्त्रनियन्त्रकः भवति तथा अस्माकं स्थाने स्वकीयस्थानान्तरणसुरक्षाव्यवस्थासु निर्भरः भवति।

Login, Account and workspace records: for as long as each exists, then as clause 16 describes. Billing and tax records: as long as tax and accounting law requires, and a closed Account keeps its invoices for 7 years after it closes. Support correspondence: while it is useful and then on our ordinary correspondence schedule. Project content: for as long as the project exists. Translation version history: 180 days, with a floor of the newest 20 versions per string, which survives any age, on every plan rather than as a paid tier. Notifications: 90 days. Comments: kept while a thread is unresolved, and 365 days after a thread is resolved. Activity feed: 180 days. Assistant conversations: 90 days, and deleted with the login that made them. In-context screenshots: 90 days. Connector sync run records: 90 days, keeping the most recent run per connection. Delivery bundle: the most recent 20 published versions per project and locale. Referral click records: 90 days. Ad click attribution: one row a person, holding the Google click identifier, the campaign labels it carried and the page it landed on, kept while the login exists unless optional tracking is withdrawn, when the attribution record is removed, and deleted with the login. The conversion ledger, which records what we reported to Google, when, and the hashed identifiers sent with it: kept as the record of a report we made, and detached from your login when the login is deleted. Withdrawal prevents future reports and removes identifiers from unsent conversions; it does not recall a report already sent to Google. A signed-in login’s optional-tracking choice and the time it was recorded are kept to enforce that choice, including before a queued conversion is uploaded. Unreviewed translation memory entries that were never reused: 90 days. Audit events: append-only and kept until the workspace is purged; on an Account’s own audit trail the IP address is removed after 395 days. Webhook delivery records: kept for the life of the endpoint, with no time-based prune today, so delete an endpoint to clear its history. Failed background jobs: 7 days. Expired API tokens: swept 24 hours after they lapse. Operational metrics: 30 days. Signup integrity signals: the pair and the network hash stored on an Account are removed when its welcome words are decided, and otherwise 90 days after the Account was created; a pair from which welcome words were given is kept until 90 days after it was last seen. Sign-up refusal records: 90 days. Welcome words velocity records, a keyed hash of a non-webmail email domain or of a network with the time of a grant: 30 days for a domain and 24 hours for a network. Sign-up allowlist entries, which an operator writes to let one email address or one network and browser pair past the sign-up checks: until the expiry the operator sets, never more than 365 days. An Account that was never verified and has no workspace and no payment history is deleted 30 days after it was created, unless a sign-up review of it is pending; the fingerprints described below are kept. While a sign-up review of an Account is pending, its signals and its refusal record are kept past those periods until the review is decided or the Account is deleted. Welcome words and trial records: a one-way fingerprint of each email address, login and phone number that received welcome words or a trial, kept 1,095 days from the grant, so that they are given once; a phone number’s fingerprint, and the fingerprints carried over from the welcome words records kept before Accounts existed, are kept for as long as the Service runs. The trial ledger, which holds a hashed fingerprint of the card each trial started with: 1,095 days. A card fingerprint flagged for a dispute or an unpaid invoice: 1,095 days. Backups: encrypted backups keep these identifiers for up to 3 weeks after they leave the live database. After any restore from a backup, the deletions carried out since the restored moment are applied again, login and identity deletions before the Service restarts and scheduled deletions by their next daily run, and a deletion request not yet carried out is repeated by support.

They are three different actions with different clocks, and the difference matters. Deleting your login is immediate and irreversible: your sign-in methods, notifications, saved views, assignments, assistant conversations and the record of which ad click brought you are hard deleted at once, and there is no recovery window. What you contributed inside a workspace stays with that workspace, including the comments you wrote and the record of what you did, and those can still show your name, because deleting one member must not rewrite another workspace’s history. Closing an Account cancels its subscription at once, bills any usage beyond the plan on a final invoice, and deletes every workspace on it after 30 days; the Account’s invoices are kept as clause 15 describes. Deleting a workspace makes it read only for 30 days, during which an Account Owner can cancel; after that it is purged, and projects, translations, versions, usage history, webhook deliveries, screenshots and audit events cascade out of the live database. Deleting a workspace cancels nothing, because the plan belongs to the Account. Those purges do not reach the encrypted backups behind them, which roll off on their own schedules described in clause 17. When a login received welcome words or a trial, its fingerprints are not deleted with it: they cannot be turned back into an address, a number or a card, and without them the allowance could be collected again, so they are kept for the periods in clause 15.

परिसरे (edge) TLS 1.2 वा ततो उत्तरेण परिवहनसुरक्षा। bcrypt द्वारा लागत-गुणक १२ इत्यनेन पासवर्ड्स् हैश् (hashed) कृताः। वैकल्पिकं द्वि-कारकं प्रमाणीकरणं समय-आधारितकोडैः तथा च पुनःप्राप्ति-कोडैः सह, अपि च पासकीस् (passkeys), सर्वयोजनासु निःशुल्कयोजनायां अपि उपलब्धम्, तथा च सम्पूर्णकार्यक्षेत्राय आवश्यकं यत् खातस्वामी (Account Owner) सक्रियं कर्तुं शक्नोति। API टोकन्स् तथा च वितरणकुञ्जाः SHA-256 डाइजेस्ट्स् रूपे रक्षिताः तथा च निर्माणसमये एकवारं प्रदर्शिताः। तृतीयपक्षस्य प्रमाणपत्राणि तथा च वेबहुक-गुप्तानि गुप्तस्तम्भेषु रक्षिताः। बहिर्गच्छन्तः वेबहुक्स् समयचिह्नस्य तथा च शरीरस्य उपरि HMAC-SHA256 इत्यनेन हस्ताक्षरिताः। प्रत्येकयोजनायां कार्यक्षेत्र-तथा च प्रकल्प-स्तरे भूमिका-आधारितं प्रवेशनियन्त्रणं, भाषा-प्रति अनुमतिसहितम्। प्रत्येकप्रश्ने टेनन्ट् स्कोपिङ्ग्, यत्र क्रॉस्-टेनन्ट् पहचानकर्ता ४०३ इत्यस्य स्थाने ४०४ इति उत्तरं ददाति येन अस्तित्वं कदापि न लीयते। सार्वजनिकबिन्दुषु दरसीमाः। केवलं योज्यलेखापरीक्षा-अभिलेखाः। गुप्ताः डाटाबेस् बैकअप्स् (द्वे पूर्णे बैकअप्स् तथा च निरन्तरराइट-अहेड्लॉग् आर्काइविङ्ग् सह भेदात्मकाः इति रूपे रक्षिताः) तथा च गुप्तानि फाइल् बैकअप्स् (३० दैनिकानि, १२ साप्ताहिकानि तथा च १२ मासिकानि स्नैपशॉट्स् इति रूपे रक्षिताः)। अहं किं न दावयामि: सक्रियाः वॉल्यूम्स् डिस्क-गुप्ताः न सन्ति, लेखापरीक्षा-लॉग् उपरि क्रिप्टोग्राफिक् हाश् चेन् नास्ति, तथा च अद्य अहं कोऽपि तृतीयपक्षस्य सुरक्षाप्रमाणपत्रं न धारयामि। सुरक्षापृष्ठे एते अवकाशाः समानशब्दैः उल्लिखिताः सन्ति।

अहं घटनाप्रतिक्रियाप्रक्रियां निर्वहामि। यदि व्यक्तिगतडाटाभङ्गः भवतः पक्षे अहं प्रक्रमितडेटां प्रभावितं करोति, तदा तस्य ज्ञानोत्तरं अनुचितविलम्बं विना अहं खातस्वामिनः (Account Owners) सूचयामि, डाटाप्रक्रमणपरिशिष्टेन (Data Processing Addendum) आवश्यकितसूचनासहितं, तथा च भवतः स्वसूचनाकर्तव्येषु अहं साहाय्यं करिष्यामि। यदि भङ्गः नियन्त्रकरूपेण अहं धृतडेटां प्रभावितं करोति तथा च भवतः प्रति उच्चजोखिमस्य सम्भावना अस्ति, तदा अहं भवतः साक्षात् सूचयामि तथा च कानूनेन अनुमतकाले प्रासङ्गिकं पर्यवेक्षकप्राधिकारिणं सूचयामि। अहं भवतः तस्य विषये किं वक्तुं शक्यते इत्यस्य किमपि प्रतिबन्धस्य सहमतिं सूचनायाः पूर्वशर्तं न करिष्यामि।

भवतः निवासस्थानानुसारं, भवतः अधिकारः भवितुं शक्नोति: अहं कानि व्यक्तिगतडाटा धारयामि इति ज्ञातुं तथा च तस्य प्रतिलिपिं प्राप्नुम्; अशुद्धं वा अपूर्णं डाटां शुद्धं कर्तुम्; तत् विलोपयितुम्; प्रक्रमणं प्रतिबन्धयितुं वा विरोधयितुम्, प्रोफाइलिङ्ग् तथा च प्रत्यक्षविपणनं समाविश्य; तत् पोर्टेबल्, मशीन-पठनीयरूपे प्राप्नुम् तथा च तकनीकरूपेण सम्भवति चेत् अन्यनियन्त्रके प्रति प्रेषयितुम्; पूर्वप्रभावमविनाश्य कदापि सहमतिं वापस गृहीतुम्; तथा च केवलं स्वचालितप्रक्रमणाधारितनिर्णयेन न बाध्यितुं यः कानूनिकं वा तत्सदृशं महत्त्वपूर्णं प्रभावं जनयति। अधिकांशं प्रवेशसूचना भवतः सेटिङ्ग्स्मध्ये सम्पादनीयम् अस्ति, खातस्वामिनः खातं, तस्य सदस्यान् तथा च तस्य कार्यक्षेत्राणि व्यवस्थापयितुं शक्नुवन्ति, तथा च कार्यक्षेत्रप्रशासकाः सदस्यान्, भूमिकाः तथा च टोकन्स् व्यवस्थापयितुं शक्नुवन्ति; केवलं खातस्वामिनः कार्यक्षेत्रं विलोपयितुं शक्नुवन्ति। अधिकारस्य प्रयोगार्थं अहं भवतः प्रति भेदभावं न करिष्यामि।

Write to privacy@transglot.ai and say what you want. An opt-out through Privacy choices, Do Not Sell or Share My Personal Information, or Global Privacy Control does not require a login, proof of identity or acceptance of terms. For requests that require verification, such as access to or deletion of personal records, we will verify that the request comes from you or from someone you have authorised, using the email address of your login where we can and asking for reasonable additional information where we cannot; we ask for the minimum needed and we do not create a new identity record to answer a request. We respond within one month where the GDPR or UK GDPR applies, extendable by two further months for a complex request with an explanation, and within 45 days where United States state privacy law applies, extendable once by a further 45 days. There is no charge unless a request is manifestly unfounded or excessive. Where the personal data sits inside another customer's project content we are the processor, so we will pass the request to that customer's Account Owners and support them in answering it rather than answering it ourselves.

If you are unhappy with how we have handled your personal data, tell us first and we will try to put it right. You also have the right to complain to a supervisory authority: in the European Economic Area, the authority in the country where you live, work or where the issue arose; in the United Kingdom, the Information Commissioner’s Office; in Switzerland, the Federal Data Protection and Information Commissioner. Nothing in this policy takes away that right or requires you to come to us first.

यत्र अहं यूरोपीयआर्थिकक्षेत्राय अनुच्छेद २७ प्रतिनिधिं नियुक्तुं बाध्यः अस्मि, तत् our EU Article 27 representative, whose details are published here once appointed and are available on request in the meantime अस्ति, तथा च संयुक्तराज्याय (UK) हमारे यूके के अनुच्छेद २७ प्रतिनिधि, समान आधार पर अस्ति। डाटारक्षणअधिकारिविषये, we have not appointed a Data Protection Officer, because we are not required to. Privacy questions are handled by the team behind the address below। भवान् सदैव अस्य दस्तावेजस्य पादे स्थितपतेन गोपनीयताविषये व्यक्तिं सम्पर्कयितुं शक्नोति।

अयं खण्डः संशोधितकैलिफोर्नियाउपभोक्तृगोपनीयताअधिनियमानुसारम् आवश्यकः सङ्ग्रहसमये सूचनात्मकः अस्ति। अन्तिमद्वादशमासेषु वयम् एतेषां व्यक्तिगतसूचनानाम् वर्गाणां सङ्ग्रहं कृतवन्तः स्मः: पहचानकर्तारः (नाम, ईमेलपत्रस्य पता, दूरभाषसङ्ख्या, प्रवेश- तथा खाता-पहचानकर्तारः, आईपीपता, भवतः ईमेलपत्रस्य पतस्य तथा दूरभाषसङ्ख्यायाः एकदिशाङ्गुलिमुद्राः, नेटवर्कपरिसरस्य च ब्राउज़रटोकनस्य यत् साइन-अप आगतम् तस्य कीलितह्याशेषाः, तथा भुगतानकार्डस्य ह्याशितम् अङ्गुलिमुद्रा); ग्राहकलेखाः (बिलिङ्गसम्पर्कः, बिलिङ्गईमेल, बिलिङ्गपता, बिलिङ्गदेशः तथा करपहचानकर्तारः); वाणिज्यिकसूचना (योजना, सदस्यता तथा भुगतानइतिहासः); अन्तर्जालस्य वा नेटवर्कस्य क्रिया (उपयुक्ताः पृष्ठाः तथा अन्त्यबिन्दुः, अनुरोधलॉग्स्, उपकरणस्य तथा ब्राउज़रस्य सूचना); भौगोलिकस्थानः यः केवलं स्थूलस्तरे अनुमितः यत् आईपीपतः ददाति; व्यावसायिकसूचना यत्र भवान् स्वस्य भूमिकां वा कम्पनीं वदति; तथा सामग्री यां भवान् प्रकल्पे निक्षिपति, यस्यां भवान् यं कञ्चित् वर्गं निधातुं इच्छति तत् सर्वं भवेत्। वयम् तत् खण्डे ०८ उल्लिखितानाम् व्यापारिक- तथा वाणिज्यिक-प्रयोजनार्थं सङ्गृह्णीमः, खण्डे १५ उल्लिखितकालावधिपर्यन्तं रक्षामः, तथा खण्डे १२ उल्लिखितप्राप्तिकर्तृवर्गाणां समीपे प्रकटीकुर्मः। तेषु वर्गेषु द्वे अपि क्रॉस्-कांटेक्स्ट व्यवहारजनकविज्ञापनार्थं साझ्यन्ते, यथा खण्डः २४ निर्दिशति: पहचानकर्तारः, अर्थात् परिवर्तनेन सह प्रेषितं ह्याशितमीमेलपत्रस्य पतं तथा गूगल् टैग् येन उपयुक्तं क्लिकं तथा कुकीपहचानकर्तारः, तथा अन्तर्जालस्य वा नेटवर्कस्य क्रिया, अर्थात् भवान् ये पृष्ठानि उद्घाटितवान् तथा यस्मिन् विज्ञापने आगतवान्। वयम् लक्षणानाम् अनुमानार्थं संवेदनशीलां व्यक्तिगतसूचनां न सङ्गृह्णीमः, तथा तस्याः कोऽपि उपयोगं न कुर्मः यः सीमितकरणाधिकारं जनयेत्।

वयं धनार्थं व्यक्तिगतसूचनां न विक्रीणामः। अनुमतिसहितं, वयम् खण्डेषु ०७, १२ तथा २३ वर्णितान् पहचानकर्तारः तथा ब्राउज़िंगक्रियां विज्ञापनार्थं, अस्मिन् जालस्थले क्रॉस्-कांटेक्स्ट व्यवहारजनकविज्ञापनं समाविश्य, गूगल् समीपे प्रकटीकुर्मः। यद्यपि दत्तांशार्थं किञ्चित् धनं न दीयते, तथापि कैलिफोर्नियाकानूने अयं साझ्यः अस्ति। एतादृशं साझ्यं सितम्बर ८, २०२६ तः आरब्धम्। अक्टोबर २१, २०२६ तः, वैकल्पिकट्रैकिङ्गार्थं प्रत्येकक्षेत्रे स्पष्टानुमतिः आवश्यकः; पूर्वम् यूरोपबाह्ये डिफ़ॉल्ट् अब न लागू भवति। उत्पादं स्वीकारानन्तरम् अपि विज्ञापनवैयक्तिकरणं निष्क्रियं रखति, तथा प्रकल्पसामग्री कदापि विज्ञापनार्थं न साझ्यते। तत्क्षणमेव बाहरागमनार्थं 'Do Not Sell or Share My Personal Information' वा 'Privacy choices' चयनं कुरुत तथा 'Reject optional tracking' चयनं कुरुत। वैश्विकगोपनीयतानियन्त्रणसङ्केतः अपि भवन्तं बाहरागमयति तथा पूर्वस्वीकारात् प्राथम्यं लभते। प्रवेशस्य वा पहचानसत्यापनस्य आवश्यकता नास्ति। ब्राउज़रचयनं उभयोः होस्टयोः 180 दिवसान् यावत् तिष्ठति। प्रवेशिते सति प्राप्तः अस्वीकारः अपि नवीनस्पष्टचयनं कृतं यावत् तस्य प्रवेशस्य कृते भविष्यसर्वर-पार्श्वविज्ञापनपरिवर्तनान् रोधयति। भवान् privacy@transglot.ai सम्पर्कं कर्तुं शक्नोति। वयं १६ वर्षाधः कस्यापि व्यक्तिगतसूचनां जानन्तो विक्रीणामः वा साझ्यन्ते वा न।

California residents may request to know the categories and specific pieces of personal information we collected, the sources, the business purpose and the categories of recipients; to delete personal information, subject to applicable exceptions; to correct inaccurate personal information; and to opt out of sale or sharing. We do not sell personal information for money, but permission-based advertising sharing occurs as described in clause 24. Optional tracking is off until you affirmatively accept. Use Do Not Sell or Share My Personal Information, Privacy choices, or Global Privacy Control to refuse or withdraw permission without a login or identity verification. For other rights requests, write to privacy@transglot.ai; we verify identity only to the extent required for that type of request. We will not discriminate against you for exercising a right: no price difference, no service difference and no denial of service. An authorised agent may act for you with the authority required by applicable law; for requests that require identity verification, we may ask you to verify directly.

समग्रगोपनीयताकानूनयुक्तानां राज्यानां वासिनः पुष्टिकरणस्य, प्रवेशस्य, शुद्धिकरणस्य, विलोपनस्य, स्वस्य व्यक्तिगतसूचनायाः प्रतिरूपं प्राप्तुं, तथा लक्षितविज्ञापनस्य, विक्रयस्य तथा केचन प्रोफाइलिङ्गस्य बाहरागमनस्य अधिकाराः भवेयुः। अस्मिन् जालस्थले वैकल्पिकं विज्ञापनं खण्डेषु ०७ तथा २४ वर्णितम् अस्ति। तत् प्रत्येकक्षेत्रे स्पष्टानुमतिं अपेक्षते तथा 'Privacy choices', 'Do Not Sell or Share My Personal Information', वा 'Global Privacy Control' माध्यमेन अस्वीकर्तुं शक्यते। वयं धनार्थं व्यक्तिगतसूचनां न विक्रीणामः वा कानूनीं वा तद्वत् महत्त्वपूर्णं प्रभावं जनयन्तं प्रोफाइलिङ्गं न कुर्मः। अन्यलागूअधिकाराणां प्रयोगार्थं वा निर्णयस्य अपीलार्थं privacy@transglot.ai लेख्यताम्। वयं भवतः राज्येन अनुमतकालावध्या उत्तरं ददामः, तथा यदि अपील अस्वीक्रियते, तर्हि भवतः महाधिवक्ता सम्पर्कयितुं कथं इति व्याख्यामः।

वयं transglot.ai तथा app.transglot.ai उभयोः वैश्विकगोपनीयतानियन्त्रणं सम्मानयामः। Sec-GPC: 1 अनुरोधहेडरः वा ब्राउज़रस्य globalPrivacyControl सेटिङ्ग् true इति वैकल्पिकविश्लेषणस्य, सत्ररेकर्डिङ्गस्य तथा विज्ञापनस्य अस्वीकारः इति सर्वत्र गृह्यते। तत् पूर्वस्वीकारं अधिलिखति। तस्य सङ्केतस्य सह पृष्ठलोडे, वैकल्पिकाः तृतीय-पक्षट्रैकिङ्गस्क्रिप्ट्स् अनलोडेड् तिष्ठन्ति। यदि पृष्ठं खुल्ले सति सङ्केतः परिवर्तते, वयं नवान् वैकल्पिकघटनाः निरोधयामः तथा तेषां स्क्रिप्ट्स् बिना पुनर्लोड् कुर्मः। वयं नवान् विज्ञापनआत्रिब्यूशनं तथा परिवर्तनरिपोर्ट्स् निरोधयामः, तथा उभयोः होस्टयोः 180 दिवसान् यावत् अस्वीकारं स्मरामः। भवान् प्रवेशिते सति, अस्वीकारः भवतः प्रवेशस्य कृते अपि रेकर्ड् भवति येन पश्चात् सर्वर-पार्श्वविज्ञापनपरिवर्तनान् रोधयति। केवलं ब्राउज़रचयनं अन्यब्राउज़रं वा अनामिकआगमनं न पहचानयितुं शक्नोति, अतः तत्र वैश्विकगोपनीयतानियन्त्रणं सक्षमं कुरुत वा तत्र अपि ट्रैकिङ्गं अस्वीकुरुत। पुरातनः Do Not Track सङ्केतः अनुमतिः वा वैश्विकगोपनीयतानियन्त्रणं इति न व्याख्यायते। अस्वीकारानन्तरम् अपि सर्वाणि मुख्यलक्षणानि उपलब्धानि तिष्ठन्ति।

सेवा एकः व्यापारिकसाधनम् अस्ति, बालकेषु लक्षिता न अस्ति, तथा १६ वर्षाधः कस्यापि कृते उद्दिष्टा न अस्ति। वयं जानन्तो बालकात् व्यक्तिगतदत्तांशं न सङ्गृह्णीमः। यदि भवान् मन्यते यत् बालकः वयं व्यक्तिगतदत्तांशं दत्तवान्, तर्हि अधोलिखितपते लेख्यताम् तथा वयं तत् विलोपयिष्यामः। यदि भवतः स्वस्य उत्पादं बालकेषु लक्षितम् अस्ति तथा भवान् तस्य स्ट्रिङ्ग्स् अस्माभिः स्थानीयकरणं कारयति, तर्हि भवान् प्रकल्पे निक्षिप्तस्य कस्यापि वस्तुस्य नियन्ता अस्ति तथा तत् आवश्यकानुमतीनां कृते उत्तरदायी अस्ति।

सेवासन्देशाः उत्पादस्य भागः सन्ति तथा मार्केटिङ्ग् न सन्ति: आमन्त्रणानि, चलनं तथा पुनरावलोकनसूचनाः, कोटा तथा बिलिङ्गसूचनाः, सुरक्षाचेतनाः, घटनासूचनाः तथा एतेषां दस्तावेजानां परिवर्तनानि। भवान् स्वस्य सूचनासेटिङ्ग्स् मध्ये तेषु बहून् ट्यून कर्तुं शक्नोति, तथा भवान् सुरक्षास्य तथा बिलिङ्गस्य सन्देशान् निष्क्रियं कर्तुं न शक्नोति यावत् भवान् प्रवेशं धारयति, यतः ते एव सन्ति येन भवतः अधिकतम आवश्यकता अस्ति। मार्केटिङ्गईमेल पृथक् अस्ति, यत् केवलं तत्र प्रेष्यते यत्र तत् प्रेषयितुं वयं कानूनीआधारं धारयामः, तथा प्रत्येकस्मिन् एक-क्लिक् अनसब्सक्राइब् अस्ति यत् वयं त्वरितं सम्मानयामः।

वयं समय-समये एतां नीतिं अद्यतनं कुर्मः। यदा वयं तत् कुर्मः तदा वयं उपरि प्रभावीतिथिं परिवर्तयामः, तथा यत् परिवर्तनं भवतः अधिकारान् महत्त्वपूर्णेन प्रभावितं करोति तस्य कृते प्रभावनपूर्वं ईमेलद्वारा वा कन्सोल् मध्ये अतिरिक्तसूचनां ददामः। वयं अधिलिखितं संस्करणं याचनायां उपलब्धं रखामः येन भवान् दृष्टुं शक्नोति यत् किं परिवर्तितम्। परिवर्तनप्रभावानन्तरं सेवायाः उपयोगं जारी रखणं अर्थः यत् अद्यतनीकृता नीति भवन्तं प्रति लागू भवति।

Privacy questions, data subject requests and anything about this policy go to privacy@transglot.ai. Vulnerability reports go to security@transglot.ai. Anything else, including contract and billing questions, goes to hello@transglot.ai. A postal address for formal correspondence is on your invoice and is available on request.