प्रोसेसर शर्तें, परिशिष्ट शामिल हैं।

इदं दत्त-प्रक्रिया अनुबन्धपत्रम् ("DPA") सेवा-नियमावलीनाम् अथवा अन्यस्य लिखित-अनुबन्धस्य ("अनुबन्धः") भागः भवति, यः Digital Socket LLC, a limited liability company formed in Delaware, United States, trading as Transglot ("Transglot", "प्रक्रियाकर्ता") तथा ग्राहकस्य ("ग्राहकः", "नियन्त्रकः") मध्ये भवति, च यत्रापि वयं ग्राहकस्य नाम्ना ग्राहक-वैयक्तिक-दत्तानां प्रक्रियां कुर्वः तत्रायम् अनुबन्धः लागू भवति। एतत् अनुबन्धे सन्दर्भेण समाविष्टं भवति च अनुबन्धस्य प्रभावे आगते एव प्रभावशाली भवति; एतद् बन्धनकारकं भवितुं हस्ताक्षरस्यापेक्षा नास्ति। यत्र ग्राहकः स्वयं तृतीय-पक्ष-नियन्त्रकस्य कृते प्रक्रियाकर्ता भवति, तत्र ग्राहकः निर्यातकः भवति च इदं DPA एवं लागू भवति यथा सः नियन्त्रकः आसीत्, च ग्राहकः पुष्टिं करोति यत् तेन स्वस्य नियन्त्रकात् तेषां शर्तानाम् उपरि एतत् प्रविष्टुं अधिकारः प्राप्तः अस्ति।

"दत्त-संरक्षण-विधिः" इत्युक्ते पक्षे लागू भवन्ती वैयक्तिक-दत्त-प्रक्रिया सम्बन्धिनी सर्वे विधयः, येषु यूरोपीय-सङ्घस्य सामान्य-दत्त-संरक्षण-विनियमः २०१६/६७९ ("GDPR"), युके GDPR च दत्त-संरक्षण-अधिनियमः २०१८, स्विट्जरल्याण्डस्य संघीय-दत्त-संरक्षण-अधिनियमः, क्यालिफोर्निया-उपभोक्ता-गोपनीयता-अधिनियमः यथा संशोधितः ("CCPA") च तुलनीयाः संयुक्त-राज्य-राज्य-गोपनीयता-विधयः सम्मिलिताः सन्ति। "ग्राहक-वैयक्तिक-दत्तम्" इत्युक्ते ग्राहक-सामग्रीमध्ये निहितं वैयक्तिक-दत्तम् अथवा अन्यथा वयं ग्राहकस्य नाम्ना यत् प्रक्रियामहे तत्। "मानक-अनुबन्ध-खण्डाः" अथवा "SCCs" इत्युक्ते आयोगस्य कार्यान्वयन-निर्णयस्य (EU) २०२१/९१४ परिशिष्टे उल्लिखिताः खण्डाः। "UK अनुबन्धपत्रम्" इत्युक्ते दत्त-संरक्षण-अधिनियमस्य २०१८ धारा ११९A अन्तर्गतं UK सूचना-आयुक्तेन निर्गतं अन्तर्राष्ट्रीय-दत्त-स्थानान्तरण-अनुबन्धपत्रम्। "उप-प्रक्रियाकर्ता" इत्युक्ते तृतीय-पक्षः यं वयं ग्राहक-वैयक्तिक-दत्तस्य प्रक्रियायाः कृते नियोजयामः। "नियन्त्रकः", "प्रक्रियाकर्ता", "दत्त-विषयः", "वैयक्तिक-दत्तम्", "प्रक्रिया", "वैयक्तिक-दत्त-भङ्गः" च "पर्यवेक्षक-प्राधिकरणम्" इत्यादीनाम् अर्थाः GDPR मध्ये दत्ताः सन्ति, च अन्यविधिषु समतुल्यपदानां समतुल्यः अर्थः भवति।

