Service providers

The services behind Tringify.

The companies that help us run Tringify, what they do, and the information they handle.

Version: 2026-11-15. Effective date: 2026-11-15.

Tringify Ecommerce Private Limited, LGF-116, Khazana Complex, Aashiana, Lucknow 226012, India, uses the services below to operate Tringify. Our Data Protection Officer is Agrim Khurana, agrim@tringify.com. Contact privacy@tringify.com about this list.

A provider processing merchant-controlled personal data on our instructions is a subprocessor for that activity. Providers supporting Tringify’s own account, business or website activities are recipients for those activities. A provider can have different roles for different services. Provider references include the applicable contracting affiliate for the service.

This list accompanies our Privacy Policy and Data Processing Agreement.

Core infrastructure and communications

Provider / servicePurpose and personal dataProcessing locations and scope
Microsoft AzureHosting, databases, storage, backups and operational monitoring. Account and store records, shopper contacts and addresses, orders, communications, content, technical identifiers and audit records, as needed for the service.Primary store databases in Central India or Sweden Central according to store placement. Shared account/control processing includes India; India database recovery copies are held in Sweden. Subprocessor for merchant data and hosting provider for Tringify’s own processing.
Cloudflare, Inc.Website/storefront delivery, Workers and related services, R2 and other storage, DNS, certificates, abuse prevention and protected operational access. Requests, content, files, IP/device information, domain/DNS records and authentication metadata.Global edge processing. Designated EU media and private-file storage uses the EU jurisdiction; other services can involve international processing. Subprocessor for merchant data and provider for Tringify’s own processing.
Amazon Web Services: SES, SNS and SQSEmail sending and delivery outcomes. Sender/recipient details, message content and attachments, identifiers, bounce/complaint records and delivery status.Regional email infrastructure; sending region depends on service configuration. Delivery involves recipient mail systems worldwide. Subprocessor where messages contain merchant-controlled data.
Google Workspace: Google LLC / Google Ireland Limited, as applicableSupport and business email. Names, email addresses, message content and attachments supplied in correspondence.International email processing, including recipient mail systems. Recipient for Tringify’s business communications and subprocessor to the extent support messages contain merchant-controlled data.
GitHub, Inc.Source, builds/releases and authorised operational diagnostics. Operational identifiers, actor details and personal information included in necessary diagnostic logs or artifacts.International service processing. Operational recipient and subprocessor to the extent merchant-controlled personal data is included; it does not host routine store databases.

Optional AI and mobile notifications

Provider / servicePurpose and personal dataProcessing locations and conditions
Google Vertex AIStandard image generation, image descriptions, translation and email templates. Selected text, prompts, images, content context and generated output, including personal information the user supplies.EU location for EU-home stores; global location otherwise. Intermediary Cloudflare processing also applies. Subprocessor when the feature processes merchant-controlled data.
Google Gemini APIAI video generation. Prompts, an optional starting image chosen from the store’s files, video settings and the generated video with sound.Global API processing, for stores in every region; the video is stored in the store’s region. Subprocessor when the feature processes merchant-controlled data.
OpenAITransparent-image generation. Submitted prompts, image-generation settings, generated output and associated result metadata.International API processing, for stores in every region. Subprocessor when the feature processes merchant-controlled data.
Google Firebase Cloud MessagingAndroid notifications. Device tokens, alert text and event data, including shopper or order information included in notifications to merchant/staff devices.Global service. Subprocessor to the extent notification content includes merchant-controlled data.
Apple Push Notification serviceiOS notifications. Device tokens, alert text, badges and event data, including information about people described in alerts.International service processing. Subprocessor to the extent notification content includes merchant-controlled data.

Optional features send only the content needed for the requested operation. Merchants should submit only information they are authorised to use and review generated content before using it.

Recipients for Tringify’s own activities

Provider / servicePurpose and personal dataRole and scope
Razorpay and PayPal, where offeredTringify subscription and platform payments. Payer/contact and billing details, payment references, mandates and transaction information needed for the payment.Recipients for Tringify’s own billing; payment providers also process data for their independent financial, fraud-prevention and legal responsibilities. Processing follows the provider and payment service used and can involve other countries.
Google AnalyticsOptional marketing-site analytics. Consented browsing events, page/referrer information, device metadata and identifiers.Website analytics recipient; international processing. Loads after analytics permission is granted. The Privacy Centre does not load marketing analytics.
Cloudflare Web AnalyticsOptional marketing-site analytics. Request and browsing information used to measure website use.Website analytics provider; global processing. Uses the same analytics permission gate.
ipapi.co, IPGeolocation.io and ipwho.isConditional country-detection services. Visitor IP address and ordinary browser request metadata to suggest a country.Website recipients when the site cannot resolve an allowed country from page context or a saved selection. Requests can involve international processing. This fallback is disabled on the Privacy Centre.

Custom domains, certificates and public records

Certificates for custom domains are issued through Cloudflare. Domain names and validation information are processed to issue certificates and provide HTTPS. Because certificates are issued for custom domains, their names and public certificate information appear in public Certificate Transparency logs, searchable worldwide. Historical entries are not removed when a domain is disconnected or a store is deleted.

Public DNS records disclose names and values as required by DNS. Avoid placing private information in public record values. Public log readers and DNS users are not all appointed as Tringify subprocessors.

Merchant-selected services

Merchants can independently install or connect payment, messaging, advertising, shipping and other services, including Razorpay, PayPal, PhonePe, MSG91, Google, Meta, Snapchat and Shiprocket where available. Those services receive information within the permissions and features the merchant selects. For example, payment services receive checkout/payment information, messaging services receive recipient details and message content, advertising integrations receive authorised conversion or audience information, and shipping services receive order and delivery details.

The merchant’s agreement, settings, lawful basis and notices govern these relationships. An independently selected service is not automatically Tringify’s subprocessor. Hosting providers supporting a Tringify-operated connector remain part of our processing chain where applicable. Merchant-selected apps, webhooks and theme embeds may introduce additional recipients.

Locations and international transfers

A store’s home placement determines its primary store database, not every service or copy. Shared account processing, global edge services, support, communications, AI, payments and merchant-selected services can involve other countries. Selecting a page language, currency or shopper location does not relocate the store.

For international transfers restricted by applicable data-protection law, Tringify uses Standard Contractual Clauses through each provider’s standard data processing terms, with the applicable module and supplementary measures where required. The DPA addresses transfers involving Tringify in India. You can request information about applicable safeguards and relevant terms at privacy@tringify.com, with confidential details protected where permitted.

Changes and objections

For proposed additions or replacements of subprocessors processing merchant-controlled data, Tringify will give affected merchants at least 30 days’ notice to their registered owner/contact email, with an account notice where available, as described in the DPA. Updating this page alone does not replace that notice. The DPA describes objections on reasonable data-protection grounds, available solutions and urgent changes required by law or security incidents.

Send subprocessor questions and objections to privacy@tringify.com.