Skip to content

Contact us

One mailbox, and a plain account of what goes where

We have exactly one address we know receives mail, so this page is short. The short part is not a brush-off: saying what to write and what to include gets further than listing five inboxes.

Write to

Every category currently lands in the same mailbox. That is the state of things, not a placeholder — better one address that works than a row of them that do not exist yet.

Categories

What to send, and what to bring

Giving us the whole context in the first email beats three rounds of clarification. The “bring” line under each category is not a formality — it is what we actually need to act.

Data, deletion and export

What we hold about you, deleting an account and its data, or getting a copy of it. What deletion actually removes and what it leaves behind is set out item by item in the privacy policy.

Bring

The email address on the account, and specifically what you want removed or exported.

Terms, compliance and invoicing details

Questions about the terms, paperwork your organisation needs, or the company details for an invoice. We have no data processing agreement available to sign and hold no security certification — the privacy policy says so, and we are not going to say otherwise here.

Bring

The section number you want confirmed, or the specific question your legal team has asked.

Billing and subscriptions

Changing a payment method, retrieving an invoice and cancelling are all things you can do yourself in Stripe's billing portal without writing to anyone. Come to us for what Stripe cannot settle — a charge that does not line up with the usage records, say.

Bring

The team name, plus the date and amount of the charge in question.

Failed runs and faults

A stage that will not move, a master that will not render, a share link that will not open. We look at the stage records and the usage records for that run — every external call leaves an entry, including the ones that failed.

Bring

The project title or the share link, and roughly when it ran.

Three things up front

Read these before you write

01

We do not promise a response time

You will not find “within one business day” here, because there is no SLA and nobody on a rota — the availability section of the terms is making the same point. Putting the full context in the first email will move things along faster than a follow-up would.

02

The thumbs in the product do not reach a person

Each generated shot in the workbench has a thumbs up and a thumbs down, and a thumbs down offers four preset reasons. That control feeds model scoring — it is the satisfaction signal, weighted 20%, and it decides which vendor gets a shot like that one next time. It is not a ticket, and nobody reads it and writes back. For that, use email.

03

There is no contact form on this page

A form needs a backend to receive it, somewhere to store it, and a person answerable for replying. We have none of the three. A form that nobody reads is worse than a bare address, because it looks like a commitment.

The contracting party

Who you are writing to

OCTOPUS CORE PTY LTD

ACN
696 931 236
ABN
28 696 931 236

The registered office is not printed on this page; the address for service of legal notices can be looked up from the ACN or the ABN on the ASIC public register.

If the question is specific, run an episode first

Commercial scope, data handling, disclosure rules — a question attached to one real run gets a far more specific answer than the same question asked in the abstract. Drafts are unlimited and cost no credits.