विरोधस्य स्थितौ, पूर्वता-क्रमः एवं भवति: (a) मानक-अनुबन्ध-खण्डाः च UK अनुबन्धपत्रम्, यत्र ते लागू भवन्ति; (b) इदं DPA; (c) आदेश-पत्रके अन्ये केचन दत्त-संरक्षण-शर्ताः; (d) अनुबन्धस्य शेषभागः। इदं DPA पक्षस्य दत्त-संरक्षण-विध्यन्तर्गतं कर्तव्यैः सह विरोधं जनयितुं न अभिप्रेतम्, च यः कोऽपि शब्दः तथा कुर्यात् सः विरोधं निवारयितुं आवश्यकतमं न्यूनतमं परिमाणं यावत् अवरोध्यते।

इदं DPA अनुबन्धस्य प्रभावी-दिनाङ्कात् आरभ्य यावत् वयं किञ्चित् अपि ग्राहक-वैयक्तिक-दत्तं न धारयामः तावत् लागू भवति, यत् अनुबन्धस्य समाप्तेः पश्चात् अपि भवितुं शक्नोति खण्ड १३ मध्ये उल्लिखित-विलोपन-समयरेखाणां कारणेन। अस्य कर्तव्यानि समाप्तेः पश्चात् यावत् वयं किञ्चित् अपि ग्राहक-वैयक्तिक-दत्तं धारयामः तावत् जीवन्ति, च गोपनीयता-कर्तव्यानि दत्त-संरक्षण-विधिना आवश्यकतया अनिश्चितकालं यावत् जीवन्ति।

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

We process Customer Personal Data solely to provide, secure, support and maintain the Service for the Customer, and for no independent purpose of our own. We do not sell Customer Personal Data, we do not share it for cross-context behavioural advertising, we do not combine it with personal data we receive from other sources except as permitted by Data Protection Law for a service provider, and we do not use it to train, fine-tune or evaluate any machine learning model. Our AI subprocessors process it for inference only, under commercial terms that prohibit training on it. We may create and use aggregated or de-identified statistics that identify neither the Customer nor any data subject, and we will not attempt to re-identify them.

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

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

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

Taking into account the nature of the processing, we assist the Customer by appropriate technical and organisational measures, insofar as this is possible, in fulfilling the Customer’s obligation to respond to a data subject exercising rights of access, rectification, erasure, restriction, portability or objection. The product itself is the first line of that assistance: the Account Owners and the workspace admins can search, edit and delete project content, manage members and roles, and retrieve project content through the API pull endpoint, the command line interface, the delivery bundle or a storage connector on a paid plan, and the Account Owners can delete the workspace. Where the product cannot answer a request, we will help on request within a reasonable period and at no charge for a reasonable volume of requests. If a data subject contacts us directly about Customer Personal Data, we will not respond substantively ourselves; we will tell them to contact the Customer and, unless prohibited, tell the Customer promptly.

Taking into account the nature of processing and the information available to us, we assist the Customer in meeting its obligations under Articles 32 to 36 of the GDPR and their equivalents, including data protection impact assessments and prior consultation with a supervisory authority. In practice that means providing this DPA, Annex II, the Trust Center disclosures, the retention schedule in the Privacy Policy, our security documentation and reasonable written answers to a security or privacy questionnaire. We may charge for assistance that goes materially beyond a reasonable volume, at our then-current professional services rates, and we will say so before doing the work rather than afterwards.

We notify the Customer without undue delay, and in any event within seventy-two hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notice describes, to the extent known at the time and updated as we learn more: the nature of the breach including where possible the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed to address it and to mitigate its effects; and a contact point for further information. We cooperate with the Customer and take the steps the Customer reasonably requests to assist in its own investigation and notification. A notice is not, and will not be construed as, an admission of fault or liability. We will not delay a notice in order to complete an investigation first.

