Sub-processors

To run Amino Engine we use a small number of vendors. This page is the list, and it is the list referred to by our Data Processing Addendum — adding or replacing one of these is a change to that agreement.

We keep this short on purpose. The whole reason this platform exists is that peptide brands got dropped by providers they could not replace. So we own the sending infrastructure ourselves, and every vendor below is one we could move off within a day if we had to.

Notice of changes. We will give customers 30 days' notice by email before adding or replacing a sub-processor, and update this page at the same time. Objections go to support@aminoengine.com; the process is in section 5 of the DPA.

Current sub-processors

Railway — application hosting and database

• What it does. Runs the Amino Engine app at app.aminoengine.com and hosts the PostgreSQL database behind it, including automated backups.
• Where. United States.
• What reaches it. Everything stored in the platform: your account details, your contacts and their attributes, consent records, message history and outcomes, shop and website events, and your billing status. This is the primary store.

OVHcloud — mail servers

• What it does. Provides the servers that run our own mail transfer software and physically deliver your email.
• Where. Canada (Beauharnois, Québec). Canada holds an EU adequacy decision for commercial organisations.
• What reaches it. The recipient's email address and the rendered message — subject, body and headers — for each message being delivered, plus the delivery result. It holds the message in transit, not your contact database.

Stripe — payments

• What it does. Takes payment for plans and one-time purchases, hosts the checkout and the billing portal, and stores card details.
• Where. United States, with global processing.
• What reaches it. Your brand's billing information: business name, billing email, payment card, address and tax details, plus what you bought. Card numbers go straight to Stripe and never reach our servers. No subscriber data of any kind is sent to Stripe.

Resend — transactional email to our customers

• What it does. Sends the platform's own email to account holders — sign-in and password reset links, trial reminders, billing notices, and operational alerts.
• Where. United States.
• What reaches it. The account holder's name and email address and the message we are sending them. Your subscribers' mail does not go through Resend — that goes through our own mail servers above.

Google — sign-in

• What it does. Lets you sign in to Amino Engine with a Google account, if you choose to.
• Where. United States, with global processing.
• What reaches it. Only what an OAuth sign-in involves: Google tells us your name, email address and profile picture after you approve it, and knows you signed in to our app. We send Google no contact data, no message content and no analytics. If you sign in with a password instead, Google is not involved at all.

Twilio — text-message delivery

• What it does. Delivers SMS for brands that turn on texting, and receives replies.
• Where. United States.
• What reaches it. The recipient's phone number and each message's text, only for brands that use SMS.

Slack — internal alerts

• What it does. Carries our own internal operational notifications so we notice things — a new signup, a purchase, a fulfilment task, an account crossing a size threshold.
• Where. United States.
• What reaches it. A brand name, a metric, and the account holder's email for account events. No subscriber names or contact data.

Not currently used

• No third-party advertising or product-analytics tracker runs inside the signed-in app.
• No AI or machine-learning vendor receives your contacts or message content.
• No CDN or web application firewall sits in front of the app or the tracking endpoints today. Customers point their own DNS at us and may put their own provider in front of their own website; that is their arrangement, not ours.

Questions, or to object to a change: support@aminoengine.com