Skip to main content
Start here: nothing changes for your application unless you choose it.For any field type you protect, your own API keys receive the real value by default, so the text your app reads back is identical to what it reads today. Request and response shapes do not change. There is no new SDK call to make, and no code to write.Two settings do change what your app receives, and both are yours to pick: Do not store it, and Protect from everyone. Nothing else alters your reads.

What this feature is

Synap reads the content you send. Some of it is sensitive: an Aadhaar number in a support transcript, a card number a customer read out on a call, an API key somebody pasted into a chat. Two things are true about that content at once. You need it, because answering the customer’s next question depends on remembering the conversation. And keeping it is a liability, because it sits in a memory store, gets embedded for search, and passes through a language model on the way in. Sensitive data protection separates those two. Synap finds the value, replaces it with a stable placeholder everywhere it would come to rest, and hands the real value back to your application when it asks. Your product behaves the same. What we hold on disk does not contain the value. You decide which kinds of value get that treatment. The decision is made once, in the dashboard, per category.

The three things that can be true

These are separate, and mixing them up is the easiest way to misread the feature.
1

Watching

Synap runs its detection over every document and records what it found: which field types, how many times, across how many of your users. Nothing is changed, nothing is replaced, and your memories are byte for byte what they would have been.This is what every account gets before anyone configures anything. It is not a degraded state. It is how you find out what is actually in your traffic before you make a decision about it.
2

The floor

A short list of field types is never kept, whatever your settings say. Card numbers, card security codes, card PINs, passwords, API keys and other secret codes, private keys, and raw biometric data.There is no setting for these. They are not one of your eleven choices, and no preset, exception, or support request turns them into one.
3

Your policy

Once you have set a policy and approved it, Synap applies it to everything ingested from that point on. Each category gets one choice, and that choice decides what the model sees, what we store, what your application receives, and what our staff can see.A policy is inert until a person approves it. Saving a draft changes nothing.

The eleven categories

Field types are grouped into eleven categories so you configure eleven things rather than a long list of individual formats. The grouping is for navigation. Nothing about detection depends on it.
Two categories have no shipped detection yet: Health, and Origin and Beliefs.You can set a policy on them, and the setting is stored and applied. But Synap ships no detector for health conditions or origin and belief data, so under a policy alone nothing in those categories is found and nothing is replaced. Names are found by a separate service: while it is unavailable, names are not found.If you need protection in one of these categories today, describe your own field type for it. See Your own field types.
You can add field types Synap does not ship, put them in whichever category you think they belong to, and move them later. An asset tag, a policy number, an order id: you know your own data better than we do.

The six settings

Each category gets one choice. Three of them are offered on the row itself; the other three sit behind an advanced link for the minority who need them. The three offered up front are Not sensitive (“keep it”), Protect at rest (“protect it”), and Do not store it. Protect at rest is the one most clients want: the value is not in our store, and your application still reads the real thing. Logs and telemetry are deliberately not a column in that table. They always receive the most restricted treatment your chosen setting allows, and there is no setting for them, because nobody has ever wanted a real value in a log line.
Your own vault is not available yet. The setting exists and a policy can carry it, but the outbound path to a customer-operated endpoint is a separate track that starts when a client asks for it. Until then, treat it as equivalent to Protect fully and talk to us before selecting it.

What a placeholder is

A placeholder, which the product calls an alias, looks like this:
The same value always becomes the same alias, so deduplication, corrections, and search keep working on a consistent string. Search for the real value and Synap matches the memory that stores its alias. See Aliases for what your application receives and why search still works.

Presets

Rather than starting from eleven empty dropdowns, you can apply one of three starting points, then adjust. A preset is a starting point, not an answer. It lands as a draft and still needs approving.

The floor

Seven field types are never stored, for any account, in any industry, whatever the settings say:
  • Full card number
  • Card security code
  • Card PIN
  • Passwords
  • API keys and other secret codes
  • Private keys
  • Raw biometric data
No setting on your account changes this. It is not a category-level rule, so it does not drag the rest of the category with it: a bank account number sits in Payment Info and plenty of products legitimately keep one. When one of these appears, the value is replaced with a short description of what was taken, such as [a card number was given and not kept], and the record that it happened is kept. Nothing is stored that the value could be recovered from.

What happens to the memory around it

If a value never reaches the model, the model will sometimes still write a memory about the empty space. “Their card number is a card number” answers no question, takes up room, and reads as though we hold the number somewhere. The rule Synap applies is simple: keep a memory if it records something happening, drop it only if it does nothing but assert a value we chose not to keep. “Requested an address change on 12 August” survives, because the event is the useful part and the address was only one attribute of it. Suppressed memories are counted and shown on your dashboard with the reason, alongside a sample of what was kept, so a working feature does not look like data loss.

