Version: 2026-10-26. Effective date: 2026-10-26.
This agreement forms part of the Store Agreement between the merchant identified in the store’s account and Tringify Ecommerce Private Limited, India (“Tringify”). It applies when Tringify processes personal data on the merchant’s behalf to provide the services. It prevails over conflicting general terms for that processing. Mandatory transfer clauses prevail where they apply.
Tringify’s registered address: LGF-116, Khazana Complex, Aashiana, Lucknow 226012, India. Data Protection Officer: Agrim Khurana, agrim@tringify.com. Tringify has not yet appointed a representative in the European Union under Article 27 GDPR; until it does, contact the Data Protection Officer directly. Privacy contact: privacy@tringify.com. Security contact: security@tringify.com.
1. Roles and instructions
The merchant determines the purposes and essential means of processing its customer and store data and acts as controller. Tringify acts as processor. If the merchant is itself a processor, it confirms that its controller has authorised this appointment and the instructions it gives Tringify.
The Store Agreement, this agreement, the merchant’s configuration, authorised feature use and written requests form the documented instructions, including instructions about international transfers. Tringify will process personal data only on those instructions, unless applicable law requires otherwise. Where GDPR Article 28(3)(a) applies, the exception is a requirement of Union or Member State law. Tringify will inform the merchant before that processing unless the law prohibits notice on important grounds of public interest. Other government demands are handled under applicable law and the transfer clauses; they do not create a general permission to use the data.
Tringify will promptly tell the merchant if it believes an instruction infringes applicable data-protection law. It may suspend the affected instruction while the parties resolve the issue, without unnecessarily interrupting other services.
Tringify separately acts as controller for its own account administration, billing, platform-security and legal records, as described in the Privacy Policy. This agreement does not give Tringify a right to repurpose merchant-controlled shopper data for its own advertising or to sell it.
The merchant is responsible for its lawful basis, notices, consent where needed, authorised users and independently selected integrations. It must not submit personal data unrelated to the services or use a feature for an incompatible purpose.
2. Processing covered
The subject matter is hosting and operating the merchant’s store and the related features it requests. Annex 1 describes the processing, categories of data, people concerned and duration. Processing is continuous while the relevant services are used, with individual transfers triggered by visits, transactions, messages, uploads, support requests and enabled features.
Personal data supplied to optional AI features remains within the instructed purpose. Selecting such a feature authorises sending the necessary content to the provider listed for it; it is not authority to send unrelated customer records. The merchant must review generated content before using it.
3. Confidentiality and security
Tringify will ensure that people authorised to process merchant data are bound by confidentiality obligations or an appropriate statutory duty. Access will be limited to what is needed for their work and managed through appropriate authentication and permissions.
Taking account of the processing, risks, available technology and implementation costs, Tringify will maintain appropriate technical and organisational measures under GDPR Article 32. Annex 2 identifies the implemented technical measures and their limits. Tringify will review the measures and maintain appropriate protection as systems change. It will not materially reduce the agreed overall protection during the service term.
The merchant remains responsible for its users’ permissions, credentials and devices, store content and independently selected services. No provision removes either party’s own legal security duties.
4. Subprocessors and merchant-selected services
The merchant gives general written authorisation for Tringify to use the subprocessors in Annex 3 for the relevant services. Optional-feature entries apply only when that feature processes merchant data. Tringify will enter written terms imposing substantially the same data-protection obligations relevant to the entrusted processing, including sufficient security guarantees. Tringify remains responsible to the merchant for its subprocessors’ performance of those obligations as required by Article 28(4).
Tringify will maintain the subprocessor list. For a proposed addition or replacement, it will send affected merchants a notice to their registered owner/contact email, with an account notice where available, at least 30 days before the provider starts the affected processing. The notice will identify the provider, service, data, locations and intended start date. An update to a webpage alone is not the notice mechanism promised here.
The merchant may object on reasonable data-protection grounds by emailing privacy@tringify.com within that notice period. The parties will seek a practical solution, such as additional safeguards, an alternative service or disabling the affected feature. Tringify will not begin the disputed processing while the objection remains unresolved. If no lawful, reasonable solution is available, either party may end the affected service before the change, with return/deletion under section 8 and a refund of unused prepaid fees for that affected service. This does not require ending unrelated services.
Where an immediate change is required by law or necessary to address an urgent security incident, Tringify will give as much advance notice as practicable and explain the reason; notice and an opportunity to object will follow promptly if advance notice is impossible. This exception does not displace any longer or stricter requirement of applicable transfer clauses.
A payment, messaging, advertising, shipping or other service independently selected and contracted by the merchant is not automatically Tringify’s subprocessor. Tringify may transmit data to it on the merchant’s documented instructions and approved permissions. The merchant is responsible for the relationship and transfer basis for that service. Hosting providers used by a Tringify-operated connector remain within Tringify’s own processing chain where applicable.
5. Requests from individuals
Tringify will assist the merchant with requests to access, correct, export, erase, restrict or object to processing, and other applicable rights, taking account of the nature of processing and available information. Assistance includes the available customer privacy/export tools and reasonable support for requests those tools cannot complete.
If Tringify receives a request about merchant-controlled data, it will promptly direct the person to the merchant or relay the request. It will not independently disclose or delete that data contrary to lawful instructions, except as required by law. The parties will use proportionate identity checks and protect other people’s information. Assistance must allow the merchant to meet applicable deadlines; a support process does not extend a statutory period.
6. Personal-data breaches and compliance assistance
Tringify will notify the merchant without undue delay after becoming aware of a personal-data breach involving data processed for that merchant and, in any event, within 48 hours of awareness. It will use the registered owner/security contact and follow up through another available channel if delivery fails. Initial notice will not wait for a completed investigation.
Notice will include, as available, the nature of the breach, affected categories and approximate numbers of people and records, a contact for follow-up, likely consequences, and measures taken or proposed to contain and address it. Information may be provided in stages without undue further delay. Tringify will investigate, preserve appropriate evidence, mitigate the incident and provide reasonable updates.
Tringify will assist the merchant with its duties under Articles 32–36, taking account of the processing and information available: security, breach assessment and notifications, data-protection impact assessments and prior consultation with supervisory authorities. The merchant remains responsible for its controller notifications, including any applicable 72-hour authority deadline. Tringify’s notice period is not an extension of that deadline.
7. Information, audits and inspections
Tringify will make available information necessary to demonstrate compliance with this agreement and Article 28. It will allow and contribute to audits, including inspections, by the merchant or an auditor the merchant appoints.
The parties will first use relevant documentation and existing assessment evidence where that adequately answers the issue. They will agree reasonable scope, timing, confidentiality and access arrangements to protect other customers’ information and service security. These arrangements cannot prevent an effective audit, delay an urgent investigation or restrict a supervisory authority’s lawful access. An auditor’s independence and confidentiality obligations must be appropriate to the information accessed.
Routine audits should use reasonable notice and avoid unnecessary disruption. Additional or urgent audits remain available after a material incident, credible compliance concern or regulatory requirement. Any agreed reasonable costs must not make the merchant’s statutory audit right ineffective. Tringify will address identified non-compliance and report the corrective action relevant to the merchant.
8. Return, deletion and retention
At the merchant’s choice, Tringify will return or delete personal data processed on its behalf after the relevant service ends, and delete existing copies unless applicable law requires their storage. Where GDPR Article 28(3)(g) applies, the statutory exception is Union or Member State law. The merchant should export needed records before closing the store and can request assistance at privacy@tringify.com. Return will use a commonly used, readable format appropriate to the data and available export tools.
The normal live-store flow has a 30-day closing period in which reopening is possible, followed by closure and a purge scheduled 30 days later. A transfer store locked at its build deadline is normally scheduled for purge 60 days after that deadline unless extended or handed off. Development-store and abandoned-setup deletion use separate deletion requests. Authorised staff can postpone a scheduled purge by up to 365 days in total from its original scheduled date. A postponement for merchant-controlled data must have a documented instruction or lawful preservation reason; the software limit alone is not a lawful reason to keep data.
Purge is a coordinated process across services, databases, media, domains and analytics. A scheduled date starts that process and is not proof every dependent step has finished. Tringify will monitor failed or waiting steps and complete them without undue delay. It will provide confirmation of completion and identify any lawfully retained categories or outstanding protected backup copies when reasonably requested.
Store audit logs, including domain/DNS history, normally age out after 90 days rather than being removed by immediate store purge. Ordinary backup settings include a 35-day database retention/immutability window, version cleanup and an additional 35-day soft-delete window; message and cache copies have 35-day protection, deletion rules after 36 days and seven-day soft deletion. A final migrated database archive is protected for 90 days with deletion scheduled after 91 days. Backup-chain dependencies and provider lifecycle execution mean these are settings, not a universal last-copy deadline.
Backups awaiting expiry will remain protected, be unavailable for ordinary business use and be accessed only as needed for recovery, security or a legal obligation. If a backup is restored, Tringify will reapply relevant erasure instructions before making restored data available for ordinary use. In encrypted analytics archives, store purge removes the per-store decryption key; any backup containing the key must remain within the same recovery/deletion controls. Tringify will require corresponding deletion or expiry from its subprocessors.
Custom domains on closed or otherwise eligible deletion-state stores can be released after another store proves DNS control. Reopening does not restore an already released association. Public DNS publication and Certificate Transparency history cannot be recalled by a store purge.
9. Regions and international transfers
The primary store database stays where the store was created: stores created in the EU use Azure Sweden Central; stores created in India use Azure Central India. Shared account processing includes India. India backup copies are also configured in Sweden. Global edge delivery, support, push, billing and the provider-specific services in Annex 3 are separate from primary store placement. The merchant’s or shopper’s language, currency or current location does not relocate a store.
Tringify will not make a restricted international transfer without the safeguards required by applicable data-protection law. For transfers to its providers, Tringify uses Standard Contractual Clauses through each provider’s standard data processing terms, with the applicable module and supplementary measures where required.
Annex 4 describes transfers between the merchant and Tringify and onward transfers. The parties will assess the laws and practices affecting relevant transfers and respond to government-access demands under the applicable clauses. If the required protection cannot be maintained, the affected transfer must be suspended and resolved as those clauses require. Tringify will provide relevant transfer information on request, subject to lawful confidentiality protections.
10. Contact and other terms
Send instructions, requests, objections and transfer-document requests to privacy@tringify.com. Report security incidents to security@tringify.com. The merchant must keep its owner and security contacts current.
The Store Agreement’s other terms continue to apply except where they conflict with this agreement, mandatory law or applicable transfer clauses. Liability limits cannot reduce rights or obligations under mandatory transfer clauses or rights that applicable law does not permit the parties to exclude.
Annex 1: Processing details
| Item | Description |
|---|---|
| Subject matter | Provision, operation, maintenance and support of the merchant’s online store and requested features. |
| Nature of processing | Collection, receipt, recording, organisation, storage, retrieval, use, transmission, correction, export, restriction, erasure and recovery as instructed. |
| Purposes | Storefront delivery, customer accounts, checkout/orders, communications, fulfilment support, merchant-authorised integrations, analytics, media/content and optional AI features, security and technical support. |
| People | Shoppers, customer-account holders, delivery recipients, merchant staff/collaborators and other people whose information the merchant lawfully submits. Tringify’s separate controller activities remain outside this annex. |
| Data | Names; email/phone and postal/delivery addresses; account/store/customer identifiers; order and transaction references; cart and purchase details; preferences/consent; messages and uploaded content; images and prompts selected for AI; IP/device/browser/session data; domain/DNS records; activity/audit information; push tokens and notification payloads where relevant. Full payment credentials handled directly by a payment provider are not represented as stored by Tringify. |
| Sensitive data | Not intentionally required by the core service. Free text, images or merchant products can nevertheless disclose sensitive information. The merchant must avoid unnecessary sensitive data and obtain written agreement on appropriate safeguards for processing requiring special protection. |
| Frequency | Ongoing service processing and feature-triggered transfers; backups on configured schedules. |
| Duration | Service term and the necessary return/deletion period in section 8; specific lawful retention exceptions must be identified and limited. |
Annex 2: Security measures and boundaries
Tringify maintains the following measures for the processing covered by this agreement. The measures apply according to the service and data involved.
| Area | Measures | Scope |
|---|---|---|
| Transmission | Public HTTPS through Cloudflare, protected operational tunnels, HTTPS provider connections and restricted private-network database access | Internal service communications are protected by network and access controls; encryption is applied according to the connection. |
| Storage | Encrypted cloud storage and private backup accounts; application encryption for integration credentials; per-store encryption keys for analytics archives | Access to storage and encryption keys is restricted to authorised services and personnel. |
| Authentication and access | Account sessions and passkeys, scoped user/store/organisation permissions, authenticated internal requests, app permissions, managed service identities and protected operational access | Access is limited according to role and operational need. Available account controls depend on the feature used. |
| Segregation | Store-scoped authorisation, store-home routing and regional store databases | Account and platform-control services are shared; authorised support and global provider services may involve other locations. |
| Audit and monitoring | Account, store and domain/DNS audit events; operational logs and traces; redaction of selected sensitive fields | Logs can contain personal identifiers and follow the retention schedules applicable to them. |
| Recovery | Database replication, database and service backups, recovery procedures, protected backup storage and retention controls | India database recovery copies are held in Sweden. Backup expiry is subject to section 8; no fixed recovery time is guaranteed. |
| Erasure | Coordinated deletion across services, retry handling, removal of analytics archive keys and expiry jobs | Protected backups await expiry; relevant erasure instructions are reapplied following restoration. |
| Confidentiality and operations | Confidentiality obligations, scoped secret access, authenticated operational actions and controlled releases | Authorised personnel may access data as needed for support, recovery, security or legal obligations. |
Annex 3: Subprocessors for merchant processing
Only services processing data on the merchant’s behalf fall within this annex. The service-provider and subprocessor list also explains recipients for Tringify’s own activities and merchant-selected services. Provider references include the applicable contracting affiliate for the service.
| Provider / service | Processing and data | Locations and conditions |
|---|---|---|
| Microsoft Azure | Hosting, databases, operational logs and backups; the data and people described in Annex 1 as needed to operate the service | Primary store databases in Central India or Sweden Central; shared control data includes India; India database recovery copies in Sweden. |
| Cloudflare, Inc. | Edge delivery, storage, DNS, certificates, abuse prevention and protected operational access; requests, content, files, domain/DNS records and technical identifiers | Global edge processing; designated EU media and private-file storage uses the EU jurisdiction. Other services can involve international processing. |
| Amazon Web Services | Email delivery and outcomes through SES, SNS and SQS; message content, addresses, identifiers and delivery records | Regional email infrastructure and worldwide recipient mail systems; sending region depends on the service configuration. |
| Google Vertex AI | Optional standard images, descriptions, translation and templates; selected prompts, text, images and outputs | EU location for EU-home stores, global location otherwise; intermediary edge processing also applies. |
| Google Gemini API | Optional AI video generation; prompts, an optional starting image, video settings and the resulting video | Global API processing, for stores in every region; the video is stored in the store’s region. |
| OpenAI | Optional transparent-image generation; submitted prompts, generation settings and resulting output | International API processing, for stores in every region. |
| Google Firebase Cloud Messaging | Android push tokens and notification/event content, including information about people described in alerts | Global service. |
| Apple Push Notification service | iOS push tokens and notification/event content, including information about people described in alerts | International service processing. |
| Google Workspace: Google LLC / Google Ireland Limited, as applicable | Support and business email; names, email addresses, messages and attachments, including merchant-controlled data supplied in support requests | International email processing, including recipient mail systems. |
| GitHub, Inc. | Authorised operational diagnostics, build logs and artifacts to the extent they contain merchant personal data | International service processing; operational records are limited to the information needed for the task. |
Restricted transfers to these providers use Standard Contractual Clauses through their standard data processing terms, with supplementary measures where required. Optional services apply only when used for the merchant’s data.
Certificates for custom domains are issued through Cloudflare. The domain and certificate-validation information are processed for issuance, and custom domain names appear in public Certificate Transparency logs because certificates are issued for them. Historical certificate entries and public DNS disclosures cannot be recalled through store deletion.
Tringify’s own payment and website analytics/geolocation recipients and independently selected merchant integrations have the roles described in the provider list. They are not automatically subprocessors for merchant-controlled data under this agreement.
Annex 4: International transfer terms
Transfers from a merchant to Tringify in India, including access from India to an EU-home store, must have the safeguards required by applicable data-protection law. Where the Standard Contractual Clauses in Commission Implementing Decision (EU) 2021/914 apply to the transfer and importer, the parties will enter the applicable clauses without modifying their mandatory protections. Module Two applies to controller-to-processor transfers and Module Three to processor-to-subprocessor transfers. A merchant acting as processor must have its controller’s authority.
The transfer documentation identifies the merchant and Tringify using their agreement and account details, describes the processing using Annex 1, and records the security measures in Annex 2 together with any transfer-specific safeguards. It identifies the competent supervisory authority under Clause 13 and the applicable governing law and courts under Clauses 17 and 18. Subprocessor authorisation and notice are addressed in section 4, subject to the mandatory requirements of the applicable clauses.
For onward transfers to its providers, Tringify uses Standard Contractual Clauses through each provider’s standard data processing terms. The relevant processing, locations and conditions are described in Annex 3 and the linked provider list. The parties will assess the relevant laws and practices and implement supplementary measures where required.
Applicable transfer clauses take precedence over conflicting provisions of the Store Agreement or this agreement. Liability limits, audit arrangements and general governing-law provisions do not modify their mandatory protections or individuals’ rights.
For UK or Swiss restricted transfers, the parties will put in place the applicable UK International Data Transfer Addendum or Swiss adaptations, or other safeguards required by the applicable law. Contact privacy@tringify.com to arrange the relevant transfer documentation before making a transfer requiring it, and to request information about the safeguards that apply.
Reference: European Commission Standard Contractual Clauses.