At the Customer’s choice, we delete or return Customer Personal Data at the end of the provision of services, and delete existing copies, unless a law to which we are subject requires storage. In the product that works as follows: cancelling a subscription moves the Account to the Free plan, which includes one workspace, and every other workspace becomes read only and is deleted 30 days later, or sooner for a workspace that went through the same recently as clause 13 of the Terms of Service describes, unless the Customer upgrades or moves it first; deleting a workspace makes it read only for 30 days, during which an Account Owner can restore it, and after that period the workspace is purged from the live database, including projects, translations, version history, usage records, webhook delivery records, screenshots and audit events; closing the Account deletes every workspace on it in the same way and keeps the Account’s invoices for 7 years; deleting a User’s login is immediate and irreversible. Content the Customer retrieves through the API, the command line interface, the delivery bundle or a storage connector is out of our hands from the moment we deliver it. Encrypted backups are not reached by the purge and expire on the schedules in Annex II; while they exist they are isolated, encrypted and restored only for disaster recovery, never to return a purged workspace to service. A written request for return in a structured format made before deletion will be honoured once, at no charge, within a reasonable period.

We make available to the Customer the information reasonably necessary to demonstrate compliance with this DPA and with Article 28 of the GDPR, and allow for and contribute to audits, including inspections, conducted by the Customer or an auditor it mandates. In the first instance that obligation is met by this DPA, Annex II, the Trust Center, the security page and our completed security questionnaire responses. Where those are genuinely insufficient for the Customer’s regulatory obligation, the Customer may audit once in any twelve month period, on at least thirty days written notice, during business hours, without unreasonably disrupting our operations, subject to confidentiality obligations, limited to systems and records relating to the Customer’s own data, and at the Customer’s cost. A supervisory authority exercising a statutory power is subject to none of those limits. An auditor may not be a competitor of ours, and we may require a separate confidentiality undertaking from them.

यत्र ग्राहकव्यक्तिगतदत्तांशस्य अस्माकं संसाधने यूरोपीयआर्थिकक्षेत्रात् एकादेशनिर्णयेन अनावृतदेशे स्थानान्तरणं सम्भवति, तत्र मानकसंविदाखण्डाः एतस्मिन् DPA समाविष्टाः भवन्ति तस्य भागः च भवन्ति तथा च अधोलिखितरीत्या प्रयुज्यन्ते। Module Two (नियन्त्रकात् संसाधकपर्यन्तं) तत्र प्रयुज्यते यत्र ग्राहकः नियन्त्रकः भवति। Module Three (संसाधकात् संसाधकपर्यन्तं) तत्र प्रयुज्यते यत्र ग्राहकः स्वयमेव संसाधकः भवति। Clause 7 (डॉकिङ्ग् खण्डः) प्रयुज्यते। Clause 9 इत्यत्र, Option 2 (साधारणलिखितअनुमतिः) चयिता, ऊर्ध्वतन clause 09 इत्यत्र उल्लिखितसूचनाकालेन सह। Clause 11 इत्यत्र, वैकल्पिकस्वतन्त्रविवादनिवारणभाषा न चयिता। Clause 17 इत्यत्र, खण्डाः आयरलैण्ड्गणराज्यस्य विधिना शास्यन्ते यदि पक्षाः Order Form इत्यत्र अन्यं EU सदस्यराज्यविधिं न स्वीकुर्वन्ति। Clause 18(b) इत्यत्र, विवादाः आयरलैण्ड्गणराज्यस्य न्यायालयेषु समान आधारभूतरीत्या निवार्यन्ते। Annex I(A) पक्षाः, Annex I(B) स्थानान्तरणस्य वर्णनम्, Annex I(C) सक्षमप्राधिकारी, Annex II तकनीकी तथा संस्थागतउपायाः, तथा Annex III उपसंसाधकानां सूची, प्रत्येकं अधोलिखितरीत्या निर्दिष्टम्।