What detection can and cannot do

Synap does not claim perfect detection, and the strength of the promise differs by field type. This matters more than a single accuracy number would. Measured precision and recall are published per field type rather than claimed as one number. See Security and Trust for the current figures and the size of the corpus they were measured on.

Known limits, stated up front

  • Name detection depends on a separate service. Do not plan around names being found if that service is unavailable.
  • Health, origin and belief data are not detected. The categories exist and accept a setting; no field type ships in them.
  • Biometric detection is text only. Synap finds an encoded biometric template when it appears in text next to a word that labels it, such as “fingerprint template” or “iris minutiae”. An unlabelled binary attachment is not text and is not covered.
  • Images, audio, and scanned documents are not covered. Detection runs over text.
  • Voice transcripts are covered for four field types. Numbers dictated as words (“nine eight seven six five…”) are reconstructed for Aadhaar, card number, phone, and PIN code, including Hindi digits and corrections mid-number. Other field types are not recovered from speech.
  • The shipped identifier list is largely India-first. Aadhaar, PAN, GSTIN, IFSC, UPI, voter ID, and vehicle registration are Indian formats. Email, phone, card number, IP and MAC address, passwords, API keys, and private keys are not region-specific. Phone number detection assumes an Indian number by default.
  • Data ingested before you turned this on is unaffected. It stays exactly as it is, in plain text. Policy applies forward only.

Turning it on

Everything is configured on the Sensitive data page in the dashboard. See Sensitive data and data controls for the step-by-step, including the test box that shows you what would happen to sample text before you commit to anything.

Finding the page

Open the Dashboard and go to Sensitive data. The page opens on What we found, which lists what Synap has actually detected in your traffic over the last 30 days. It is deliberately not an empty configuration form: the point is to decide about data you really have. At the top of the page, Applies to controls the scope of everything below it. The default is All instances (whole account). Pick a single instance to give that one instance a policy that overrides the account setting. Most teams set one policy for the whole account and never touch this.

Setting a policy

1

Start from a preset, or don't

If you have not configured anything yet, the page offers three starting points under Clients like you usually begin here: Minimal, Standard, and Regulated. One click sets every category. Standard is the right answer for most products.A preset lands as a draft. It is not live until you approve it, and you can change any row afterwards.
2

Work down the findings list

Each row is a field type Synap found, with how many times it appeared and across how many of your users. Each row offers three choices:The advanced link on a row opens the other three settings: hide from the model only, protect from everyone including your own app, and keep it in your own vault. Most teams never open it.Rows on the floor list, such as card numbers and passwords, show a never stored badge and offer no choice. See the floor.
3

Read the before and after

Picking a different choice renders a real before-and-after for that row, using a sample memory sentence, plus one line saying whether your application is affected. That line is the one to read. Two settings affect your app; the rest do not.
4

Review and apply

Nothing takes effect one row at a time. Changes collect in a bar at the bottom of the page showing how many are not applied yet. Discard throws them away. Review and apply saves them and approves them together.Approving records who approved it and when, and bumps the version. The previous version stays readable under the policy history, so you can always see what was in force when a given memory was created.
Below the findings list there is a line reading “We also looked for N other kinds of sensitive data and did not find any.” Expand it to see the full list of what was searched for. It is there so you can tell “we checked and found nothing” apart from “nobody ever looked”.

Suggestions

Above the findings list, Synap surfaces field types appearing in your traffic that you have not decided about yet. At most three are shown as prominent; the rest sit under show more, and the total is stated so you can see the list is complete. Nothing is hidden by a score; the score only decides the order. Each suggestion offers protect, ignore permanently, or not now. Choosing protect records the decision, it does not switch protection on by itself. You still set the category and approve the policy.

The test box

The Try it tab is the fastest way to answer “what would this actually do to my data”. Paste sample text, click See what happens, and the page lists everything Synap found: the field type, where in the text it sits, and what would happen to it at each destination under your current settings. Findings on the floor are badged never stored, and your own field types are badged as yours. Two things about this box are worth knowing:
  • Nothing you paste is stored. Not the text, not the values, not a counter, not a log line, not an audit row.
  • The result carries positions and field type names, never the matched text itself. You can safely screenshot or paste a result into a ticket.
