Skip to content
Help

Custody, safety and what is public

What Memoline can and cannot do with your money, and what is written on Arc for anyone to read.

Memoline never holds your money or your keys

Your wallet signs every payment. Payouts go from your wallet to the people you pay through Arc’s own Memo contract, except a payout to one-time addresses: there each payment goes, through the same contract, to a fresh one-time address that only its payee’s keys can move. Payments to your links go from the payer’s wallet to yours. Memoline has no key that can move your money, and no contract of its own that holds it.

What is public

Anything on Arc is public and permanent: the addresses, the amounts, and the reference you type, except in a payout to one-time addresses, where the reference stays in your books and is not written on Arc. Use invoice numbers as references, never names or emails.

What Memoline stores

Your workspace and its settings; its members, invites and changes waiting for a second person; the payout files you upload and the ledger built from them and from your imports, with Memoline’s fee each payment carries and the exact amount of each line in a stablecoin with 18 decimals; the recurring payout schedules you save (their name, the paying wallet, the currency, the payments, how often they repeat and until when, which payouts were skipped, whether and why each is paused, and who saved or last changed each); the chart of accounts, rules and every booking change; locked month reports; the names and kinds you give addresses; payment links (each split link’s wallets and the names you give them), invoices and recurring invoices, with your customers’ names, email addresses, billing addresses and tax ids (an invoice’s pay page shows its customer’s to anyone with its link); the Circle Gateway transfers you upload; the day’s exchange rates Memoline reads and each quote it gives a payer (the price, the rate, its source and day, and the token amount); notification channels and webhook endpoints; the auditor links you make; the activity log; your plan; and, for each API key, only a fingerprint.

For a payout to one-time addresses, Memoline keeps each payment’s one-time address, its ephemeral public key and view tag, a hash of the payee’s registered keys and a seal only the server can make; never the payee’s keys.

Webhook secrets, notification channel addresses, two-step secrets and accounting software sign-ins are stored encrypted; recovery codes, and each auditor link itself, only as fingerprints. Each opening of an auditor link is logged with a one-way fingerprint of where it came from, never the address itself.

Memoline also keeps, for all of Arc and read from public data once a day: the names agents gave themselves in Arc’s ERC-8004 identity registry, and the three sanctions lists that payouts, and the wallets that pay your links, are screened against: the US Treasury’s sanctions list (OFAC), the UK Sanctions List and the EU’s financial sanctions list. It also keeps every announcement of a payout made through Memoline, and every other one made on Arc testnet since Memoline began reading it, so a payee can find their own.

See recurring payouts, one-time addresses and the terms and privacy page.

Reporting a problem

Found something wrong? Use the contact link at the foot of every page: it writes to the Operator where this site has a private address, and otherwise opens a public question on GitHub. Never post personal details or a security problem in a public issue.