Anonyflow

Anonymizes sensitive PII before it hits your logs or database and recovers original values using private keys when authorized access is required.

Try Anonyflow in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Anonyflow integration

    • Describe the outcome and Ceven picks the right Anonyflow calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Anonyflow data, across all 5 of its actions.
  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Anonyflow access.
    • Per user and per environment credentials instead of shared keys.
  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Anonyflow, when, and on whose behalf.
    • The agent pauses and asks when Anonyflow is unclear instead of plowing ahead.
  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Anonyflow.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Anonyflow action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Anonyflow, and when to use it.

Anonymize Value
Use this when you need to conceal sensitive text or arrays of strings before storage or transmission to prevent PII leaks.
Deanonymize Packet
Use this to recover specific fields from a JSON data packet using your private key after receiving anonymized data.
Deanonymize Value
Use this when you need to recover the original plaintext values from one or more encrypted anonymized strings.
Test Connection
Use this to verify that the Anonyflow service is reachable and operational before starting a large batch job.
Mask User Email
Pass a raw email address to the anonymizer to create a secure token for use in public logs.
Anonymize Batch
Process a list of multiple sensitive values in a single call to reduce API overhead during migrations.
Recover Identity
Use the private key to turn an anonymized token back into the original identity for authorized users.
Validate Packet
Check if a data packet is correctly anonymized before attempting to store it in a low security zone.
Rotate Encryption Key
Trigger a key rotation event to ensure long term security of the anonymized data set.
Fetch Public Key
Pull the current public key used for the anonymization process to share with external data producers.
Audit Anonymization
Pull logs of when data was anonymized to prove compliance with data privacy regulations.
Purge Anonymized Data
Use this to permanently remove the mapping for specific tokens to satisfy right to be forgotten requests.

12 actions · scroll to see them all

Frequently asked questions

Anonyflow uses a split key architecture where the public key is used for the anonymization process and the private key is required for any deanonymization. Ceven does not store your private keys in plaintext. When you configure the integration, you provide the keys via an encrypted vault. The agent only accesses the private key when a specific deanonymize action is triggered by an authorized user. This ensures that even if a workflow is compromised, the attacker cannot recover the original identity values without the separate private key. You maintain full control over key rotation and access levels within your Anonyflow dashboard.
Yes, Anonyflow is designed specifically for compliance with HIPAA, GDPR, and CCPA. It achieves this by ensuring that personally identifiable information is never stored in a readable format within the target system. By using the anonymize value action, Ceven ensures that the data leaving your secure environment is already encrypted. This removes the target system from the scope of many privacy audits because it never possesses the means to decrypt the data. You can set up workflows that automatically scrub patient names and IDs before they are sent to any third party analytics tool or AI model.
You can process large datasets, but you must be aware of the API rate limits associated with your Anonyflow tier. The Free and Basic tiers have strict requests per minute limits that can cause workflows to fail if you attempt to loop through thousands of rows in real time. For large scale migrations, Ceven implements a queuing system that respects these rate limits by batching requests and inserting delays between calls. If you are on an Enterprise plan, these limits are significantly higher, allowing for near instant processing of millions of records through the anonymize batch action.
Because Anonyflow relies on strong encryption for its privacy guarantees, losing your private key means that any data anonymized with the corresponding public key is permanently unrecoverable. There is no back door or password reset for the encryption keys themselves. This is a critical security feature that prevents the service provider from accessing your data. We strongly recommend that you store a backup of your private key in a secure offline location or a corporate secret manager. Ceven cannot recover this key for you as it is never stored in a recoverable format on our servers.
The anonymization process replaces the original plaintext with an encrypted token. This means the resulting string will be longer than the original value and will contain a different set of characters. If your downstream database has strict character limits or specific format validations for fields like phone numbers or zip codes, you may encounter errors. We recommend updating your database schema to allow for longer variable length strings in any column that will store Anonyflow tokens. The deanonymize action restores the original format exactly as it was before the masking took place.
Yes, the deanonymize packet tool allows you to specify which keys within a JSON object should be restored to plaintext. You do not have to decrypt the entire object to get one piece of information. This follows the principle of least privilege, ensuring that the user only sees the specific data they need for their task. For example, a support agent might only need to recover a customer email to send a manual notification while keeping the customer address and phone number anonymized within the same record.
The Test Connection tool sends a lightweight heartbeat request to the Anonyflow API endpoints. It checks for valid authentication and confirms that the service is responding within acceptable latency thresholds. This is particularly useful for complex workflows that trigger on a schedule. By placing a Test Connection step at the start of your workflow, the agent can send an alert to your team if the privacy service is down before it attempts to process sensitive data. This prevents the workflow from failing halfway through a critical data sync operation.
Yes, Ceven can integrate Anonyflow into real time streaming pipelines. As data events fire from your source system, the agent can intercept the payload and run the anonymize value action before pushing the data to its final destination. This ensures that PII is masked in flight. However, keep in mind that adding an API call to every single event introduces a small amount of latency. For ultra high volume streams, we recommend using the batch anonymization features to group events together and reduce the total number of network requests sent to the Anonyflow servers.

Alternatives to Anonyflow

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Privitar logoPrivitarImmuta logoImmutaTonic logoTonic

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Anonyflow and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free