SynqDocs
Guides

Leaving Synq

What an export through the management API gives you, what can't come out, and what your users redo on another system.

Your users are yours, and you can export them through the management API at any time, on every plan. An export gives you each user's profile, email address, wallets, linked accounts and your own metadata. Password hashes and passkeys never come out, so people who sign in with a password set a new one on the system you move to, and people with a passkey make a new one there.

Download your audit log before you delete the org: it's erased with the org.

What comes out

The users and what belongs to them need a key with org.users.view, and each list comes a page at a time. The audit log downloads whole, as CSV or JSON, with org.auditLog.export.

WhatWhereWhat you get
Each brand's usersList a brand's usersid (the sub your apps know them by), email and email_verified, username, names, picture, locale, wallets, sign_in_methods, disabled, created_at and last_sign_in_at
Your metadata and accountsRead a userAll of the above, plus metadata (your own JSON) and identities: each email address, wallet and provider account they sign in with, by its provider and subject, with its handle and details where the provider gives them
Their passkeysList a user's passkeysEach passkey's id, whether it's synced and backed_up, its transports, created_at and last_used_at. Never its public key or its credential id
What they allowed appsWhat a user allowed appsEach app outside the brand's own that they consented to, and the scopes
Your audit logDownload the org's audit logEvery change your plan keeps, on every plan, as CSV or JSON. The dashboard's Audit log page has Download CSV and Download JSON too

To export a brand, page through its users with limit=200 and each page's next_cursor, then read each user for their metadata and accounts. One key makes up to 600 management API requests a minute (management.principal, see rate limits): on a 429, wait the Retry-After it gives, then go on. Keep each user's id with what you import elsewhere, for example in the new system's own metadata, so your apps can match the people they already know.

What doesn't come out

Password hashes

Password hashes are never exported. Your users set a new password, or sign in with an emailed code, at your new provider.

Synq keeps a password only as an Argon2id hash, in the PHC string format ($argon2id$v=19$m=19456,t=2,p=1$<salt>$<hash>: version 0x13, 19 MiB of memory, 2 passes, 1 lane and a 32-byte hash). No route returns a hash, to you or to anyone, so no export holds one. Synq doesn't take another system's hashes either, today, when you move in.

They set it through the new system's own reset: their address comes with them, and email_verified says whether they proved it, so the reset reaches them.

Passkeys

A passkey belongs to one relying party, the host name it was made on (WebAuthn's RP ID): your brand's issuer host, such as https://acme.auth.synq.build, or your custom domain. Its private key never leaves the person's device or password manager, so no service holds it, Synq included. Synq keeps its public key and credential id, and exports neither. A passkey made on a brand's issuer host also works on that host alone, which no other system can serve.

So nobody's passkey moves. People sign in another way on the new system, then make a new passkey there.

Sessions, tokens and keys

Sessions, refresh tokens, your apps' secrets and your API keys stay behind. Everyone signs in once on the new system.

Linked accounts

Each account a person signs in with comes out as its provider and its subject, so a new system can match the person again when it sees the same subject:

  • An email address: the subject is the address, lowercase.
  • A Solana wallet: the subject is its address. A wallet signs in the same way anywhere, so people keep theirs on any system that signs in Solana wallets.
  • A provider account (Google, GitHub, Microsoft, Apple, Facebook, X, Discord, Telegram, Matrica, or a provider of your own): the subject is the provider's id for the person. Some providers give each app its own id for the same person, so the subject matches on the new system only when it signs people in through the same app at the provider. By default a brand signs in through Synq's own app at each provider, which you can't take with you; with your own apps at the providers, the subjects came from your apps, and stay theirs wherever you use them.

What your users redo

They sign in withOn the new system
An emailed code or linkNothing: their address comes with them
A passwordSet a new password through its reset, or use an emailed code where it offers one
A passkeySign in another way, then make a new passkey
A Solana walletNothing, where the new system signs in Solana wallets
An account at a providerSign in with it again, unless the new system signs in through the same app at the provider (above)

Someone whose only way in is a passkey has nothing else to sign in with on the new system, since a passkey sign-up needs no email address: their sign_in_methods say passkey alone. Ask them to add an address or another way in before you move.

When you're done

To erase one brand's users and apps and keep the org, delete that brand instead: its sign-in stops at once, and its users and apps are erased 30 days later. The org's default brand first hands its place to another of its brands, which you name as the org's default_brand_id when you change the org, or in the dashboard's Delete brand dialog. The org's only brand goes only with the org.

Download your audit log before you delete the org: the Delete organization dialog offers Download CSV and Download JSON first, since the log is erased with the org. A download holds as much as your plan keeps (see the audit log).

Delete your org once everything is out. Synq stops serving it at once and deletes its data 30 days later, as the terms and the data processing terms on Synq's website say.

On this page