Skip to content
PIM-TNG
Home Features AI Agent Implementation Case studies Pricing Contact us →
Language: EN
  • English
  • Български
  • Català
  • Español

Trust

Your data stays yours.

Where PIM-TNG stores your data, who can access it, how it is protected, and what happens when you leave.

  • Residency
  • Access
  • AI
  • Backups
  • Leaving
  • Subprocessors
  • GDPR

The essentials

Your region, your choice

You choose where your PIM-TNG environment is hosted. Our standard European regions are EU Central in Germany and EU East in Sofia, Bulgaria. If you need your data hosted in a specific country, we can deploy PIM-TNG with a suitable hosting provider there.

Customer isolation

Each customer has its own database, database role and application container. Starter and Basic customers may share the underlying PostgreSQL server and object-storage infrastructure. Access is separated using customer-specific credentials and permissions, so each environment can only access its own data.

Protected

Data is encrypted in transit with TLS and at rest with AES-256. Infrastructure administration is restricted to a private network.

Backups that fit your requirements

Every deployment includes backups and an offsite copy. If you need point-in-time recovery, longer retention or additional backup schedules, we can configure them for your environment.

Data residency

You choose where your data lives.

PIM-TNG is deployed by region rather than forcing every customer into the same location.

Our standard regions are:

  • EU CentralGermany
  • EU EastSofia, Bulgaria

If your company requires data to remain in a particular country, we can work with a suitable hosting provider and deploy PIM-TNG there.

Your product information, media and primary backups remain within the infrastructure configured for your environment, subject to the backup configuration agreed for that deployment.

Your product data remains yours. We use it to operate PIM-TNG. We do not sell it or use your catalog to build unrelated products.

Access

People only get the access they need.

Every PIM-TNG user has an individual account. Roles control what people can read or change. Product permissions can also be limited by tab, so someone editing marketing content does not automatically need access to administration, imports or integrations.

API access is tied to a real user account and inherits that user's permissions.

Administrative access to the database, storage and application infrastructure is restricted to the private infrastructure network. Security-relevant actions are recorded in the audit log.

AI

The catalog stays put.

Using the AI agent does not give it privileged access to your data. The agent acts as the signed-in user and follows the same roles, permissions and product validation rules.

Customers with specific AI requirements can choose compatible providers and deployment options. Enterprise customers can also use BYOK or a locally hosted model.

Backups

Backups can match your requirements.

Every PIM-TNG deployment includes a backup strategy with primary backups and a separate offsite copy. The exact locations and retention periods depend on the region and deployment selected for your environment.

If your organization has additional recovery requirements, we can configure options such as:

  • point-in-time recovery (PITR)
  • longer retention periods
  • additional scheduled backups
  • customer-specific backup locations

This allows the backup and recovery policy to match your organization's operational or compliance requirements.

Leaving PIM-TNG

Take your data with you.

There is no proprietary export format and no export fee. Your catalog can be exported using the same export system used for your other channels, including XLSX and channel-specific formats. Original media can also be retrieved.

When an account is closed, its database, storage data and application environment are retained for one month in case the cancellation was accidental. After that, they are deleted. You can also ask us to delete them sooner.

Subprocessors

The companies involved depend on your deployment.

Hosting providers and infrastructure subprocessors may vary depending on the region you choose.

Your deployment documentation and Data Processing Agreement identify the providers involved in your environment. Other service providers, such as Cloudflare or an AI model provider, are listed where applicable.

GDPR

Controller and processor

For information stored inside a customer's PIM-TNG tenant:

Controller
The customer.
Processor
PIM-TNG.

PIM-TNG normally processes limited personal information required to operate the service, such as user identities, permissions, sessions, audit records and support communications.

The catalog itself is generally product information rather than personal data, unless the customer chooses to store personal data in it.

For the PIM-TNG website and communications sent directly to us, PIM-TNG acts as controller.

Is there anything else your review needs?

If your process needs a written description of the setup, or an answer about how one particular field or file would be handled, ask us directly. We would rather answer the specific question than have you infer it from a page.

Contact usSee pricing
PIM-TNG

Product information management for manufacturers whose catalogs have to be right across distributors, ecommerce and multiple markets at once.

Pages

  • Home
  • Features
  • AI Agent
  • Implementation
  • Case studies
  • Pricing

Contact

  • [email protected]
  • Contact us
  • About us
© PIM-TNG. All rights reserved.
Trust & SecurityPrivacy PolicyData Processing AgreementLegal Notice