UK GDPR इत्यस्य अधीनं स्थानान्तरणार्थं, UK Addendum समाविष्टं तथा पूर्णं क्रियते यथा: Table 1 Annex I(A) द्वारा पूर्णं; Tables 2 तथा 3 clause 15 तथा एतस्य DPA-स्य Annexes I तथा II द्वारा पूर्णं, Approved EU SCCs इत्यस्य संस्करणं विश्वसनीयत्वेन गृहीत्वा; तथा Table 4 इत्यत्र, Approved Addendum परिवर्तने कश्चन पक्षः Addendum समाप्तं न कर्तुं शक्नोति। स्विसविधिना शासितं स्थानान्तरणार्थं, SCCs इत्यत्र GDPR इत्यस्य निर्देशाः Swiss Federal Act on Data Protection इत्यस्य निर्देशरूपेण पाठ्यन्ते, सक्षमप्राधिकारी Federal Data Protection and Information Commissioner भवति, सदस्यराज्यस्य निर्देशाः स्विट्जरलैण्ड्देशे निवासिनं दत्तांशविषयकं व्यक्तिं तस्य सामान्यनिवासस्थाने वादं दायितुं अधिकारात् वञ्चितं न कुर्वन्ति, तथा च SCCs कानूनीसंस्थाः दत्तांशं रक्षन्ति यावत् स्विसविधिः तत् न अपेक्षते।

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

For personal information subject to the CCPA, the Customer is the business and we are a service provider. We are prohibited from, and will not, sell or share that personal information; retain, use or disclose it for any purpose other than the business purposes specified in the Agreement or as otherwise permitted by the CCPA; retain, use or disclose it outside the direct business relationship between the parties; or combine it with personal information received from another source, except as the CCPA permits a service provider to do. We certify that we understand and will comply with these restrictions. We will notify the Customer if we determine that we can no longer meet them. The Customer may take reasonable and appropriate steps to stop and remediate unauthorised use, using the audit rights in clause 14. We provide the same level of privacy protection as the CCPA requires of the business.

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

प्रत्येकस्य पक्षस्य एतस्मात् DPA उत्पन्नं वा सम्बद्धं दायित्वं, चाहे संविदायां, अपराधे वा अन्यसिद्धान्तस्य अधीने, Agreement इत्यत्र उल्लिखितदायित्वसीमाभ्यः तथा बहिष्कारेभ्यः अधीनं भवति, तथा च तेषां सीमासु पक्षस्य दायित्वस्य यः कोऽपि निर्देशः सः Agreement तथा एतस्य DPA इत्येतयोः अधीने तस्य पक्षस्य समग्रदायित्वं सूचयति। एतस्मिन् खण्डे किमपि Standard Contractual Clauses इत्यस्य अधीने वा Data Protection Law इत्यस्य अधीने दत्तांशविषयकव्यक्तिनः अधिकारान् न सीमितं करोति, तथा च यत् दायित्वं वैधानिकरीत्या सीमितं न भवितुम् अर्हति तत् न सीमितं करोति।

अस्माभिः एतत् DPA अद्यतनं कर्तुं शक्यते यत्र Data Protection Law इत्यस्य परिवर्तनं, नवीनं वा संशोधितं स्थानान्तरणयन्त्रं, प्राधिकारिणः वा न्यायालयस्य निर्णयं, वा Service इत्यनेन ग्राहकव्यक्तिगतदत्तांशस्य संसाधनरीत्यां महत्त्वपूर्णं परिवर्तनं प्रतिफलितुं आवश्यकं भवति, यदा अद्यतनं ग्राहकव्यक्तिगतदत्तांशस्य दत्तं रक्षणं महत्त्वपूर्णरीत्या न न्यूनं करोति। अस्माभिः महत्त्वपूर्णअद्यतनस्य कृते न्यूनातिन्यूनं त्रिशतदिनपूर्वं सूचनां ईमेलद्वारा तथा च अस्मिन् पृष्ठे प्रदद्यामि, तथा च शीर्षे प्रभावति दिनाङ्कं परिवर्तयिष्यामि। अस्माभिः पूर्ववर्तीं संस्करणं अनुरोधे उपलब्धां रख्यामि।

