Last updated 8 October 2026 · In effect from 7 October 2026
Aisle Handle It is a free beta and this is its first published privacy policy. It describes what the software actually does today, which is the only thing a policy is good for. Where something is not built yet, it says so rather than describing the intention.
Nothing here is a term we are trying to slip past you: if anything in it reads as unclear or unfair, write to hello@aislehandleit.com and say so.
We store the wedding you are planning so you can come back to it. We use your email address to run your account and to tell you things about the service. We do not publish your wedding. It is built so that no other customer can open it: the database checks on every single read and write whether you hold a seat on that wedding, and refuses if you do not. No service can promise it will never be breached, and we do not.
You can print or save everything as a PDF at any time, and you can have it all deleted whenever you ask.
Anyone you invite to your wedding can see all of it, money included. We have no setting that keeps part of it back from them.
Aisle Handle It is operated by For The Plot, a Wyoming corporation, in the United States. For The Plot is the controller of your information — the company responsible for it, and the one that answers your email.
For anything about this policy, or to use any of the rights described below, email hello@aislehandleit.com. We aim to reply within seven days, and we will always respond within any period the law requires.
Your account. Your email address, any name you give us, and a password. You sign in with the email address and password you choose. Your password passes through this website on its way to our authentication provider, the way it has to for any sign-in form — what we do not do is keep it. It is stored only as a one-way hash, which cannot be turned back into your password, and it is never written to our database or our logs in a readable form. A hash is not magic, though: a short or reused password can still be guessed. Please use one you have not used anywhere else.
What you type into the planner. Your budget, vendors, checklist, guest list, seating, appointments, photographs and notes. This is your content. We store it so that we can show it back to you.
If you ask for beta access. Aisle Handle It is invitation only at the moment, so the home page has a form that asks for an email address and nothing else. That address goes to Netlify, who host this site, and into Kit, which is what we use to write back to you. There are two separate things you can agree to there. Asking for access means we reply to you about the beta. Next to it is a separate, unticked box for occasional product news; if you leave it unticked you will not get any, and it makes no difference to your place in the beta. Every product-news email carries an unsubscribe link, and we record which of the two you chose. Asking for access does not create an account and does not start a wedding.
Payment information. There is nothing to pay during the beta, so there is no payment processor and we hold no payment information at all. If that changes we will name the processor here before we take a penny. Your card number would be handled entirely by them and would never reach us.
Technical information. IP address, browser type and which pages you visited, kept in the ordinary server logs our hosting and database providers keep, for security and troubleshooting. Those periods are set by Netlify and Supabase as part of hosting rather than chosen by us. We are not quoting you a number we do not control; if the exact window matters to you, ask and we will tell you what they currently state.
The typefaces on this site. Our pages ask Google for the fonts they are set in, which means your browser contacts Google and Google sees your IP address, on every page, whether or not you have an account. We would rather say so than leave it as something you could only find by reading our source. It is named in the table in section 5.
This deserves its own section, because it is unusual and it matters.
When you build a guest list you give us information about other people: names, addresses, email addresses, phone numbers, and sometimes what they can and cannot eat. Those people are not our customers and have not agreed to anything with us.
You are responsible for that information. By entering it you confirm you are entitled to, and that you will handle it reasonably. We use it only to give you the service: we store it, show it back to you, count it, sort it, and let you export or print it. We do not contact your guests and we do not use their details for anything else.
A note on dietary requirements and allergies. What somebody can and cannot eat may reveal a religious belief or a medical condition, and some laws treat that as sensitive information deserving extra protection. Please record only what you actually need in order to feed people properly.
And a warning we would rather give you twice. The planner stores what you type and shows it back to you. It does not check anything, and choosing a menu option for somebody does not establish that the food is safe for them. Allergies are a conversation with your caterer, confirmed with your caterer, in writing. Please do not treat this software as the record that keeps somebody safe.
We keep dietary notes exactly as you write them — we do not rewrite, shorten or interpret them — so that what reaches your caterer is what you meant.
If one of your guests contacts us and asks what we hold about them, we will point them to you, because it is your list, and we will help you answer.
| We use it to | Because |
|---|---|
| Run your account and show you your planner | We have a contract with you |
| Reply when you get in touch | Our legitimate interest in supporting customers |
| Keep the service secure and working | Our legitimate interest in operating safely |
| Email you about the service itself | Contract, or your consent for anything promotional |
| Reply to you about beta access | Your request — you asked us to get in touch, and this is us answering |
| Send you occasional product news | Your consent, given by ticking the separate optional box on our home page. Withdraw it with the unsubscribe link in any of those emails, or by writing to us |
If we ever want to use your information for a materially different purpose than the ones listed here, we will tell you before we do, and where the law requires it we will ask you first.
We use other companies to run the service. Most of them handle your information only to do the job we have asked them to do. Two are different and it is worth saying so: Google receives your IP address because your browser fetches our fonts from them, which is their own arrangement rather than ours; and Kit and Netlify each keep their own operational records about the email they send and the traffic they serve. We have not audited every clause of every provider's terms, so we are not claiming more control than we have.
| Who | What for | Where |
|---|---|---|
| Supabase | Storing the service and your wedding | Germany (Frankfurt) |
| Supabase | Signing you in, and storing your password as a hash | Germany (Frankfurt) |
| Supabase | Keeping backups of the database, so a wedding can be recovered | Germany (Frankfurt) |
| Resend | Sending account email — confirming your address, the link you use to set a password, and a partner’s invitation | Sent from Ireland; Resend’s own records are held in the United States |
| Netlify | Hosting this website; receiving the email address if you ask for beta access using the form on our home page; and receiving bug reports sent from the “Report a bug” button in the planner, which carry what you wrote, the page you were on, your look, your browser and your wedding’s reference number — and nothing from inside your wedding | United States |
| Kit | Sending beta invitations and occasional updates about the product to people who asked for access | United States |
| Google Fonts | Serving the typefaces this site is set in. Your browser fetches them from Google, which means Google receives your IP address when you load a page here | United States |
That is the whole list. There is no payment processor, because there is nothing to pay. There is no separate backup, logging, error-reporting or support service: backups are Supabase's own, the only logs are the ordinary ones Netlify and Supabase keep as part of hosting, and support is a person reading the mailbox behind hello@aislehandleit.com. Earlier versions of this table carried empty rows for those, which implied services that do not exist — and listed payments twice. If any of them is ever added, it gets a row here before it touches anything of yours.
This table is deliberately longer than it was. It used to list four providers, which implied those were all of them. Backups, logs and support are separate services that also touch your information, and each still needs naming with the country it runs in before this policy is published.
Three were added on 5 October 2026, because they were already in use and this table did not say so. Netlify has hosted this site all along and now also receives the beta-access form; Kit sends the beta email; and Google Fonts is fetched by your browser on every page, which hands Google your IP address whether or not you ever create an account. None of those is new behaviour — only the disclosure is. A list of processors that omits the ones you actually use is worse than no list, because it reads as complete.
What is NOT here, and was. This table used to name a mapping service for “turning a town name into coordinates”. Nothing in the product does that. The planner works out sunset times from a list of places built into the file, entirely inside your browser, and no town name is sent anywhere. The row and the paragraph describing it have been removed. If we ever add that lookup, it goes back in before the feature ships, not after.
About email, because it is the one that leaves Europe. Your wedding itself is held in Germany and stays there. Email is different: we use Resend to send it, messages are dispatched from Ireland, and Resend’s own records — which include the email addresses they send to — are held in the United States.
That transfer is covered by Standard Contractual Clauses in our agreement with Resend, and by their participation in the EU–US Data Privacy Framework. We would rather tell you this plainly than let “your data is in Germany” do work it cannot do. It is true of the wedding and not of the email.
We also disclose information if we are legally required to, or if we need to in order to establish or defend a legal claim. If the business is ever sold or merged your information would transfer with it, and we would tell you first.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law.
This one is different from most services, on purpose.
If any of these periods matter to you before you start, write to us and we will tell you honestly where each one stands rather than pointing at this page.
Wherever you live, you can:
We will not charge you for any of this and we will not treat you differently for asking.
If you are in the EU or the UK you additionally have the rights set out in the GDPR, including data portability and the right to complain to your supervisory authority. If you are in California, the CCPA and CPRA only apply to businesses over certain size and revenue thresholds, and a company running a free beta with no revenue is well under them — so we are probably not covered yet. We are not going to use that as a reason to give you less. We will honour requests to know, delete, correct, and opt out of sale or sharing from anyone in California who asks, as a matter of how we intend to run this rather than because a statute currently compels it. And as above, we do not sell or share in that sense.
To use any of these, email hello@aislehandleit.com.
Everything travels between you and us over HTTPS. Access to production systems is limited to people who need it. Your password is stored only as a one-way hash, by our authentication provider, and cannot be read back out.
Two different copies, two different protections. Worth separating, because “encrypted” is often used to cover both and they are not the same:
No service can promise it will never be breached. If one happens and it affects you we will tell you promptly, and tell you what to do about it.
Your wedding is stored in Germany, in Frankfurt. If you are outside the European Economic Area your information is transferred there, and where the law requires a safeguard for that transfer — Standard Contractual Clauses or an adequacy decision — we put one in place.
Germany is in the European Union, so if you are in the EU your wedding does not leave it to reach us. That is why this location was chosen.
Where the wedding is stored is not the whole answer. Signing you in, sending email, taking payment, keeping server logs, holding backups and answering your support message are separate services that may run in different countries from the database. The table in section 5 is where each of those is named, and it is complete as of 5 October 2026. We will not describe our arrangements as “EU only” on the strength of the database alone: the database is in Germany, the person who runs this is in the United States, and three of the five providers in that table are American.
Two different things get called this, and they need separating.
Children as customers. Accounts are for people aged 18 and over. We do not knowingly let anyone younger create one, and we do not knowingly collect information from a child about themselves as a user. If you believe a child has created an account, email us and we will remove it.
Children as wedding guests. This is the common case and it is different. Couples routinely enter children on a guest list — a name, a table, sometimes a meal or an allergy. That information is entered by an adult customer, about a child who is not our customer and has not agreed to anything with us. We hold it only to provide the service, as described in section 3, and we never contact them. If you are entering a child's details, please enter only what the day actually requires, and be aware you are doing so on behalf of whoever is responsible for that child.
We may update this policy. If a change materially affects you we will email you and give you 30 days' notice before it takes effect, so that you can download your wedding as a PDF and leave if you would rather not carry on. Every version is dated at the top.
Email us at hello@aislehandleit.com. That address reaches a person, and it is the right one for anything in this policy — asking what we hold about you, asking for it back, asking us to delete it, or telling us we have got something wrong.
If you are a guest whose details a couple has entered, that address is for you too. You do not need an account to write to us.
Operated by For The Plot, a Wyoming corporation. The email address above is live and reaches a person.