Privacy policy

Who is responsible for my data?

Sashimi is operated by ATM DEV SL, Calle Cargol 4, nave D, Spain, tax ID B27674522. For your account details, we decide how they are used, so we are the controller. For the CRM data your workspace puts in, your workspace is the controller and Sashimi processes it only on your behalf.

Questions about this policy go to alfonso@mail.atm-dev.com.

What data does Sashimi collect?

Account details, the CRM data of your workspace, the credentials of the accounts you connect, the history of what AI clients and agents did, and what you type into a beta access request form.

• Account details. Your name, email address, password (stored only as a one-way hash), the workspaces you belong to and your role in each. Each sign-in session keeps the IP address and browser it came from.
• Beta access, request form in the Sashimi app (dashboard.sashimicrm.com). Your email address and, if you give them, your name, the AI client you use, how many businesses you sell for, your current CRM and the page you came from. The form also has a hidden field that only bots fill in.
• Beta access, request form on this website. It collects everything the form in the Sashimi app does, plus your company name or website, what you want to do first (free text, up to 1,000 characters) and the campaign tags of the link you followed (its source, medium and campaign name). It also asks you to tick a required consent box: «I agree that Sashimi may use these details to reply to me about the beta.» A request without that tick is refused; the consent is not stored apart from the request itself, whose date records when it was given. Its requests carry a Cloudflare Turnstile check.
• Beta access list. If you are let in, your email address goes on the beta access list, with an optional note.
• Workspace CRM data. Leads, companies, deals, tasks, notes, activities, custom fields, sequences and email templates. This is whatever you, your teammates, your AI client or your agents add, including CSV imports.
• Connected accounts. If you connect Gmail, Sashimi keeps an encrypted token for it and stores the new messages in that mailbox (sender, recipients, subject and body). It links them to matching leads and companies. Keys for a data provider or an AI provider are stored encrypted.
• AI connections. Personal connector links are stored as a hash, plus a short prefix so you can recognise each one in the list. Connections made through OAuth keep the app name and their expiry.
• The MCP activity log. MCP is the open standard your AI client uses to connect to Sashimi. Every tool call from an AI client, every action by a Sashimi agent and every change made in the web app is logged. The log records who, through which connection and app, which tool, which record IDs, the result and the duration. It does not store the values sent or returned.
• Agent history. If your workspace uses Sashimi's agents, it keeps their conversations and a step-by-step record of each run. That record includes the arguments of each tool call and what the tool returned.
• Research results. Research recipes keep the public facts and sources they found about a company, a person (a lead) or a market segment.
• IP addresses of personal links. The first time a personal connector link is used from a new IP address, that address is stored and the call shows as a new IP in the activity log. This is how you spot a link used from somewhere unexpected.

What do you use my data for?

To run the service you signed up for: sign you in, show and change your CRM, send the emails you or your sequences send, and keep the workspace secure. We do not sell your data and we do not use it for advertising.

Sashimi's own emails are limited to what the service needs: verifying your email address, inviting people to a workspace, a daily summary of your overdue tasks, stalled deals and sequence emails waiting for review (on by default, and you can turn it off), and confirmations of beta access requests.

Beta access requests are used only to decide who gets in. Each of the two request forms handles them in its own way.

The request form in the Sashimi app (dashboard.sashimicrm.com). The request is emailed to our own mailbox through Resend, and you get a confirmation email. No database record is written. Your IP address is held in memory only, to count requests: up to 3 per IP address every 10 minutes, and 60 in total per hour. This form has no Turnstile check.

The request form on this website. Sashimi's server sends the Turnstile token from the form, and your IP address, to Cloudflare to check that a person sent the request. A request without a valid check is refused, and Cloudflare's error codes are not stored. The same in-memory rate limit applies. In your browser, Turnstile reads technical signals about the browser and device to tell people from bots; it sets no advertising or tracking cookies, and Cloudflare handles that data under its own privacy policy.

Normally, a request from this form becomes a lead in Sashimi's own CRM workspace (we use Sashimi to track beta requests), in our database on Railway. The lead holds your email address and your name. Without a name, it uses the part of your email address before the «@». It also holds a company, matched or created from its web domain or its name (ignoring upper and lower case), your answers as fields on the lead, and the status «Beta requested».

If you ask again, the same lead is updated and no second lead created. Any answer you change is first saved in a note on the lead. The status is not reset, and the confirmation email is sent only the first time.

Until that workspace is set up, a request from this form is emailed to our mailbox instead, as with the form in the Sashimi app, with the extra answers, and you get a confirmation each time.

For beta access requests, Sashimi is the controller, as for account details.