The box accepts up to 20,000 characters at a time. If you have not approved a policy yet, the result is computed against your draft and says so, so you can check a change before committing to it.

Seeing what is protected

The Protected values tab answers “is anything actually protected right now, and how much”. It shows, per field type, how many distinct values are held, how many times they have appeared, what your application receives for that field type, and what the model sees. It shows no values and no placeholders, deliberately. A page that exists to demonstrate values are not readable would disprove itself by displaying them. The same tab shows what the floor removed and what was suppressed by the memory drop rule, alongside a sample of the memories that were kept. Read the kept sample: a card that shows only what was thrown away makes a working feature look like data loss.

Activity and evidence

The Activity tab is the audit trail for everything that happened to your sensitive data. Your own people and Synap staff appear in the same list, with a column saying which is which, so you find out about our access on your own dashboard rather than from us. Each entry carries the time, the action, the field type, who did it, the reason they gave, and the policy version in force. It never carries the value. Entries are kept for one year. Export downloads the trail as a CSV file an auditor can open. The policy history, on the same page, shows every version, who approved it, and when.
A reason typed into a reveal is screened before it is stored, and a reveal whose reason contains what looks like a sensitive value is refused along with the reason. This is deliberate: refusing only the reason would teach people to retype it without the number and get the value anyway.

Your own field types

The Your own field types tab lets you describe a field type Synap does not ship: an asset tag, a policy number, an order id. Give it a name, pick the category it belongs in, and paste two or three real examples. No release and no ticket. See Your own field types for how to pick the category and write good examples.

Restricting an API key

Your policy decides what any caller can receive. On top of that, each of your API keys carries a grant that can only ever narrow what the policy already allows: Use this to give a support tool or an internal dashboard a key that reads memories without reading values. A grant cannot widen access, so there is no way to accidentally hand a key more than your policy allows: to widen, change the policy. A grant change takes up to about a minute to take effect on live traffic, because the credential is cached.

What does not appear on the dashboard page

  • Erasing a person is not a self-service action. See Erasing a person.
  • Data ingested before you approved a policy is untouched and stays in plain text. Policy applies forward only, and every record carries the policy version that was in force so you can tell which is which.

FAQ

For the claims a security review needs in one place, read Security and Trust.

From your engineering team

No, unless you choose it.For any field type you protect, your own API keys receive the real value by default, so the text your application reads back is identical to what it reads today. Request and response shapes do not change.Only two settings change what you get back, and both are yours to pick: marking a field type Do not store it, and restricting one of your own API keys. A third, Protect from everyone, exists behind the advanced link and does exactly what its name says, including to you.
No. There is no new call to make, no parameter to pass, and no version to pin for this. Everything is configured in the Dashboard.If you deliberately restrict a key so it receives placeholders, your code has to be ready to see a placeholder in the text. See Aliases.
Placeholders are stable: the same value always becomes the same placeholder, in the same form, however it was spelled. So deduplication still merges duplicates, corrections still supersede what they correct, and entity identity in the graph still resolves to one thing rather than two.Every change to this feature is held to the same benchmark gate Synap uses for retrieval quality, with a hard limit on how far any individual benchmark may move.
Ingestion picks up a detection pass, and ingestion is asynchronous, so it does not sit in your request path.Reads pick up a small step to put real values back before the response is assembled, which is short next to a fetch that is already dominated by retrieval. If a fetch returns no placeholders at all, which is the case for every account that has not configured anything, that step is skipped entirely.
Yes, and this is a hard requirement in the design rather than an optimisation.Your query goes through the same detection step your content did. A search for 9876543210 is turned into the same placeholder that was stored, so it matches the memory holding it. A value Synap has never seen leaves the query untouched, which is correct: no memory holds that value either.
They stay exactly as they are, in plain text. Policy applies forward only, from the moment you approve it.Every record carries the policy version that was in force when it was created, so you can always tell which memories were written under which rules. Re-processing older memories under a new policy is possible and is a job we run for you on request; it costs real time and money, so it is not automatic.
Yes. Set the categories back and approve, and new memories stop being protected.Memories already protected stay that way, and stay readable: your application keeps receiving the real values for them, because the placeholders still resolve.
We do not promise perfect detection, and Security and Trust states exactly what we do and do not promise.What you get instead of a promise is visibility. Watch mode runs for every account from day one and shows you what is being found in your own traffic, by field type, with counts. A gap is a number you can see rather than something you find out about later. The publication of measured precision and recall per field type is part of the same idea.
For the settings most people pick, it costs you nothing visible. A false positive is protected on the way in and revealed straight back to you on the way out, so the text your application receives is unchanged.It shows up as a count on your dashboard. If a field type is producing noise, move it down a level or set it to Keep it.
Describe it on the Your own field types tab with a name, a category, and a few real examples. No deploy and no ticket.One caveat that matters: a field type you describe is currently detected in the Try it test box only, and is not yet applied to live ingestion. See Your own field types for the full picture, and contact us if you need a custom format protected in production now.
Yes. The Try it tab takes sample text and shows exactly what would be detected and what your current settings would do with it at each destination.Nothing you paste there is stored: not the text, not the values, not a counter, not a log line. The result carries positions and field type names rather than the matched text, so it is safe to paste into a ticket.
Yes. Issue that tool a restricted API key. A key’s grant can only ever narrow what your policy already allows, never widen it, so there is no way to accidentally hand a key more access than you intended. See restricting an API key.
It depends on whether you have a policy in force.In watch mode, a detection failure is counted and the document proceeds. Watch mode changes nothing about your data, so a failure there must not be able to break your ingestion.Under an approved policy, a document that cannot be protected is refused rather than stored. Continuing anyway would send a value to a model you told us to keep it from, which is the one outcome this feature exists to prevent.