एतत् DPA हस्ताक्षरं विना अस्मान् बध्नाति, अतः ग्राहकं सुरक्षितं भवितुं तस्य आवश्यकता न अस्ति। यदि भवतः प्रक्रियायाः कृते भवतः अभिलेखाय निष्पादितप्रतिरूपं आवश्यकं भवति, वा यदि भवान् रेडलाइनं उत्थापयितुं इच्छति, तर्हि privacy@transglot.ai इत्यत्र लिखतु कानूनीसंस्थानाम, पञ्जीकृतपता, सूचनासम्पर्कः तथा च हस्ताक्षरकर्ता सह, तथा च अस्माभिः हस्ताक्षरितप्रतिः प्रेष्यते। अस्माभिः सुरक्षा तथा गोपनीयताप्रश्नावलीनां प्रत्युत्तरं समानपतातः प्रदद्यते, तथा च Trust Center इत्यत्र बहुपरीक्षकैः आवश्यकं पैकं वहति ये किमपि लिखितुं पूर्वं कस्मिन्चित् सम्पर्कं कुर्वन्ति।

Data exporter: the Customer, being the person or company that holds the Account, as named on the Account or on the Order Form, acting as controller (or as processor where clause 01 applies) in respect of Customer Personal Data processed through the Service. Contact details: the Account Owners' email addresses and the notice contact given on the Order Form. Activities relevant to the transfer: use of a cloud localization platform to store, translate, review, deliver and manage software and content strings. Signature and date: as recorded by acceptance of the Agreement, or as executed under clause 22. Data importer: Digital Socket LLC, a limited liability company formed in Delaware, United States, trading as Transglot, acting as processor. Contact details: privacy@transglot.ai. Activities relevant to the transfer: provision of the Service described in the Agreement. Role: processor.

Categories of data subjects: the Customer’s personnel and contractors who hold a login (Account Owners and Billing Members, and workspace admins, developers, reviewers and translators); the Customer’s own end users, customers and other individuals to the extent their personal data appears inside source strings, translations, glossary entries, comments, screenshots or imported files; and the Customer’s billing and notice contacts. Categories of personal data: identity and contact data (name, email address, login identifier, Account, workspace and role); authentication data (hashed password, second factor enrolment, federated identity subject identifiers, API token digests); usage and technical data (IP address, user agent, pages and endpoints accessed, request and run identifiers, timings, outcomes, error traces, audit records); billing data (billing contact, billing address, tax identifiers, payment method token and card metadata held by the payment processor); content data (whatever personal data the Customer chooses to place in project content, which is under the Customer’s control and which the Acceptable Use Policy asks the Customer to keep free of payment card data, government identifiers, credentials and special category data). Sensitive data: none is requested or required, and none should be submitted; where the Customer nonetheless submits it, the restrictions and safeguards are those in Annex II applied to all Customer Content, and the Customer remains responsible for its lawful basis. Frequency: continuous, for the duration of the Agreement, on the Customer’s instruction. Nature and purpose: hosting, storage, indexing, machine translation, quality checking, translation memory matching, glossary enforcement, review workflow, delivery and transmission through the API, webhooks, connectors and the delivery bundle, together with support, security and billing. Duration of processing: the term of the Agreement plus the retention periods stated in the Privacy Policy and clause 13 of this DPA. Subprocessor processing: for the purposes, and for the durations, set out in Annex III and in the Trust Center.

Where the SCCs apply on the basis of Article 3(1) of the GDPR, the competent supervisory authority is the one in the member state in which the data exporter is established. Where they apply because the exporter is not established in the European Economic Area but is caught by Article 3(2), the competent authority is the one in the member state in which the exporter’s Article 27 representative is established. Where they apply on the basis of Article 3(2) and no representative is appointed, the competent authority is the one in the member state in which the data subjects whose personal data is transferred are located. For UK transfers the competent authority is the Information Commissioner’s Office; for Swiss transfers, the Federal Data Protection and Information Commissioner.