We review beta requests in Sashimi itself, sometimes through Claude (Anthropic) connected to our own workspace. The decision on who gets in is always taken by a person.

Who else processes my data?

A short list of providers, each only for the part of the service that needs it. Several apply only if your workspace turns on the feature that uses them.

• Railway hosts the Sashimi app and its database. Always.
• Resend sends Sashimi's own emails: email verification, workspace invitations, the daily summary (which contains CRM data such as task and deal names) and beta access requests and their confirmations from both request forms. Always.
• Google (Gmail) reads and sends email for a mailbox. Only if you connect Gmail.
• Anthropic runs Sashimi's built-in AI features on Sashimi's account: onboarding suggestions, agents and research. Only when your workspace uses them without its own AI key. Agents are off by default.
• Your workspace's own AI provider (Anthropic or an OpenAI-compatible provider). Only if a workspace admin connects its key. It works under your contract with that provider.
• Apollo searches and enriches prospects. Only if your workspace configures an Apollo key.
• Telnyx is not in use today. It would provide phone numbers and calling only if telephony is switched on.
• Cloudflare serves this public website, once the site is deployed on it.
• Cloudflare (Turnstile) checks that a person sent the request form on this website. Only when that form is used.

Your AI client (Claude, ChatGPT, Cursor or another MCP client) is your own provider, not ours. What it sees is what the Sashimi tools it calls return. Its handling of that data is governed by its own terms. The same goes for any webhook address your workspace sets up: Sashimi sends the event data to the address you chose.

The full list, with when each one applies, is on the security page.

How long do you keep my data?

CRM data stays for as long as your workspace keeps it. Some temporary data has a fixed limit. Other stored data has no fixed limit yet. Both lists are below.

With a fixed limit:

• Deleted records wait in the trash for 30 days so they can be restored. After that they are purged the next time the trash is opened. An admin can empty the trash at any time.
• People research results are cached for 30 days. They are also removed when the lead is permanently deleted.
• Market segment research results are cached for 30 days.
• Saved results of repeated AI writes (so a retried call is not done twice) are kept for 24 hours.
• Change events used to trigger agents are deleted after 7 days.
• Agent jobs are deleted 30 days after they finish.
• Webhook delivery records are deleted after 30 days.
• The MCP activity log is deleted after 180 days. That includes the entries that record a new IP address for a personal link.

With no fixed limit yet:

• Company research results. Older results are no longer used, but they are not deleted.
• Agent conversations and run history, including tool arguments and results. They are deleted when the agent is deleted.
• Sign-in session records, with their IP address and browser.
• IP addresses of personal connector links. They are deleted when the link is deleted, not when it is revoked.
• Email synced from Gmail. It stays after you disconnect Gmail.
• Beta access requests in our mailbox, the beta access list, and beta request leads in Sashimi's own CRM workspace.

Beta access requests, in our mailbox and as leads in our own workspace, are deleted 12 months after the last request if you were not let in. Everything else in this list is deleted when you delete it, or within 30 days of your workspace or account being closed.

The database is backed up on Railway every day (each copy kept 6 days) and every week (each copy kept one month), so deleted data leaves the backups within a month.

Can I export my data?

Yes. The web app exports leads, companies and deals as CSV files. Your AI client can also export them through the export_records tool, up to 500 rows per call.

How do I delete my data?

Delete leads, companies, deals or tasks from the web app or your AI client (deleting through an AI client needs an admin). Deleted records go to the trash for 30 days, or are removed at once if an admin empties it. To delete a whole workspace or your account, write to alfonso@mail.atm-dev.com.

Permanently deleting a lead also removes its cached people research. Disconnecting Gmail, a data provider or an AI provider stops Sashimi from using that account.

What are my rights under the GDPR?

If you are in the EU or the UK, you can ask to access, correct, delete, restrict or port your personal data, and object to how it is used. Write to alfonso@mail.atm-dev.com. We answer within one month. You can also complain to your local data protection authority.

If your data sits in another customer's workspace (for example, you are one of their leads), that customer is the controller. Contact them first. We will help them answer you.

Does Sashimi use cookies?

Only the cookies needed to sign you in and keep you signed in to the app. There are no advertising or analytics cookies. This public website sets no cookies of its own.

The request form on this website loads Cloudflare Turnstile to check that a person is sending it. Turnstile sets no advertising or tracking cookies; it only reads technical signals about your browser and device to tell people from bots.

How will I know if this policy changes?

We update the date at the top of this page with every change. Material changes are announced by email to account holders at least 30 days before they take effect.

See also the terms of service, the security page and the home page.