Protected values are held in one place, encrypted under a key that belongs to your account alone. The plain value is not written to the memory store, the vector store, the graph, or our logs.This applies to field types you have protected. A field type you set to Keep it, and anything ingested before you approved a policy, is ordinary content.
The application can, using a master secret held in the deployment environment.Synap staff cannot read a protected value without a deliberate reveal action, which requires a named person, a written reason, and writes an audit entry that you can read on your own dashboard the same day. There is no path that shows a value to our staff without leaving that record, and an impersonated session cannot reveal at all.The reason field is itself screened, and a reveal whose reason contains what looks like a sensitive value is refused along with the reason.We state the limits of this honestly: see what we do not protect against.
Erasure deletes the person’s protected values and memory records from Synap’s live systems, along with what was built from them for search. Backups taken before it still hold them until those backups expire, and the documents and conversations you sent are not touched unless you ask.Removing an entire account makes every protected value it owns unreadable in the live systems.One thing is deliberately kept and is named in the preview before anything runs: values shared with other people, because deleting those would break other people’s memories. See Erasing a person.
Yes. During ingestion, content is sent to the model provider that performs extraction.Under a policy, protected values reach that provider as placeholders rather than real values. Floor field types never reach it at all.Whether a given provider retains or trains on data sent to it is a contractual question and is answered in our Data Processing Agreement, not here. Request it from [email protected].
Protected values are encrypted individually, under a key held per account, on top of the volume-level encryption described in Security and Trust.Memory text itself is not field-encrypted, and that is a deliberate choice rather than an omission: encrypting it would make semantic search impossible, and semantic search is the product. Protection for memory content comes from the sensitive values not being in it.
We publish it per field type rather than claiming a single number, and we do not sell two different mechanisms at the same confidence.Field types with a check digit, such as Aadhaar, GSTIN, and card numbers, are close to certain: a value that fails its checksum is rejected rather than guessed at. Field types found by shape are strong but weaker than that.Names are found statistically by a separate service, with both misses and false alarms. While that service is unavailable, names are not found. Street addresses are found by shape: a house number followed by a street word such as Road, Street or Nagar. An address written another way can be missed.The current measured figures for both, and the size of the corpora they were measured on, are in Security and Trust.
Yes, append only, kept for one year.Each entry records the field type, the action taken, the placeholder involved, the scope, the time, who acted and whether they were your person or ours, the reason they gave, and the policy version in force. It never records the value, and never records the text around it.You read it on your own Activity tab and export it as a CSV file. Your policy history shows every version, who approved it, and when.
Stated plainly, because a reviewer will find these anyway:
  • Name detection depends on a separate service. Do not plan around names being protected if that service is unavailable.
  • Health, origin and belief data are not detected. Those categories accept a setting; no field type ships in them.
  • Biometric detection is text only, and only for an encoded template that appears next to a word labelling it. An unlabelled binary attachment is not covered.
  • Images, audio, and scanned documents are not covered.
  • Data stored before this shipped is plain text and stays that way.
  • We do not protect against an attacker who holds our application environment and our database at the same time.
The full list is on Security and Trust.

Next steps

Aliases

What your application receives, and why search still works.

Your own field types

Describe a field type Synap does not ship, and pick its category.

Erasing a person

What erasing someone deletes, and what it leaves.

Security and Trust

Everything an enterprise security review asks about, in one place.