Data in transit is protected with TLS 1.2 or better at the edge, and connections below that are refused. Passwords are hashed with bcrypt at a cost factor of 12 and are never stored or logged in plaintext. API tokens and delivery keys are stored as SHA-256 digests, are displayed once at creation and cannot be recovered afterwards; publishable in-context keys are deliberately public identifiers bound to an origin allowlist rather than secrets, and are documented as such. Third party credentials, connector tokens, SSO configuration secrets and webhook signing secrets are held in encrypted columns using authenticated application-level encryption. Database backups are encrypted with AES-256 by the backup tool itself, independently of any provider-side encryption, and file backups are held in a password-encrypted repository. Two honest gaps: the live database and application volumes are not disk-encrypted, and server-side encryption of the object store is not asserted in our own configuration. We state both here rather than letting a reviewer discover them in diligence.

Every query in the application is scoped by Account, workspace and project, and a cross-tenant identifier answers 404 rather than 403 so that the existence of another tenant’s record never leaks. The two Account roles (Owner and Billing), the four workspace roles (admin, developer, reviewer and translator), eighteen project abilities and per-project and per-language grants are available on every plan including Free, so least privilege is never a paid upgrade. Two-factor authentication with time-based one-time codes and recovery codes, and passkeys, are available on every plan, and an Account Owner can require a second factor for an entire workspace, enforced at the workspace boundary so that federated and single sign-on doors cannot bypass it. SAML 2.0 single sign-on with just-in-time provisioning, generic OpenID Connect, SCIM 2.0 provisioning and de-provisioning, and the ability to switch off password login for a workspace are available on the Enterprise plan. API access uses scoped tokens with optional expiry. Internal administrative access is least privilege, and operator impersonation of a customer’s login is time-limited to thirty minutes and writes an audit record when it starts and when it ends.

Security-relevant events are written to an append-only audit trail: sign-in and single sign-on events, second factor and workspace MFA policy changes, member invitations, joins, role changes and removals, custom role changes, token and key creation and revocation, integration and connector connection and disconnection, review policy changes, branding changes, SCIM provisioning events, workspace rename and deletion requests. Plan, billing and spend cap changes, changes to the Account’s members and the closing of the Account are written to the Account’s own audit trail in the same way. Each record carries the workspace or the Account, the actor, the action, the target, structured metadata, the source IP address and the time, and the model layer refuses updates and deletes, so a record cannot be edited after the fact; on the Account’s trail the IP address is removed after 395 days. On the Enterprise plan the whole trail, the Account’s included, can be exported as CSV. Append-only is enforced in the application layer and there is no cryptographic hash chain or signature over the log, so we do not describe it as tamper-evident. Application errors are collected by an error tracker we host ourselves, configured not to send personally identifying information and not to capture request bodies, which is the setting that actually keeps customer strings out of a stack trace. Operational metrics are retained for thirty days.

Public endpoints are rate limited: the REST API at sixty requests a minute per token, the delivery endpoint at three hundred a minute per key and address, sign-in at five a minute per email and address, and registration at five a minute and twenty an hour per network block, with separate buckets for the other public doors. Outbound webhooks are signed HMAC-SHA256 over the timestamp and the raw body, sent as an explicit signature header and a timestamp header, and compared in constant time; the timestamp is published so the receiver can enforce its own replay window, and we are explicit that no server-side tolerance is enforced on our side. Inbound forge webhooks are verified by signature, with the delivery identifier as the replay guard. Cross site request forgery protection is applied to every state-changing browser request, sessions expire after 120 minutes of inactivity, sensitive actions require password re-confirmation within a 3 hour window, password reset links expire after 60 minutes, and destructive actions require typing the workspace name or re-entering a password. A frame-ancestors content security policy is applied; we do not claim a broad content security policy, because we do not yet ship one.

