Security starts
with control.

From signing in to deciding who can access your store, security is part of how you work on Tringify.

Secure your account Explore the Privacy Centre

Protect your account.

Passkeys, two-factor authentication and session controls help keep access in your hands.

Choose who can do what.

Give your team and collaborators the access they need for their work.

Understand your data.

Clear privacy information and a process for accessing, correcting or deleting personal information.

Sample screens

A stronger way to sign in.

Manage your account’s security from Tringify Accounts. Review your sign-in methods and the devices with access.

Open account security

Passkeys

Sign in using a supported device’s fingerprint, face recognition or screen lock. Manage and remove the passkeys registered to your account.

Two-factor authentication

Add a verification step to password sign-in. Use an authenticator app or the supported email method, and keep your backup codes somewhere safe.

Active sessions

Review signed-in devices and revoke sessions you no longer recognise or need. You can also sign out your other devices.

Recovery codes

Save recovery codes when setting up your account protection. Generating a new set replaces the old codes.

Your team. Your permissions.

Keep ownership, staff access and app access distinct. Review permissions as people join, change roles or leave.

Explore Teams

Access for the job.

Choose staff permissions for the parts of your store they work with, and update that access when their responsibilities change.

Collaborators you approve.

Review access requests from partners. The merchant controls the access granted to the store.

Consider each installation.

Review an app’s requested permissions and privacy information before installing it. Manage which team members can access installed apps.

Remove access when it ends.

Remove memberships and revoke sessions when access is no longer needed. Use individual accounts so people do not share credentials.

Protection beyond the sign-in screen.

Technical controls and recovery procedures support the services your store relies on.

Protected connections and permissions.

Tringify’s public services use HTTPS. Requests to protected account and store features are checked against the caller’s identity and access.

Backups with recovery in mind.

Production databases have backups and archived changes for recovery. We have tested restoring database information to a selected point in time.

Recovery is a process.

Redundancy and recovery checks help us respond to failures. Recovery time depends on the incident and affected services; any contractual recovery commitment must be expressly agreed.

Privacy you can act on.

Use the Privacy Centre to make a request about your information and track its progress. Merchants manage shopper requests through their store’s privacy workflow.

A few habits make a difference.

Use individual accounts.
Give each team member their own account. Keep passkeys, passwords and recovery codes private.
Review access regularly.
Remove old memberships, unused apps and sessions. Give partners and staff only the access their work requires.
Keep your store’s promises clear.
Publish accurate customer policies and respond to privacy requests. Review how apps and integrations handle customer information.

Questions, answered.

Where do I manage passkeys and two-factor authentication?

Manage your account’s security from Tringify Accounts. Review your sign-in methods and the devices with access.

What if I lose access to my passkeys?

Use a recovery code to sign in if you lose access to all your passkeys. Generating a new set of recovery codes replaces the old codes.

Can I sign out my other devices?

Yes. Review signed-in devices and revoke sessions you no longer recognise or need. You can also sign out your other devices.

Is there a guaranteed recovery time?

Recovery time depends on the incident and affected services; any contractual recovery commitment must be expressly agreed.

Found a security concern?

Tell us what you found and how to reproduce it. Use accounts you control, avoid accessing other people’s data, and stop if testing could disrupt a service. A report does not require exploiting the issue further.

Report a concern