FAQ

In the region chosen when the account was created: the UK, Ireland or Germany. Data does not leave it, backups included.

Moving an existing account needs a planned window, so it is not self-serve. Ask and we will arrange it.

Up to 250, and a 90-stop run returns in about eleven seconds. Beyond 250 the honest answer is that you are usually looking at two runs rather than one, and the planner will suggest the split.

That is being built now. Until it lands, retention is a single account-wide setting, so an account spanning jurisdictions with different rules should set it to the shortest and keep anything longer outside Corvid.

We would rather say that plainly than let you assume otherwise.

Eighteen months from the release of its successor, and we have never shortened that window. v1 therefore runs until March next year at the earliest.

A compatibility mode lets you move endpoint by endpoint rather than all at once.

Sheets, signatures and photographs are held on the phone and upload when there is signal, with the waiting count shown on screen so nobody has to take it on trust.

Nothing is lost, and nothing needs typing in again.

Post here and you will get a first reply within the hour, at any time of day.

Anything happening during a live on-sale or on a door should go to the number in your account handbook, which reaches somebody directly.

The door list is held on the device, so scanning carries on and admissions are recorded locally. They sync when the connection returns, and any ticket scanned twice while offline is flagged for you rather than quietly accepted.

Three working days after the event, with the fee breakdown itemised per show rather than rolled into a monthly total.

For a run of nights, each night settles separately, so a week-long run does not wait for the last performance.

Yes. Nothing is stored on the device that can move money on its own, and you can freeze every card from any browser by signing in to Halden Online.

If you cannot get to a browser, the 24-hour number in your welcome pack freezes everything in about a minute.

Because a first payment to a new payee is where almost all fraud happens. The extra check takes a couple of seconds and only ever applies once per payee.

Payments to someone you have paid before do not ask again.

Most payments arrive within seconds, but a first payment to a new payee can be held for up to two hours while it is checked, and payments made after 3.30pm on a Friday to a non-participating bank may not land until Monday.

The payment screen shows which of these applies. If it has been longer than that, call us and we will trace it.

Yes, on up to three devices, each registered separately with its own Face ID or passcode.

Registering a fourth signs out the one you have used least, and you will get a notification saying which.

The current and previous versions of Chrome, Safari, Firefox and Edge. Older versions still work but will show a notice, because we cannot promise the security behaviour we need on a browser that has stopped receiving updates.

Fifteen minutes without activity, and typing counts as activity. It is deliberately short because people bank from shared and public machines.

If a session does end while you are filling in a payment, what you typed is kept and returned to you when you sign back in.

Post here and you will get a first reply within the hour, at any time of day.

Anything affecting live customers should go to the number in your account handbook, which reaches somebody directly.

Yes, up to a cut-off you set per class, which is usually somewhere between two and twenty-four hours. After the cut-off they see your studio's own wording rather than a generic refusal.

Two working days after the class, not after the booking. Holding it until the class has happened is what makes refunds and cancellations simple for everybody.

Post here and you will get a first reply within the hour, at any time of day.

Anything affecting live payments should go to the number in your account handbook, which reaches somebody directly.

Only at the lightest level, provided card details go straight from your customer's browser to us and never touch your servers. That is what the hosted fields are for.

The moment a card number passes through your own systems the obligation changes considerably, which is why we will not store them for you.

No, and no payments API should tell you otherwise. Delivery is at-least-once, so key on the event id and treat a repeat as a no-op.

Every attempt is kept for thirty days and can be replayed, and a replay reuses the original event id.

Whoever you invite, at one of three levels: full access, read-only, and a finance view that shows totals and exports but not individual customers.

Every sign-in and every export is recorded, and you can see the log yourself rather than having to ask us for it.

Anything that speaks ASCOM through a bridge, plus native support for the current Sky-Watcher, iOptron and Celestron mounts.

If yours is not listed, tell us the model. Most additions take a fortnight and we will say so if yours will not.

Yes. Sequences hold the Mac awake, resume where they stopped if something interrupts them, and park the mount safely at the end or if cloud cover crosses a threshold you set.

Yes, which matters because dark sites rarely have signal. The catalogue and your plate-solving data are held locally. Only the weather forecast needs a connection, and Pallas says how old the last one is rather than showing you a stale sky.