ArmfulCounted to the bunch. Open the app

Security

Automated programs can now try thousands of sign-ins, messages, and sign-ups an hour, work that once took a room full of people. Armful is built for that. This page says what protects your account and the site, what it does not promise, and how to report a problem.

Signing in

  • No passwords. There is nothing to guess, and lists of passwords leaked from other sites are no use here.
  • Sign-in links work once, for 15 minutes, and only in the browser that asked for them. A link someone else sends you signs you in to nothing. The page a link opens names the account and has one button, so an email scanner that follows links cannot use one up.
  • Links and sessions are stored only as one-way hashes, so even a copy of the database signs no one in.
  • Settings lists every device signed in to your account and signs out the others with one button.

Against automated traffic

  • Cloudflare filters the network in front of the site.
  • Before a sign-in link is sent, and before the assistant or a person gets a message from someone who is not signed in, a check from Cloudflare tells people from programs. Most people never see it.
  • Sign-in links, assistant questions, and support messages are limited per email address, per network, and per account.
  • The whole site has daily limits on emails sent and assistant answers, so a flood of automated requests cannot run up costs that end up in the price. New sign-ups and support emails each have their own share, so a flood of either never stops florists who already have an account from signing in. If a limit is reached, that one feature pauses until the next day; the app, your events, and your account keep working.

Your data

  • Without an account, your events never leave your device.
  • With one, the copy in your account can be read only with your session. One account cannot read or change another's.
  • Every request that changes anything must come from Armful's own pages; a page on another site cannot act for you.
  • The pages run only Armful's own scripts, plus Cloudflare's check when it is needed. Anything you type is shown as text, never run.
  • The help assistant can look up whether you are signed in and syncing, and open a ticket. It cannot change your account or see your events.

How it is tested

In November 2026 four automated testers attacked a copy of Armful, each with one goal: take over an account, run up the bill, get past the check, or lock florists out. Everything they found was fixed, and each finding is now a test that runs on every change. Before any change can go live, a security suite attacks the real server and a real database: requests from other sites, forged, expired, and signed-out sessions, one account reaching for another's copy, injected code, oversized and malformed requests, the limits above, and 2,000 generated malformed requests that must not cause a single server error. The pages are checked in Chrome's engine on every change, and in Firefox and Safari's engines every day the code changes.

What this page does not promise

No software is free of flaws, and this page is not a promise that Armful cannot be broken. It describes what is in place and what is tested, so you can judge for yourself.

Reporting a problem

If you find a security problem, write to the address in security.txt, or use Write to a person in the app and choose “Something is broken”. Say what you found and how to see it. Please test only with your own account, and do not try to overload the site. A person will reply.

Last updated November 16, 2026. Questions: use Write to a person in the app, or reply to any email from Armful.