Usage metering records counts of words and tokens, never the body of a request. The shared exact-match translation memory pool stores the linguistic pair keyed by a hash of the source, together with plural forms and reuse counters, and stores no user column and no team column at all, so an entry cannot be traced to a person; the key name, file path, screenshots, comments and every other piece of surrounding context are stripped. Human-reviewed memory entries carry a workspace identifier, which functions as a hard tenant fence on the near-match query rather than as attribution, and that is why a reviewed entry is never returned to another workspace. Any project can leave the pool entirely with a per-project switch on every plan, which stops it both contributing and drawing. In-context screenshots are held on a private store with no public path and are served only through short-lived signed URLs.

The database is backed up continuously with write-ahead log archiving and periodic full and differential backups, retaining two full backups and seven differentials, encrypted with AES-256 by the backup tool. Application file storage is snapshotted nightly into a password-encrypted repository retaining thirty daily, twelve weekly and twelve monthly snapshots, with an integrity verification pass on each run. Restore procedures are documented and exercised. Backups are isolated from the production credentials that could delete them, and they are restored for disaster recovery only, never to return a purged workspace to service. Deployment images are retained for the last several releases so that a rollback is a minute rather than a rebuild.

Changes are made through version control with peer review, an automated test suite, static analysis and dependency scanning, and container image vulnerability scanning in the build pipeline, and a failing gate blocks the release rather than warning about it. Test environments do not use production customer data. Secrets are held encrypted at rest in the deployment repository and injected at runtime rather than committed. Several product claims are themselves enforced by tests: a translation engine that becomes reachable without a subprocessor disclosure row fails the build, and the advertised overage rate is pinned to the rate the system charges. Third party components are tracked and patched, and a build is refused when a scanner reports a vulnerability above threshold.

Access to production is limited to the personnel who need it, granted individually, and removed on role change or departure. Personnel are bound by confidentiality obligations that survive their engagement, and receive security and data protection guidance appropriate to their role. We operate a documented incident response process with defined severities, an on-call rotation, alerting on service health and background job health, and post-incident review. We publish a vulnerability disclosure policy with a safe harbour for good faith research and a security address that is monitored. We hold no third party security certification today: a SOC 2 Type II audit is in progress and an AI management system standard is being pursued, and the compliance status published on our site is rendered from a configuration value that cannot show a certificate we do not hold.

Scheduled jobs enforce the retention windows published in the Privacy Policy rather than leaving them as intentions: translation version history at 180 days with a floor of the newest 20 per string, notifications at 90 days, resolved comment threads at 365 days from resolution, the activity feed at 180 days, assistant conversations at 90 days, in-context screenshots at 90 days with the stored object deleted alongside the record, connector sync records at 90 days keeping the latest per connection, referral click records at 90 days, unreviewed and unused translation memory entries at 90 days, failed background jobs at 7 days, expired API tokens 24 hours after they lapse, federated login correlation records at their own expiry, signup integrity signals 90 days after the Account was created or the pair was last seen, sign-up refusal records at 90 days, welcome words velocity records at 30 days for a domain and 24 hours for a network, sign-up allowlist entries at the expiry an operator set, never more than 365 days, Accounts never verified and holding no workspace at 30 days, welcome words, trial and card fingerprint records at 1,095 days, and the IP address on an Account’s audit trail at 395 days. Deletion runs in bounded batches rather than as one unbounded operation. Workspace deletion is a 30 day reversible grace period followed by a cascading purge of the live database. Webhook delivery records have no time-based prune today and are removed with their endpoint or their workspace.

For transfers to subprocessors we rely on the contractual measures in clause 15 together with these supplementary measures: transport encryption on every hop; contractual prohibitions on training, on onward transfer without equivalent protection, and on processing outside our instructions; a published and code-enforced disclosure list so that no undisclosed vendor can be routed customer text; the ability for a customer to disable the optional features that engage a conditional subprocessor, including the semantic translation memory feature and the per-project translation memory switch; retention windows enforced by scheduled jobs so that transferred data does not accumulate indefinitely; and the government access commitments in clause 17, including challenge, minimisation, notification and record keeping.

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