Legal Change Log

A dated, plain-English record of every change to a published bartendersNow™ legal document.

How to read this log. Each entry names the documents affected, classifies the change, states what the document said before and what it says now, why it changed, and the effect on you. We say "the Terms said X from [date]" — never "the Terms always said X." A corrected term applies from the date of its entry below, not retroactively.

Classification. A minor correction moves no operative term — no fee, payout, cancellation, refund, dispute-resolution, or data-practice term changes — is not adverse to any user, and conforms a document to practice already in place. It is published with an entry here; the Terms of Service version is unchanged and no re-acceptance is required. A material change does the opposite: it bumps the Terms of Service version, sends email notice, and requires re-acceptance in the app before you continue.

Questions about any entry, or a request for the superseded text: legal@bartendersnow.com.

---

Documents affected: Payment & Cancellation Policies — a new orientation paragraph before Part 1; Part 1, Sections 2.2 and 5.1; Part 2, Sections 1, 2.2, 2.4, 3.1, 4.2, 5.2 and 6.2, and a new Section 2.5 (Payment Failure on a Short-Notice Booking); Part 3, a new "At a glance" summary and Sections 2.1, 2.2 and 6.1; Part 3, Section 8 (Policy Updates), which is replaced by a new "Policy Updates" section that applies to the whole document; Part 4, Sections 1, 2.1, 6.1, 8.2, 8.3, 8.4, 9.2 and 10.1, and a new Section 14 (If You Work Before Completing Payout Setup); the Contact Information list; and the Frequently Asked Questions. Version 1.25 → 1.26. Last Updated October 30, 2026 → November 3, 2026. The Effective Date does not move. The separately published Cancellation Policy, Payment Failure Policy, and Bartender Payout Policy pages now redirect to the matching Part.

Classification: minor correction. Except for Part 2, Sections 2.4 and 2.5 and the description of when a Bartender is confirmed, each described below, every term added to the Payment & Cancellation Policies was already published in our Cancellation Policy, Payment Failure Policy, or Bartender Payout Policy. Part 2, Section 2.5 describes how a payment failure on a short-notice booking is handled today: a Host whose payment is not collected, or who cancels before it is collected, is not charged and owes nothing. Part 2, Section 2.4 only narrows when an account is restricted. The corrected description of when a Bartender is confirmed matches how bookings have always been confirmed; a Bartender's payout already depended on the Host's payment clearing, and no payout term changes. No fee, payout percentage, refund tier, dispute-resolution, or data-practice term changes, and nothing is adverse to anyone. The new Policy Updates section states the notice and acceptance rules that Section 15 of our Terms of Service already applied to these policies. The Terms of Service version is unchanged and no re-acceptance is required. As with every correction, the corrected text is not applied against anyone for any period before this entry.

What the document said before this date. Part 3, Section 8 said "Material changes will be communicated via email and in-app notification at least 14 days before taking effect" and "Your continued use of the Platform after policy changes indicates acceptance of the updated terms." Part 4, Section 1 said "Payment Protection: You are confirmed only after the Host's payment is secured, and your payout is not reversed if the Host later disputes the charge (Section 8)." Part 2's key principle said "A Bartender is confirmed only once the Host's payment is secured", Part 1, Section 2.2 said "the 48-hour charge means a Bartender is confirmed only after your payment is secured", and Part 4, Sections 8.2 and 8.4 said "You are confirmed for an event only after the Host's payment has been secured" and "We charge the Host before we confirm you". Part 2 did not describe a payment failure on a short-notice booking; the separate Payment Failure Policy page said that if the charge fails, "the booking does not proceed." Part 2, Sections 4.2, 5.2 and 6.2 applied a Host cancellation, account suspension and collections to every unresolved payment failure. Part 2, Section 2.4 said that after a failed cancellation payment "Your account is restricted until payment is resolved", with no exception for a payment your bank asks you to confirm. Section 2.2 said an unresolved failure "is handled per Section 2.3", and the Section 3.1 table said "Handled per 48-hour-lock rules below." Part 3, Section 6.1 said "See the Payment Timeline Policy for full details on each trigger." Eight passages pointed Bartenders to "our Bartender Payout Policy" for how held earnings work. The contact list was headed "Billing Disputes" for billing@bartendersnow.com.

What it says from this date. The document opens by explaining that it is one policy in four parts and that the former separate pages are those parts. Part 2 now includes Section 2.5: on a short-notice booking your card is charged right after the booking is confirmed, and if that charge fails the booking stays confirmed while you update your payment method and the charge is retried. If payment is not collected within 24 hours of the first failed attempt, or by your Bartender's scheduled arrival time if that is sooner, the booking is cancelled, you are not charged and owe nothing, and the Bartender is told the booking was cancelled because payment was not collected. If you cancel before payment is collected, you are not charged and owe nothing, and Part 1, Section 5.1 and Part 3, Section 2.1 now say so too. We do not tell the Bartender each time a charge attempt fails, but if the charge still has not gone through after several retries, or cannot be retried, the Bartender may be told that there is a payment issue with the booking. The Section 3.1 table has a row for short-notice payment failures, and Section 2.2 points to Section 2.5. Part 2, Section 2.4 adds that if your bank asks you to confirm a cancellation payment rather than declining it, this is not treated as a payment failure: no grace period runs, your account is not restricted, and our support team will contact you to complete the payment; the Section 3.1 table has a row saying so. Part 2's key principle now says that a Bartender's payout depends on the Host's payment clearing and on the booking's terms being met, and that, except as stated in Section 2.5, an unresolved payment leads to a Host cancellation and the collections process in Section 7; Sections 4.2, 5.2 and 6.2 carry the same exception. Part 1, Section 2.2 says the 48-hour charge leaves time to resolve a payment problem before your event. Part 4, Sections 8.2 to 8.4 say that a Bartender is confirmed when the booking request is accepted and that the Host's payment is collected afterwards — 48 hours before the Bartender's scheduled arrival, or right after confirmation for a short-notice booking; that the Bartender may be told about a payment issue that has not cleared after several attempts; and that if the Host's payment is not resolved within its grace period, or the Host cancels a short-notice booking before its payment is collected, the booking is cancelled, the Bartender is told, and no payout is issued, which for a short-notice booking can happen close to the start of the event. Part 3 has an "At a glance" summary, and its refund table and service-fee list show that a Bartender cancellation at any time gives you a 100% refund. Part 3, Section 6.1 points to Part 1, Section 2.1. Part 4, Section 1 says that your payout is backed by our support and dispute process, still depends on the Host's payment clearing and the booking's terms being met, and is not a guarantee by bartendersNow™. Part 4, Section 14 explains working before payout setup, held earnings, what happens if verification can't be completed, and holds required by law, and the eight pointers now point to it. The Policy Updates section says we change these policies as described in Section 15 of our Terms of Service, that a material change — including any change to our fees, payout percentages, or cancellation or refund terms — is made only with the notice in Section 15.2 and takes effect for you only when you accept it, and that continuing to use the Platform never by itself accepts a material change. The contact entry for billing@bartendersnow.com is headed "Outstanding Balances." The Frequently Asked Questions add the questions previously answered on the separate pages, including what to do in a weather emergency and if you can't pay right now, and the answer about a Host's failed payment now points to Part 2, Sections 2.3 and 2.5.

Why it changed. We published the same payment and cancellation terms twice — once as separate pages and once inside these Policies, which our Terms of Service incorporate — and the two versions had drifted apart. These Policies are now the only version. Part 2, Section 2.5 replaces the description on the separate Payment Failure Policy page, which no longer matched how a short-notice payment failure is handled. Several passages said a Bartender is confirmed only after the Host's payment is secured; in fact a booking is confirmed when the request is accepted and the Host's payment is collected afterwards, and those passages now say so. The Policy Updates text now matches Section 15 of our Terms of Service, which already governed.

Effect on Hosts, Bartenders, and visitors. None. The text now describes how bookings, charges, cancellations and payouts already work; this entry changes no booking, charge, refund, payout, or fee. Three items from the former separate pages were not carried over because they were not terms: an illustrative example of a payment-failure notice, a suggested email subject line, and a sentence saying we were exploring instant payouts.

Prior text. The changed lines are quoted above. The full superseded text of all four documents is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Dispute Resolution Policy — Sections 4.1, 4.2, 4.3 and 5.2. Last Updated October 20, 2026 → November 3, 2026. The Effective Date does not move.

Classification: minor correction. It conforms the policy to the refund and payout terms in our Payment & Cancellation Policies, which already govern, and is adverse to no one. The Terms of Service version is unchanged and no re-acceptance is required.

What the policy said before this date. The Section 4.3 table said that if a Bartender cancels "7-14 days before", the "Host receives 50% refund." Section 4.2 was headed "Bartender Payment Guarantee" and began "Per our Terms of Service, Hosts cannot dispute Bartender payments for completed services." Section 5.2 said a Bartender's payment is protected "in accordance with our Bartender Payment Guarantee" and referred to "the Payment Timeline Policy." Sections 4.1 and 4.3 referred to our Cancellation Policy.

What it says from this date. The table says a Host receives a 100% refund whenever a Bartender cancels, as our Payment & Cancellation Policies already provide. Section 4.2 is headed "Bartender Payment Protection" and says that payment for a booking arranged and paid through bartendersNow™ is backed by our support and dispute process, as described in Part 4, Section 8 of our Payment & Cancellation Policies, and is not a guarantee by bartendersNow™; the protections listed beneath it are unchanged. Section 5.2 refers to Section 4.2 and to Part 1 of our Payment & Cancellation Policies. Sections 4.1 and 4.3 refer to Part 3 of our Payment & Cancellation Policies.

Why it changed. The table understated the refund a Host receives when a Bartender cancels 7–14 days before the event. Our Terms of Service do not say that Hosts cannot dispute Bartender payments; Hosts can raise disputes as this policy describes. The separate Cancellation Policy and Payment Timeline Policy pages are now parts of our Payment & Cancellation Policies.

Effect on Hosts, Bartenders, and visitors. None in practice: Hosts have always been entitled to a 100% refund when a Bartender cancels, and Bartenders' payment protections are unchanged.

Prior text. The changed lines are quoted above; the full superseded text is available on request at legal@bartendersnow.com.

---

Documents affected: Payment & Cancellation Policies, Part 4 (Bartender Payout Policy) — Section 1 (Overview), the "When You're Paid" item; Section 2.1 (Standard Payout Process), Steps 4 and 5; Section 2.2 (Total Timeline), the "Payout released" row; Section 4.3 (Task Completion Deadline); Section 6.1 (Immediate Payout for Cancellations), the paragraph below the table; Section 6.2 (Example: Host Cancels 10 Days Before), the "Timing" line; Section 7.3 (Captain Fee on Cancellations), a new sentence below the table; and Frequently Asked Questions, the answers to "When do I get paid after an event?" and "What if the Host cancels?". Version 1.24 → 1.25. Last Updated stays October 30, 2026 (versions 1.23, 1.24 and 1.25 were published together that day). Payment Timeline Policy — Section 11 (Frequently Asked Questions), the answer to "When does the Bartender get paid?". Version 1.9 → 1.10. Last Updated October 20, 2026 → October 30, 2026. Neither Effective Date moves. This completes the correction recorded for the Bartender Payout Policy in the entry below.

Classification: minor correction. It moves no fee, payout amount, cancellation, refund, dispute-resolution, or data-practice term, and it is not adverse to anyone. It brings these documents into line with the Bartender Payout Policy, which already says that a payout depends on the Host's payment clearing and that a Bartender is paid only once payout setup is complete. It describes how payouts already work and adds no new hold. The Terms of Service version is unchanged and no re-acceptance is required. As with every correction, the corrected text is not applied against anyone for any period before this entry.

What the Payment & Cancellation Policies said before this date, in their own words. Part 4, Section 1: "Your payout is released once you complete your post-event tasks — or automatically 7 days after the event if you don't — and then arrives in your bank account on the standard 2–4 business-day schedule." Section 2.1, Step 4: "Once you complete your post-event tasks, your payout is released. If you haven't completed them, it's released automatically 7 days after the event." Step 5: "Funds arrive in your bank account 2-4 business days after payout is initiated." Section 2.2, "Payout released": "When you complete your post-event tasks — or automatically 7 days after the event". Section 4.3: "Complete your post-service tasks to release your payout. If you don't, your payout is released automatically 7 days after your event." Section 6.1, below the table: "Cancellation payouts follow the same payout-setup rule as event payouts: if your payout setup and identity verification aren't complete, the amount is held safely with our payment processor and released when you finish (see our Bartender Payout Policy)." Section 6.2, "Timing": "Immediate (within minutes of cancellation)". Frequently Asked Questions, "When do I get paid after an event?": "Your payout is released once you complete your post-event tasks (confirm your departure time and service completion). If you don't complete them, it's released automatically 7 days after the event." "What if the Host cancels?": "Payment is issued immediately, provided your payout setup is complete — if it isn't, it's held for you (see our Bartender Payout Policy)."

What the Payment Timeline Policy said before this date, in its own words. Section 11, "When does the Bartender get paid?": "Bartenders are paid once they complete their post-event tasks, or automatically 7 days after your event; funds then arrive on their bank's standard 2–4 business-day schedule. For cancellations within 14 days, they're paid immediately."

What they say from this date. In the Payment & Cancellation Policies, each of those places now adds that if the Host's payment is still clearing with our payment processor, the payout is released once those funds become available. Section 1 adds that it then arrives on the same schedule. Step 5 now reads: "Funds then arrive in your bank account on the standard 2–4 business-day schedule after your payout is released." Section 6.2's "Timing" line now reads: "Issued immediately on cancellation, subject to the payout-setup and funds rules in Section 6.1 above." Section 7.3 adds, below its table: "Captain cancellation payouts follow the same payout-setup and funds rules as cancellation payouts in Section 6.1 above." The Payment Timeline Policy answer now reads: "Bartenders are paid once they complete their post-event tasks, or automatically 7 days after your event, or later if your payment is still clearing with our payment processor, provided their payout setup is complete; funds then arrive on their bank's standard 2–4 business-day schedule. For cancellations within 14 days, they're paid immediately, on the same conditions. If a Bartender hasn't finished payout setup yet, their earnings are held for them with our payment processor and released once they do. None of this changes what you're charged or when." Everything else in those passages is unchanged.

Why it changed. A Bartender's payout comes from the Host's payment for the booking. Our payment processor does not always make a Host's payment available to us right away, and we can't send a payout until it does; that is true of a payout owed when a Host cancels as well as after an event. Separately, a Bartender who has not finished payout setup can work a booking, and their earnings are held for them until they do. The Payment Timeline Policy did not mention either case, and the Payment & Cancellation Policies did not mention the first.

Effect on Hosts, Bartenders, and visitors. Hosts: what you are charged, when you are charged, and your refund tiers do not change. Bartenders: what you are paid, our fees, and cancellation tiers do not change. If the Host's payment has already cleared, nothing changes. If it is still clearing when your payout would otherwise be released, your payout is released once those funds become available, and then reaches your bank on the same standard schedule. Visitors: none.

Prior text. The changed passages are quoted in full above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Bartender Payout Policy — Section 1 (Overview), the "When You're Paid" item; Section 2.1 (Standard Payout Process), Steps 4 and 5; Section 2.2 (Total Timeline), the "Payout released" row; Section 4.3 (Task Completion Deadline); Section 6.1 (Immediate Payout for Cancellations), the paragraph below the table; Section 6.2 (Example: Host Cancels 10 Days Before), the "Timing" line; Section 7.3 (Captain Fee on Cancellations), a new sentence below the table; and Section 14 (Frequently Asked Questions), the answers to "When do I get paid after an event?" and "What if the Host cancels?". Version 1.11 → 1.12. Last Updated stays October 30, 2026 (versions 1.11 and 1.12 were published together that day). The Effective Date does not move. The same text in Part 4 of the Payment & Cancellation Policies, and the matching answer in the Payment Timeline Policy, will be corrected in a later entry.

Classification: minor correction. It moves no fee, payout amount, cancellation, refund, dispute-resolution, or data-practice term, and it is not adverse to anyone: Section 1 already said that a payout "still depends on the Host's payment clearing," and this change says the same thing in each place that describes when a payout is released. It describes how payouts already work and adds no new hold. The Terms of Service version is unchanged and no re-acceptance is required. As with every correction, the corrected text is not applied against anyone for any period before this entry.

What the Bartender Payout Policy said before this date, in its own words. Section 1: "Your payout is released once you complete your post-event tasks — or automatically 7 days after the event if you don't — and then arrives in your bank account on the standard 2–4 business-day schedule." Section 2.1, Step 4: "Once you complete your post-event tasks, your payout is released. If you haven't completed them, it's released automatically 7 days after the event." Step 5: "Funds arrive in your bank account 2-4 business days after payout is initiated." Section 2.2, "Payout released": "When you complete your post-event tasks — or automatically 7 days after the event". Section 4.3: "Complete your post-service tasks to release your payout. If you don't, your payout is released automatically 7 days after your event." Section 14, "When do I get paid after an event?": "Your payout is released once you complete your post-event tasks (confirm your departure time and service completion). If you don't complete them, it's released automatically 7 days after the event." Section 6.1, below the table: "Cancellation payouts follow the same payout-setup rule as event payouts: if your payout setup and identity verification aren't complete, the amount is held safely with our payment processor and released when you finish (see Section 15)." Section 6.2, "Timing": "Immediate (within minutes of cancellation)". Section 14, "What if the Host cancels?": "Payment is issued immediately, provided your payout setup is complete — if it isn't, it's held for you (see Section 15)."

What it says from this date. Each of those places now adds that if the Host's payment is still clearing with our payment processor, your payout is released once those funds become available. Section 1 adds that it then arrives on the same schedule. Step 5 now reads: "Funds then arrive in your bank account on the standard 2–4 business-day schedule after your payout is released." Section 6.2's "Timing" line now reads: "Issued immediately on cancellation, subject to the payout-setup and funds rules in Section 6.1 above." Section 7.3 adds, below its table: "Captain cancellation payouts follow the same payout-setup and funds rules as cancellation payouts in Section 6.1 above." Everything else in those passages is unchanged.

Why it changed. Your payout comes from the Host's payment for the booking. Our payment processor does not always make a Host's payment available to us right away, and we can't send a payout until it does. The policy said your payout is released as soon as your post-event tasks are done, which isn't possible while the Host's payment is still clearing. The same is true of a payout owed when a Host cancels. It now says so wherever it describes when a payout is released.

Effect on Hosts, Bartenders, and visitors. Bartenders: what you are paid, our fees, and cancellation tiers do not change. If the Host's payment has already cleared, nothing changes. If it is still clearing when your payout would otherwise be released, your payout is released once those funds become available, and then reaches your bank on the same standard schedule. Hosts: none. Visitors: none.

Prior text. The changed passages are quoted in full above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Payment & Cancellation Policies — Section 11.3 (IRS Form 1099-K Reporting). Version 1.23 → 1.24. Last Updated stays October 30, 2026 (versions 1.23, 1.24 and 1.25 were published together that day). The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms the document to how the platform already works. The Terms of Service version is unchanged and no re-acceptance is required.

What it said before this date. Section 11.3 began "As a marketplace facilitator utilizing Stripe Connect as our payment settlement partner."

What it says from this date. "As an online marketplace utilizing Stripe Connect as our payment settlement partner"; the rest of the sentence and of Section 11.3 is unchanged. This is now the same wording as Section 11.3 of the Bartender Payout Policy.

Why it changed. For the reason given in the two 2026-09-29 entries: "marketplace facilitator" is a California sales and use tax term for platforms that facilitate retail sales of goods. This is the sentence the first of those entries said would be corrected later.

Effect on Hosts, Bartenders, and visitors. None. Form 1099-K reporting is unchanged.

Prior text. The changed line is quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 5.1 (Retention Periods), a new "Security and system logs" paragraph; and Section 5.2 (Deletion Process), a new bullet. Last Updated October 22, 2026 → October 30, 2026. The Effective Date does not move.

Classification: material change. It describes, for the first time, the security and system logs we keep and how long we keep them, and it allows us to keep that information for longer than we do today. Under Section 14.2 of the Privacy Policy, we are emailing notice of it to registered users and showing a notice at the top of the Privacy Policy, and the longer retention period takes effect no earlier than 30 days after that email: on November 30, 2026. Until then, security and system logs are kept on our current, shorter schedule. This is a material change to the Privacy Policy, not to the Terms of Service: the Terms of Service version is unchanged and no re-acceptance is required, because Section 14.2 of the Privacy Policy provides for notice rather than re-acceptance.

What the Privacy Policy said before this date. Section 5.1: added; no prior text. Section 5.2: added; no prior text. Neither section described the technical logs our servers record when the Platform is used, or how long we keep them. Section 5.2 said, and still says, that when information is deleted, "Data is removed from active databases within 30 days and purged from disaster-recovery backups in accordance with our standard automated backup retention cycles."

What it says from this date. Section 5.1 now includes this paragraph, in full:

Security and system logs. Our servers automatically record technical logs when the Platform is used, such as a request's IP address and browser information, the page, function, or database or file record requested, the time, and any email address entered to sign in, create an account, or reset a password, including when the attempt fails or no account exists for that address. If you are signed in, the logs also include your account identifier, your email address, and when and how you signed in. We use these logs only to secure and operate the Platform, detect and investigate security incidents and fraud, identify and notify anyone affected by an incident, and comply with the law. They are separate from the analytics records described above and are never used for analytics or advertising, and access to them is limited to the personnel responsible for securing the Platform. We keep them for up to 400 days, after which they are deleted automatically, unless a legal hold, investigation, or legal claim requires us to keep specific entries longer.

Section 5.2 now includes this bullet, in full:

• Security and system logs are deleted on the schedule described in Section 5.1, not within 30 days of a deletion request.

Why it changed. Our servers already keep technical logs to keep the Platform secure, but the Privacy Policy did not describe those logs or how long we keep them. Keeping them for longer lets us find out, if a security incident ever happens, what was affected and who we need to tell. Our policy now says what these logs hold, what we use them for, who can see them, and the longest we keep them.

Effect on Hosts, Bartenders, and visitors. Nothing you do changes. Until November 30, 2026, security and system logs are kept on our current, shorter schedule. From that date we may keep them for up to 400 days; logs recorded before this change was published are not kept for longer than the schedule that applied when they were recorded. If you ask us to delete your account or your personal information, these logs are not deleted within 30 days of your request; they are deleted on the schedule in Section 5.1. The rest of Section 5.2 is unchanged. Visitors who type an email address into a sign-in, sign-up, or password-reset form are covered by the same paragraph. They are not emailed, because they have no account; this entry and the notice at the top of the Privacy Policy are their notice.

Notice. We are emailing notice of this change to the email address on every registered account at least 30 days before the longer retention period takes effect, and the Privacy Policy carries a notice at the top until November 30, 2026. Questions about the change: privacy@bartendersnow.com.

Prior text. No text was replaced (added; no prior text). The prior version is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 5.1 (Retention Periods), a new "Profile-photo review records" paragraph; and Section 5.2 (Deletion Process), a new "Profile photos" bullet. Last Updated October 22, 2026 → October 30, 2026. The Effective Date does not move.

This change and the October 30, 2026 "Security and system logs" change were published together, in the same version of the Privacy Policy, dated October 30, 2026.

Classification: minor. It describes a practice already in place more completely. It adds no new category of information, no new use, and no new sharing, and narrows nothing you had. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. Section 5.1: added; no prior text. Section 5.2: added; no prior text. It did not describe the record we keep when we review a profile photo, or how we delete profile photos.

What it says from this date. Section 5.1 now includes this paragraph, in full:

Profile-photo review records. When you submit a profile photo, we review it before it appears on your public profile, and we keep a record of that review: the photo's review status (for example, awaiting review, approved, or declined), when you submitted it and when we made our decision, which stored image file the decision applies to, and, if we declined the photo, any reason we recorded. Together, these records are the moderation history of your account. We keep them, and any photo of yours that is awaiting review or that we declined, for as long as your account is open, so that we can show you the status of your photo, explain a decision, and respond to a safety report, dispute, or appeal about an image, and longer only where a safety report, investigation, legal hold, audit, or legal claim requires it. We do not show a photo on your public profile until it has been approved. We delete these records and photos as described in Section 5.2.

Section 5.2 now includes this bullet, in full:

• Profile photos. When you ask us to delete your account, or make a verified request to delete your personal information under Section 12, we delete your profile photo — the published photo, any photo still awaiting review, and any photo we declined — together with the stored image files and the profile-photo review records described in Section 5.1, as part of fulfilling that request, within the response times described in Section 12.5. We remove the photo from your public profile at the same time. We keep a photo or a review record only where a law, a legal hold, an audit, an investigation, or a legal claim requires us to, and if that happens we will tell you what we kept and why when we respond to your request, as described in Section 12.1.

Why it changed. We review every profile photo before it appears on a public profile and keep a record of that review. Our policy now says what that record holds, how long we keep it, and how we delete it with the photos.

Effect on Hosts, Bartenders, and visitors. Nothing you do changes. Declined photos and review records are kept while your account is open, and are deleted with your account or on a verified deletion request, except where a law, legal hold, audit, investigation, or legal claim requires us to keep them.

Prior text. No text was replaced (added; no prior text). The prior version is available on request at legal@bartendersnow.com.

---

Documents affected: Bartender Payout Policy — Section 10.1 (What You Can See), Section 10.2 (Payout Receipt), and the "Tax Document Availability" item in Section 11.3 (IRS Form 1099-K Reporting). Version 1.10 → 1.11. Payment & Cancellation Policies — Part 4, the same Sections 10.1, 10.2 and 11.3. Version 1.22 → 1.23. Last Updated October 22, 2026 → October 30, 2026 in both. The Effective Date of each document does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, and it is not adverse to anyone: it describes the payout dashboard as it is, updates the description of the payout receipt, and gives a fuller account of how a Form 1099-K is delivered. The Terms of Service version is unchanged and no re-acceptance is required. As with every correction, the corrected text is not applied against anyone for any period before this entry.

What the documents said before this date, in their own words. Both documents listed, among the things a Bartender can see on the payment dashboard:

• "Year-to-Date Totals: Your gross service totals, platform fees, and payouts for the year"
• "Tax Information: 1099 preparation data"

They did not list held earnings. Section 10.2 said: "Each payout includes a detailed receipt:" followed by "Event details", "Hours worked", "Gross service total", "Platform fee", "Your payout", and "Payment method and timing". Section 11.3 said: "Tax Document Availability: Form 1099-K documents are made available electronically via your Stripe Express / account dashboard by January 31 following each tax year."

What they say from this date. The dashboard list now reads Upcoming Payouts, Held Earnings, Processing Payouts, and Completed Payouts. The new Held Earnings item says that if you've earned before finishing payout setup, the dashboard shows the amount being held for you with our payment processor and a link to finish setup, and that it is released once your payout setup and identity verification are complete, so you won't lose it. The Year-to-Date Totals and Tax Information items are removed, and a new sentence says that tax documents are not provided in the app, and that a Form 1099-K, if one is issued to you, is delivered through Stripe as described in Section 11.3. Section 10.2 now says each payout has a receipt in the app. For a booking payout the receipt shows event details, hours booked plus any approved labor-overage hours, gross service total, platform fee, your payout, and where and when your payout was sent. A tip or labor-overage receipt shows the amount paid to you, and any item the booking's records do not include is left off, not estimated. Section 11.3 now says that a Form 1099-K, if one is issued to you, is delivered through Stripe by January 31 following each tax year: electronically in your Stripe Express dashboard if you have consented to electronic delivery, or otherwise by mail to the address on file for your connected payout account.

Why it changed. Our documents should describe the dashboard a Bartender actually sees. The dashboard shows earnings held while payout setup is unfinished, but the list did not mention them. It listed a year-to-date tile and tax information that the app does not provide, and the receipt list is updated to the in-app receipt being rolled out. The tax-document line mentioned only electronic delivery and left out delivery by mail.

Effect on Hosts, Bartenders, and visitors. Bartenders: what you are paid, our fees, payout percentages, and cancellation tiers do not change, and neither does when or whether a Form 1099-K is issued to you. Hosts: none. Visitors: none.

Prior text. The changed items are quoted in full above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Payment & Cancellation Policies — Part 4, Section 12.1 (If You No-Show), its closing paragraph. Version 1.21 → 1.22. Bartender Payout Policy — Section 12.1 (If You No-Show), the same paragraph. Version 1.9 → 1.10. Last Updated October 20, 2026 → October 22, 2026 in both. The Effective Date of each document does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, and it is not adverse to anyone: the same section already said that a Bartender who does not show up is not paid for that booking and that the Host receives a 100% refund, and this change removes a sentence that contradicted those terms. The Terms of Service version is unchanged and no re-acceptance is required. As with every correction, the corrected text is not applied against anyone for any period before this entry.

What the documents said before this date, in their own words. Both documents said: "No-shows undermine the trust essential to our marketplace. The platform's sole remedy is restriction or termination of access, consistent with the independent contractor relationship."

What they say from this date. Both documents say that bartendersNow™ does not impose fines, financial penalties, or other employment-style discipline for a no-show; that no payment is owed for service not rendered, so not paying a Bartender for a booking they did not work, and refunding the Host for it, is not a penalty; and that any action we take on a Bartender's platform access is one of the enforcement responses in Section 10.3 of the User Agreement & Code of Conduct.

Why it changed. The paragraph called restricting or ending platform access our "sole remedy," but the same section, a few lines above it, already said that a Bartender is not paid for a booking they did not show up for and that the Host receives a full refund. Our documents should not say two different things about the same subject, so the paragraph now agrees with the terms above it and with Section 10.3 of the User Agreement & Code of Conduct.

Effect on Hosts, Bartenders, and visitors. Bartenders: what you are paid for work you complete does not change, and neither do our fees, payout percentages, or cancellation tiers. Hosts: nothing changes about your fees, charges, or refunds. Visitors: none.

Prior text. The changed paragraph is quoted in full above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 5.1 (Retention Periods), a new "Profile-display choices" paragraph; and Section 12.1, the list of records we keep when you ask us to delete your information. Last Updated October 20, 2026 → October 22, 2026. The Effective Date does not move.

Classification: a new disclosure of a practice already in place. It collects nothing new and moves no fee, payout, cancellation, refund, or dispute-resolution term. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. It did not describe the record we keep when a Bartender turns on or off the option to show a certification on their profile.

What it says from this date. Each time a Bartender turns that option on or off, we keep a record linked to their account: which document, whether it was turned on or off, when, and which notice version was shown. The record never includes the certification's details. We keep it while the account is active and for three years after we delete the account, or longer under a legal hold or claim. We keep it as proof of the choice if the Bartender asks us to delete their information, and we include it when they ask for a copy.

Why it changed. The show-on-profile switch has kept these records since October 20, 2026. Our policy now says so.

Effect on Hosts, Bartenders, and visitors. Bartenders: nothing you do changes. Hosts and visitors: none.

Prior text. No text was replaced. The prior version is available on request at legal@bartendersnow.com.

---

Documents affected: Terms of Service — Section 6.4. Last Updated October 15, 2026 → October 20, 2026. Payment & Cancellation Policies — Part 1, Section 4.2; Part 2, Sections 2.2 and 2.3; and the FAQ. Version 1.20 → 1.21. Payment Failure Policy — Sections 2.2 and 2.3 and the FAQ. Version 1.9 → 1.10. Payment Timeline Policy — Section 4.2. Version 1.8 → 1.9. Accessibility Statement — notification features. Cookie Policy — Section 4.1, the Twilio entry. Last Updated → October 20, 2026. Privacy Policy — Section 7.2 (Communication Preferences), the SMS Communications heading; its Last Updated date stays October 20, 2026. The Effective Date of each document does not move.

Classification: minor correction. No fee, payout, cancellation, refund, grace-period, dispute-resolution, or data-practice term changes. The 24-hour grace period still runs from the time the payment fails. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. "The Host will receive immediate notifications via email and SMS"; "You receive urgent notifications via email and SMS (and in-app, possibly phone)"; "immediate email and SMS notifications"; "and by text message if you have given us a mobile number and have not turned off text notifications"; "Email and SMS notification options"; Twilio as providing "SMS multi-factor authentication (OTP)"; and the Privacy Policy heading "SMS Communications:".

What they say from this date. We notify you about a payment problem in the app and by email. Twilio is listed for operational text alerts about your bookings, where enabled. The Privacy Policy's text-message preferences apply if we send you text messages.

Why it changed. We do not currently send text messages about payments, and our one-time codes are sent by email, not text. Our documents now describe only the notices we actually send.

Effect on Hosts, Bartenders, and visitors. Hosts: watch the app and your email for payment notices; your deadlines do not change. Bartenders and visitors: none.

Prior text. Quoted above; the full superseded text is available on request at legal@bartendersnow.com.

---

Documents affected: Cancellation Policy — Section 6.1. Version 1.9 → 1.10. Payment & Cancellation Policies — Part 3, Section 5.1. Version 1.21 (see the entry above). Dispute Resolution Policy — Section 5.2. Last Updated September 29, 2026 → October 20, 2026. The Effective Date of each document does not move.

Classification: minor correction. What a Bartender is paid when a Host does not show up is unchanged, and it is not adverse to anyone. The 12% Platform Retained Fee in Section 6.2 of the Terms of Service has always been retained before payout. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. "Bartender receives 100% of their contracted payment."

What they say from this date. The Bartender's compensation is 100% of their contracted amount, paid less the 12% Platform Retained Fee.

Why it changed. It completes our earlier entry of this date on cancellation compensation, so every section describes the same payment the same way.

Effect on Hosts, Bartenders, and visitors. Bartenders: no change to what you are paid. Hosts and visitors: none.

Prior text. Quoted above; available on request at legal@bartendersnow.com.

---

Documents affected: Cancellation Policy — Section 2.1 (Refund Matrix), the Bartender Compensation and Captain Service Fee columns and a new paragraph, "What your Bartender is paid"; Section 2.5 (When Cancellation Is Available); and Section 3 (Cancellation Examples), Examples 1 to 4. Version 1.8 → 1.9. Last Updated October 15, 2026 → October 20, 2026. Payment & Cancellation Policies — Part 3, Section 2.1 (Cancellation Tiers) and the same new paragraph, the Section 2.3 (Captain Service Fee) table, Section 2.5, and Section 7 (Cancellation Examples); Part 4, the Section 6.1 and Section 7.3 tables; and the "What if the Host cancels?" question in the Bartender Payout Questions FAQ. Version 1.19 → 1.20. Last Updated October 15, 2026 → October 20, 2026. Bartender Payout Policy — the Section 6.1 and Section 7.3 tables, and the "What if the Host cancels?" question in Section 14. Version 1.8 → 1.9. Last Updated September 29, 2026 → October 20, 2026. The Effective Date of each document does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, and it is not adverse to anyone. The cancellation tiers, the compensation percentages, the Host refund amounts, and what a Bartender or Captain is paid are all unchanged. Our 12% platform fee — the Platform Retained Fee in Section 6.2 of the Terms of Service — has always been retained from cancellation compensation before payout, just as it is from a completed booking; Section 6.2 of the Terms of Service, Sections 3.1, 6.2 and 7.2 of the Bartender Payout Policy, and Part 4, Section 6.2 of the Payment & Cancellation Policies already said so, with the worked example $200 − $24 = $176. This change brings the cancellation sections into line with them. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date, in their own words. The cancellation tables listed "Bartender Compensation" as "50% of contracted amount" (7–14 days) and "100% of contracted amount" (within 7 days) without mentioning the platform fee, and said of the Captain Service fee "No - Captain keeps 100%." Section 2.5 said "your Bartender receives 100% of their contracted amount." The examples said "Bartender receives: $200 (50% of $400)", "Bartender receives: $400 (100%)", "Bartender receives: $200 (50%)" and "Captain receives: $50 (100% - non-refundable)." The payout tables were headed "You Receive" and "Captain Receives," and the FAQ answer said "You receive 50% if they cancel 7-14 days before, or 100% if within 7 days."

What they say from this date. Bartender Compensation is a percentage of the Bartender's contracted amount, shown before the 12% Platform Retained Fee. A new paragraph says that the fee is retained from cancellation compensation before it is paid, just as it is from a completed booking, so the amount paid is that compensation less the fee, rounded to the nearest cent; that the same applies to a Captain Service fee; and that Host refund amounts are not affected. Each example shows the compensation, the fee, and the amount paid: $200 − $24 = $176 paid to Bartender (7–14 days); $400 − $48 = $352 paid to Bartender (within 7 days); and, with Captain Service, $50 − $6 = $44 paid to Captain. The payout tables are headed "Your Compensation" and "Captain Compensation," before the 12% platform fee, and the FAQ answer says the same, with the $176 example.

Why it changed. Our cancellation sections described a Bartender's cancellation compensation as what the Bartender receives, without saying that our 12% platform fee is retained before it is paid. Our payout sections already showed the fee, so our documents said two different things about the same payment. They now say the same thing everywhere. Our FAQ answer to "What if a host cancels?" changes in the same way, and our FAQ answer to "What is the cancellation policy?" now describes the Bartender's share as compensation, a percentage of the contracted amount, rather than as a payout.

Effect on Hosts, Bartenders, and visitors. Bartenders: what you are paid does not change. If a Host cancels 7–14 days before your scheduled arrival, your compensation is 50% of your contracted amount; within 7 days, it is 100%. As with a completed booking, the 12% platform fee is retained before payout — for example, $200 − $24 = $176 on a $400 booking. Captains: the same applies to the Captain Service fee — for example, $50 − $6 = $44. Hosts: nothing changes about your charges or refunds. Visitors: none.

Prior text. The superseded wording is quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 4.1 (Between Platform Users), the certifications item in the list of public profile information, and the first two sentences of the "Bartender-Directed Document Sharing" paragraph. Last Updated October 18, 2026 → October 20, 2026. The Effective Date does not move.

Classification: a new disclosure, about a choice that is off unless a Bartender turns it on. It collects no new information from you, and nothing becomes public unless a Bartender chooses to show it. Section 4.1 already said that certifications a Bartender enters are part of the public profile. It moves no fee, payout, cancellation, refund, or dispute-resolution term. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. The list of public profile information included "Certifications you have entered, shown as self-reported and not independently verified." The "Bartender-Directed Document Sharing" paragraph began: "Documents in a bartender's Documents Hub are private by default. A document is shared with a host only when the bartender expressly chooses to share that specific document with that specific host, and only with a host the bartender has a confirmed booking or an open booking request with."

What it says from this date. The list now includes certifications a Bartender has entered on their profile, and any certification from their Documents Hub that they choose to show on their profile — its name, issuing organization, issue date and expiration date only — shown as self-reported; we do not review or confirm them, and we never show certificate numbers or document files. The "Bartender-Directed Document Sharing" paragraph now says that Documents Hub documents are private by default; that a Bartender may choose, one certification at a time, to show that summary on their public profile, which anyone can see, including people who are not signed in; that we show a summary only while the profile is public and only for certifications chosen from our list of certification types; that the Bartender can turn it off at any time, and we then remove the summary, although we cannot remove copies other people have already saved; and that the document itself is still shared with a Host only when the Bartender chooses to share it with that Host, as before. The rest of the paragraph is unchanged.

Why it changed. We are adding a switch that lets a Bartender show a summary of a certification from their Documents Hub on their profile. A privacy notice should say what that summary shows, who can see it, what is never shown, and what happens when the Bartender turns it off, before the switch is offered.

Effect on Hosts, Bartenders, and visitors. Bartenders: each certification in your Documents Hub stays private unless you turn on "Show this certification on my profile" for it; you can turn it off at any time. Hosts and visitors: you may see a self-reported summary of a certification a Bartender has chosen to show; it is not reviewed or confirmed by us.

Prior text. The superseded text is quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 2.1 (Personal Information You Provide), the "Identity Verification & Biometric Processing" paragraph; Section 2.3 (Information from Third Parties), the paragraph on the date of birth from your identity document; Section 3.2 (Safety and Security), a new item; Section 12.1 (California Consumer Rights), the "Limitation on Sensitive Personal Information" paragraph; Section 12.2 (Categories of Personal Information), the "Biometric Information" and "Sensitive Personal Information" lists and the paragraph on Stripe Identity; and Section 12.3 (Business Purposes for Collection), a new item under Security and Fraud Prevention. Last Updated October 16, 2026 → October 18, 2026. The Effective Date does not move.

Classification: a new disclosure, about a practice that has already begun. It describes a step in which a member of our team views a Bartender's identity-verification images to compare them with the Bartender's profile photo. That comparison was made once, on October 13, 2026, before this text was published, as our entry dated 2026-10-15 records, and no comparison has been made since. It conforms the Privacy Policy to Section 3.3 of the Terms of Service, which has described the comparison since October 15, 2026. It collects no new information from you, we do not sell or share any of it, and it moves no fee, payout, cancellation, refund, or dispute-resolution term. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. Section 2.3 said: "We do not receive your identity document number, and we do not receive images of your document or of your face." Section 2.1 said that Stripe may collect and process biometric verification data, but it did not say that Stripe compares your selfie with the photo on your identity document, and the Policy did not say that our team may view your identity-verification images. Section 12.1 said we collect Sensitive Personal Information "solely for necessary platform operational purposes, identity verification via Stripe, and service fulfillment."

What it says from this date. Stripe uses its own automated face-matching technology to compare a selfie you take with the photo on your identity document, and we do not receive, store, or have access to the biometric templates it uses. Authorized members of our team may view your identity-document and selfie images, and the details Stripe displays with them, which can include your identity document number, in Stripe's dashboard to compare them with your profile photo, for identity-verification and fraud-prevention purposes, and we may require that comparison before a Bartender can send or accept booking requests. The comparison is made by eye: we do not use facial-recognition or face-matching technology for it, and we do not create a faceprint or any other biometric template from your profile photo or from those images. We view those images only within Stripe's dashboard; we do not copy, download, screenshot, or store them, and we keep a record of the outcome of the comparison and of who made it and when, but not the images. Stripe still does not send those images or your identity document number to our systems. Section 12.2 lists those images as Sensitive Personal Information, Section 12.1 adds fraud prevention to the purposes for which we collect Sensitive Personal Information, and Section 12.3 lists the comparison as a security and fraud-prevention purpose.

Why it changed. We are adding a step in which a person on our team compares a Bartender's profile photo with the images from their identity verification, to help confirm that the person in the photo is the person who verified. Our sentence that we do not receive images of your document or of your face was accurate about what Stripe sends to our systems, but it did not tell you that our team could view those images in Stripe's dashboard, and on October 13, 2026 we did. A privacy notice should say who can see your identity images, and why; this one now does.

Effect on Hosts, Bartenders, and visitors. Bartenders: an authorized member of our team may view your identity-verification images in Stripe's dashboard to compare them with your profile photo. Once the comparison is required, it may need to be completed before you can send or accept booking requests; it does not affect setting up your profile or browsing events. It has not been used to limit any account. Hosts and visitors: none.

Prior text. The superseded sentences are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 7.1 (Account Settings), Section 7.3 (Data Access and Portability), and Section 12.5 (How to Exercise Your California Privacy Rights). Last Updated October 16, 2026 → October 18, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms the document to how the platform works. It does not narrow any right: you can ask us for a copy of your information, as you could before. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. Section 7.1 listed "Download your data in portable format." Section 7.3 listed "View all personal information we have about you," "Download your data in machine-readable format," "Export your profile information," "Download transaction history" and "Receive data in commonly used formats (CSV, JSON)." Section 12.5 said "Registered users may also manage account data and download profile information directly within their account settings." Those statements did not describe the app: it does not offer a way to view all of the information we have about you, or to download or export your data, your profile, or your transaction history.

What it says from this date. Section 7.1 says you can ask us for a copy of your data in a portable format, and points to Section 12.5. Section 7.3 says you can ask us what personal information we have about you; ask for a copy of your information, including your profile information and a record of your bookings and payments, in a portable, machine-readable format; and receive that copy in a commonly used format, to the extent technically feasible. It says that the app does not offer a download of your data and that you make these requests by email, as described in Section 12.5. Section 12.5 says that registered users can update much of their account information in the app, and that to request a copy of their information they email us.

Why it changed. A privacy notice should describe only the tools we actually offer. These lines described download and export tools that the app does not have, which could send you looking for a tool that is not there instead of asking us. Your right to a copy of your information has not changed.

Effect on Hosts, Bartenders, and visitors. None to the information we hold or to how we handle a request. To get a copy of your information, email privacy@bartendersnow.com with the subject "CCPA Privacy Request"; we will verify your request and respond on the timeline Section 12.5 describes.

Prior text. The superseded lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 4.1 (Between Platform Users), a new paragraph, "Link Previews," and Section 12.3 (Business Purposes for Collection), a new item under Service Provision. Last Updated October 16, 2026 → October 18, 2026. The Effective Date does not move.

Classification: a new disclosure, published before the practice begins. Today, a link to a Bartender's profile does not show a preview with that Bartender's photo or name. We will start showing a preview of a featured Bartender's profile only after this text is published, and only after we have told each Bartender who is featured at least 7 days in advance. It applies only to Bartenders who have authorized us to feature their profile. It collects no new kind of information, and we do not sell or share any of it. It moves no fee, payout, cancellation, refund, or dispute-resolution term. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. It did not describe what happens when a link to a Bartender's profile is posted in a messaging or social app.

What it says from this date. If a Bartender has authorized us to feature their profile, a link to their profile may show a preview when it is posted in a messaging or social app, such as Messages, WhatsApp, Facebook, LinkedIn, or Slack, whoever shares it. The preview shows the Bartender's profile photograph, first name and last initial, and the city and state they serve; ratings, reviews, and rates are never part of it. Those apps, and the people who receive the link, may keep their own copies of a preview. When the profile is no longer featured, or no longer meets our requirements to be shown publicly, we stop serving the preview and ask the services that allow it to refresh their copy, but we cannot remove copies that other companies or people have already saved. Section 12.3 lists showing that preview as a purpose for which we use the information.

Why it changed. When a link is posted in a messaging or social app, the app may fetch and display a preview, and may keep a copy that we cannot recall. A Bartender who is featured should know what a preview shows, and that copies may last after they stop being featured, before any preview is shown.

Effect on Hosts, Bartenders, and visitors. Featured Bartenders: once previews begin, a shared link to your profile may show the preview described above; to stop it, tap "Stop featuring" under "Feature my profile" in Settings, and we stop serving your preview and remove you from our marketing within 5 business days. Other Bartenders: none. Hosts and visitors: a link you share or receive to a featured Bartender's profile may show that preview.

Prior text. This entry adds a paragraph and an item and removes none. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 4.1 (Between Platform Users), a new paragraph, "Completed Event Teams," and Section 12.3 (Business Purposes for Collection), a new item under Service Provision. Last Updated October 16, 2026 → October 18, 2026. The Effective Date does not move.

Classification: a new disclosure, published before the practice begins. Today, no one is shown which Bartenders were on an event's team. We will begin showing it only after this text is published, and we will not show it for any event that was completed before then. It collects no new kind of information, and we do not sell or share any of it. It moves no fee, payout, cancellation, refund, or dispute-resolution term. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. Section 4.1 said that the number of events a Bartender has completed is shown only to signed-in users. It did not say that other Bartenders may see which events a Bartender was booked for.

What it says from this date. After an event is completed, other identity-verified Bartenders who can see that event may also see the first name, last initial, and screened profile photograph of each Bartender who was booked for it, with a link to that Bartender's profile. We do not show this before or during an event, we never show rates or earnings with it, and it is not shown to Hosts or to the public. A Bartender can turn this off at any time in Settings, with "Show me on completed event teams." Section 12.3 lists showing it as a purpose for which we use the information.

Why it changed. We are adding a feature that shows verified Bartenders the team of a completed event they can see. Which events you were booked for is information about you, so the Privacy Policy should say who can see it, and when, before anyone does.

Effect on Hosts, Bartenders, and visitors. Bartenders: once this begins, other verified Bartenders who can see a completed event you were booked for may see your first name, last initial, and screened photo on its team. It is on unless you turn it off; to turn it off, switch off "Show me on completed event teams" in Settings. Hosts and visitors: none — the team is not shown to you.

Prior text. This entry adds a paragraph and an item and removes none. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 4.1 (Between Platform Users), the paragraph on ratings and reviews. Last Updated October 8, 2026 → October 16, 2026. Community Guidelines — Section 4.3 (Reviews and Feedback). Last Updated September 27, 2026 → October 16, 2026. The Effective Date of each document does not move.

Classification: a new disclosure. The Privacy Policy did not say whether a review shows who wrote it, or who can read the feedback a Bartender leaves about a Host; it now does. It collects no new kind of information, and we do not sell or share any of it. It moves no fee, payout, cancellation, refund, or dispute-resolution term. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. Neither the Privacy Policy nor the Community Guidelines said whether a review shows who wrote it, or who can read the feedback a Bartender leaves about a Host. The Privacy Policy's other wording about ratings and reviews is described in the entry for its Section 4.1 dated 2026-10-08.

What they say from this date. The Privacy Policy says that when a Host rates and reviews a Bartender, the rating and review are shown on the Bartender's profile to signed-in users together with the reviewer's first name and last initial (for example, "Alex R."), and that we do not show a reviewer's full name or contact details with a review. It says that feedback a Bartender leaves about a Host after an event can be read only by the Bartender who wrote it and our team, and is not shown to the Host or to anyone else, and that a star rating the Bartender gives the Host counts toward the Host's overall rating, which other Bartenders can see. Section 4.3 of the Community Guidelines now says the same.

Why it changed. Since September 27, 2026, new reviews that Hosts write about Bartenders have shown the reviewer's first name and last initial, before the Privacy Policy said so; the review form now tells a Host this before they post. Since September 29, 2026, feedback Bartenders leave about Hosts has been readable only by the Bartender who wrote it and our team. A privacy notice should say who can see what you write, and how you are identified when they do.

Effect on Hosts, Bartenders, and visitors. Hosts: a review you write about a Bartender shows your first name and last initial, never your full name or contact details. A review written before September 27, 2026 shows as "Anonymous" unless you edited it on or after that date; if we change that, we will tell the Hosts who wrote those reviews at least 14 days in advance, and anyone who would rather stay anonymous can ask us to keep their review that way. Bartenders: feedback you leave about a Host is not shown to that Host or to other users; a star rating you give counts toward the Host's overall rating. Visitors: none — ratings and reviews are not part of a public profile.

Prior text. This entry adds sentences and removes none. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 4.1 (Between Platform Users), the "Public Profile Information" passage, the item on approximate location. Last Updated October 8, 2026 → October 16, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms the document to how the platform already works. Nothing about the location we show changed on this date. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. It said a Bartender's public profile shows "an approximate location, within about a mile, that we use to show how far you are from an event."

What it says from this date. It says the approximate location is within about a mile and a half, and that it is never a street address.

Why it changed. We measured how far the approximate location we show can be from the location it is based on. It can be more than a mile away, though within about a mile and a half, so "within about a mile" understated it. The location we show protects a Bartender's privacy more than the old wording said, not less.

Effect on Hosts, Bartenders, and visitors. None. The location we show has not changed; only the description of it has.

Prior text. The superseded wording is quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Terms of Service — Section 3.3 (What We Verify — and What We Do Not), new Section 3.4 (Availability of Registration and Services), and Section 15 (Modifications to Terms), replaced in full. Last Updated October 8, 2026 → October 15, 2026. Effective Date July 20, 2026 → October 15, 2026.

Classification: material change. It adds a right for us and changes how the Terms themselves are changed, so the Terms of Service version changes, we email you notice, and you are asked to accept the updated Terms in the app before you continue. The updated Terms apply to you from when you accept them, and only going forward. It moves no fee, payout, cancellation, refund, or dispute-resolution term. The new Section 15 is what introduces a 30-day notice period for material changes, so this change follows the process in the Terms it replaces, which provided for email notice and acceptance in the app; every material change after it will be emailed to you at least 30 days before it takes effect.

What the Terms said before this date. Section 15 said, in full: "We reserve the right to modify these Terms. Material updates will be communicated via email and an in-app re-acceptance modal. Continued platform use after terms update constitutes acceptance." Its last sentence did not distinguish material updates from any other update, so it could be read to say that simply continuing to use bartendersNow™ accepted any change, including a material one. The Terms did not say whether we may limit or close new registrations, or limit a feature. Section 3.3 said "Profile photographs are uploaded by the Bartender and are not checked against the Bartender's identity document."

What they say from this date. Section 15 sets out two tracks. A material change — one that adds, removes, or narrows a right or an obligation, including any change to our fees, payout percentages, cancellation or refund terms, dispute resolution or arbitration, how liability is allocated, or how we handle your personal information — is emailed to you at least 30 days before it takes effect, is published with a new effective date, and takes effect for you only when you accept it in the app, and only going forward. Continuing to use bartendersNow™ never, by itself, accepts a material change, and if you do not accept one, the Terms you last accepted continue to govern any booking you had already entered into. A change to the fee, payout, cancellation, refund, or dispute-resolution terms in a policy the Terms incorporate is treated the same way. A correction that moves no right or obligation, is not adverse to you, and brings the Terms into line with a practice already in place is published in this log, and continuing to use bartendersNow™ after it means you accept it; a corrected term is never applied against you for any period before its entry here. New Section 3.4 says we may limit, suspend, or close new registrations — for everyone, or for Hosts or Bartenders — and may limit or suspend a feature, including during a phased or limited launch, but not in a way that takes away a booking you have already confirmed or a payment already owed to you. Section 3.3 now says that we may have a member of our team visually compare a Bartender's profile photo with the images the Bartender provided during identity verification, and may require that comparison before the Bartender can send or accept booking requests; that it is a visual check by a person and not a guarantee that a photo shows the account holder; and that it does not confirm who will arrive at an event.

Why it changed. The old Section 15 gave two different rules for the same event: material updates needed acceptance in the app, but continued use was also said to be acceptance. A change to your agreement should bind you only after you have been told about it and have had a chance to read it; the new section says so, and gives you 30 days' notice before a material change. We are opening bartendersNow™ in phases, and the Terms did not say that we may limit who can register, or which features are available, while we do; the new section says we may, and that doing so will not take away a confirmed booking or a payment owed to you. We also intend to add a step in which a person on our team compares a Bartender's profile photo with the images from their identity verification, to help confirm that the person in the photo is the person who verified. On October 13, 2026, before this change was published, a member of our team made this comparison once for each Bartender then verified on bartendersNow™. It has not been used to limit any account, and it is not yet required before a Bartender can send or accept booking requests; when it is, we will record that in this log.

Effect on Hosts, Bartenders, and visitors. Hosts and Bartenders with an account: the next time you open the app, you will be asked to accept the updated Terms. Until you do, the Terms you last accepted govern your account, and they continue to govern any booking you had already entered into. If you have a confirmed booking and do not want to accept, email legal@bartendersnow.com and we will make sure you have what you need for that booking. No booking, payout, cancellation, refund, or fee changes. Bartenders: once the photo check is in place, it may need to be completed before you can send or accept booking requests; the check applies only to sending and accepting booking requests. Anyone registering: registration may be open for some kinds of account and not for others. Visitors: none.

Notice. We emailed notice of this change to the email address on every account on the day it was published.

Prior text. The superseded Section 15 and the superseded Section 3.3 sentence are quoted in full above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Cancellation Policy — Section 4.2 (Reliability as a Material Contract Term), the "No Progressive Discipline" paragraph. Version 1.7 → 1.8. Last Updated September 27, 2026 → October 15, 2026. Payment & Cancellation Policies — Part 3, Section 3.2 (Reliability as a Material Contract Term), the same paragraph. Version 1.18 → 1.19. Last Updated stays October 15, 2026. The Effective Date of each document does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, and it is not adverse to anyone: our right to suspend platform access was already in Section 13 and Section 7.6 of the Terms of Service and in Section 10.3 of the User Agreement & Code of Conduct, and this change brings both cancellation documents into line with them. The Terms of Service version is unchanged and no re-acceptance is required. As with every correction, the corrected text is not applied against anyone for any period before this entry.

What the documents said before this date, in their own words. Both documents said: "Consistent with the independent contractor relationship, bartendersNow™ does not impose warnings, suspensions, fines, or other employment-style discipline. The platform's sole remedy is restriction or termination of access."

What they say from this date. Both documents say that bartendersNow™ does not impose fines, financial penalties, or other employment-style discipline, and that none of our responses is a stage in a progressive disciplinary process. They say our enforcement responses are those in Section 10.3 of the User Agreement & Code of Conduct — written notice that conduct violates that Agreement, suspension of platform access (including while we investigate), restriction of platform access, or termination of platform access — and that these are alternatives, not steps in a sequence. They say that if we suspend, restrict, or terminate a Bartender's platform access, we may cancel the Bartender's affected bookings; that cancelling a booking is a platform operation, not a penalty; that any refund or payout consequence of that cancellation is governed by the cancellation policy and our Bartender Payout Policy; and that we do not withhold or forfeit earned compensation as a consequence of a violation.

Why it changed. The paragraph said we do not give warnings or suspend access. Our Terms of Service and our User Agreement & Code of Conduct said the opposite: that we may give written notice of a violation and may suspend platform access, including while we investigate. Our documents should not say two different things about the same subject, so the cancellation documents now say what the Terms and the User Agreement already said, in the same words.

Effect on Hosts, Bartenders, and visitors. Bartenders: what you are paid for work you complete does not change, and neither do our fees, payout percentages, or cancellation tiers. If we suspend, restrict, or terminate your platform access, we may cancel your affected upcoming bookings, and we tell you that when we notify you of the decision. We do not withhold or forfeit compensation you have earned. You can ask us to review an enforcement decision under Section 10.3 of the User Agreement & Code of Conduct. Hosts: nothing changes about your fees, charges, or refunds. Visitors: none.

Prior text. The changed paragraph is quoted in full above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Payment & Cancellation Policies — Part 1, Section 3.1 (What Happens When You Book), and the answer to "Does saving my card affect my available credit?" in the Frequently Asked Questions. Version 1.17 → 1.18. Last Updated stays October 15, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, and adds no obligation. It makes the Payment & Cancellation Policies describe what can already happen when a card is saved. The Terms of Service version is unchanged and no re-acceptance is required.

What the Payment & Cancellation Policies said before this date, in their own words. Section 3.1 of Part 1 ended: "No funds are held or authorized prior to your scheduled charge." Its FAQ answered: "No. Saving a card does not place a hold on your account or reduce your available credit. No funds are held or authorized prior to your scheduled charge."

What they say from this date. We don't charge your card, or hold funds for your booking, before your scheduled charge. When you add or save a card, our payment processor may ask your bank to verify it, and some banks briefly show this check as a small or zero-amount pending authorization, which can reduce your available credit until it drops off on your bank's timing. It is not a charge.

Why it changed. Some banks display a card-verification check as a pending amount. The earlier wording said no hold or authorization of any kind would appear, which was not accurate for those cardholders.

Effect on Hosts, Bartenders, and visitors. Hosts: nothing changes about what you pay or when. If your bank shows a small pending amount after you save a card, that is the verification check, not a charge. Bartenders and visitors: none.

Prior text. The changed lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Payment & Cancellation Policies — Part 1, Section 4.2 (Card Validity Monitoring), replaced in full; Part 2, Section 2.2 (Card Becomes Invalid Before Scheduled Charge); and the matching row of the Part 2, Section 3.1 grace period table. Version 1.16 → 1.17. Last Updated stays October 15, 2026. Payment Failure Policy — Section 2.2 (Card Becomes Invalid Before Scheduled Charge) and the matching row of the Section 3.1 grace period table. Version 1.8 → 1.9. Last Updated stays October 15, 2026. The Effective Date of each document does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, it does not reduce any notice we actually send, and it conforms both documents to how the platform already works. The 24-hour period these sections described had no consequence of its own: in both documents, nothing happened at its end, and an unresolved card problem has always been handled at your scheduled charge. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date, in their own words. Section 4.2 of the Payment & Cancellation Policies said: "If your stored card becomes invalid before your scheduled charge (expiration, reported lost or stolen, issuer-side changes):" followed by three points: "You will receive a notification via email, SMS, and in-app", "You have the opportunity to update your payment method before the scheduled charge" and "If not resolved before the scheduled charge, our Payment Failure Policy applies". Section 2.2 of Part 2 of the Payment & Cancellation Policies, and Section 2.2 of the Payment Failure Policy, said: "You receive immediate notification (email, SMS, in-app) when we detect the issue" and "You have 24 hours (or until your scheduled charge, whichever comes first) to update your payment method". They gave the grace period as "24 hours from the first detection or notification, not to extend beyond your scheduled charge" (Payment & Cancellation Policies) and "24 hours from the first detection or notification, not to extend beyond your scheduled payment trigger" (Payment Failure Policy), and each document's grace period table listed it as "24 hours" (Payment & Cancellation Policies) and "24 hours (or until scheduled charge)" (Payment Failure Policy).

What they say from this date. Section 4.2 of the Payment & Cancellation Policies says that before your scheduled charge we may check that the card saved for your booking can still be used, and that a card check never charges your card. If your saved card appears to have become invalid, we will notify you in the app and by email, and by text message if you have given us a mobile number and have not turned off text notifications; you can still update your payment method before the scheduled charge, and if it is not resolved before the scheduled charge, our Payment Failure Policy applies. It adds that a card check can only tell us whether a card is still open and usable, not whether it will have enough available credit or funds when your charge is made, so a card that passes a check can still be declined, and that keeping your payment method current is your responsibility. Section 2.2 of both documents says that if we detect the issue, we notify you in the same way, that you can update your payment method at any time before your scheduled charge, and that the grace period runs until your scheduled charge. The grace period tables say the same.

Why it changed. We may check the card saved for your booking before your scheduled charge, without charging it. The old wording promised a text message in every case, but we can only send one when you have given us a mobile number and have not turned text notifications off. It described a 24-hour deadline after we detect a problem that we do not apply: you can update your card at any time until your scheduled charge. And it did not say that a check cannot see whether a card will have enough credit or funds on the day, so it could be read as a promise that every card problem would be caught in advance.

Effect on Hosts, Bartenders, and visitors. Hosts: if a check of your saved card does not go through, we tell you in the app and by email, and by text message where you have given us a mobile number and have not turned text notifications off, and you can update your card at any time before your scheduled charge. Nothing changes about when you are charged or how much. Bartenders and visitors: none.

Prior text. The changed lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Payment & Cancellation Policies — Part 1, Sections 1 and 2.1, and Part 2, Section 2.3 ("When it happens"). Version 1.15 → 1.16. Last Updated September 27, 2026 → October 15, 2026. Payment Failure Policy — Section 2.3 ("When it happens"). Version 1.7 → 1.8. Last Updated September 13, 2026 → October 15, 2026. No Effective Date moves.

Classification: minor correction. No fee, payout, cancellation, refund, dispute-resolution, or data-practice term changes. It is not adverse to anyone, because the Terms of Service — which govern if these Policies conflict with them — already measured the 48 hours from your Bartender's scheduled arrival. It conforms these documents to the Terms of Service and to the Cancellation Policy, which says the same. The Terms of Service version is unchanged and no re-acceptance is required.

What the Policies said before this date. Your stored payment method was charged "automatically 48 hours prior to the scheduled event start time," or "immediately upon booking confirmation for short-notice bookings placed within 48 hours of the event"; you were charged "48 hours before your event (when modifications lock)"; and "At 48 hours before your event, we attempt to charge your card."

What they say from this date. Your card is charged at the earliest of: 48 hours before your Bartender's scheduled arrival time; a Host-initiated cancellation, subject to applicable cancellation fees; or, for a short-notice booking (any event less than 48 hours from your Bartender's scheduled arrival), when the booking is confirmed — when the Bartender you requested accepts, or when you accept a Bartender's request. Sending a request does not itself charge your card. Modifications lock, and we attempt the charge, 48 hours before your Bartender's scheduled arrival time.

Why it changed. These sentences measured the 48 hours from the event start, which contradicted the rest of the Payment & Cancellation Policies and the Terms of Service, both of which measure it from your Bartender's scheduled arrival. The Terms of Service govern, so they are what applied.

Effect on Hosts, Bartenders, and visitors. None to when cards are charged: the platform charges 48 hours before the Bartender's scheduled arrival. If your Bartender is scheduled to arrive before your event starts, to set up, the 48 hours are counted from that arrival — so the charge, and the point after which you can no longer modify your booking, come that much earlier than the event start alone would suggest. Visitors: none.

Prior text. The changed lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Sections 2.1 (Personal Information You Provide), 3.1 (Platform Operations), 4.1 (Between Platform Users), 5.1 (Retention Periods), 12.2 (Categories of Personal Information) and 12.3 (Business Purposes for Collection). Last Updated September 27, 2026 → October 8, 2026. The Effective Date does not move.

Classification: a new disclosure, published with the feature it describes. Hosts can now add safety notes to an event — allergies, service instructions, whether guests under 21 will attend, venue access and timing — for the Bartenders booked for it. Notes can include health information about a Host's guests, such as an allergy, which California law treats as sensitive personal information. Nothing collected before this date is used differently. We do not sell or share safety notes. It moves no fee, payout, cancellation, refund, or dispute-resolution term. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. It did not describe safety notes, because the feature did not exist.

What it says from this date. It lists safety notes among the information Hosts provide, and says they may include health-related information about guests. It says we show a Host's safety notes to each Bartender only while that Bartender's booking for the event is confirmed; that Bartenders who are browsing events, who have only applied, or whose booking was cancelled or has been completed cannot see them; that we do not put them in emails, push-notification text, public event listings, or analytics; and that our support staff may view them only to investigate a safety incident, a dispute, or a report involving the event, or to respond to a privacy request. It says we delete the contents 30 days after the event ends or, if the event is cancelled, 30 days after it is cancelled, keeping only a record that notes existed, when and by whom they were changed, and which kinds of notes were changed, unless a legal hold, investigation, dispute, or legal claim involving the event requires us to keep them longer. It lists health information in safety notes as sensitive personal information and says we use it only for these purposes.

Why it changed. A Bartender serving at an event may need to know about a guest's allergy, how the Host wants service paced, or whether guests under 21 will attend. Safety notes give Hosts a way to tell the booked Bartenders, and the Privacy Policy now describes what happens to that information.

Effect on Hosts, Bartenders, and visitors. Hosts: adding safety notes is optional. Please describe situations rather than people, and do not include your guests' names or contact details. Bartenders: you can read a Host's safety notes while your booking for the event is confirmed. Visitors: none.

Prior text. This entry adds text and removes none. The full text before this date is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 2.2 (Information Collected Automatically, the campaign-parameters item), Section 2.3 (Information from Third Parties, Identity Verification (Stripe Identity)), Section 5.1 (Retention Periods, a new paragraph on identity-verification and identity-change records), and Section 12.1 (California Consumer Rights, Right to Correct). Last Updated September 27, 2026 → October 8, 2026. The Effective Date does not move.

Classification: a new disclosure. The Privacy Policy did not say that we receive the date of birth on your identity document, or how long we keep the records of the age check; it now does. It describes data we already receive, records we already keep, and a correction path we already follow. It collects no new kind of information, and we do not sell or share any of it. It moves no fee, payout, cancellation, refund, or dispute-resolution term, and it is not adverse to anyone. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. Section 2.3 did not say that identity verification returns the date of birth printed on your identity document. Section 5.1 did not describe the records we keep of the age check or of a change to your date of birth, or how long we keep them. Under Right to Correct, Section 12.1 said "Update your information through account settings" and "Contact us for assistance with corrections." Section 2.2 said that the campaign parameters carried by the link you used to reach us "contain no information about you."

What it says from this date. Section 2.3 says that when you complete identity verification, Stripe returns the date of birth printed on your identity document, that we do not receive your document number or images of your document or face, and that the date from your document replaces the date of birth you entered yourself and is used to confirm that you meet the minimum age of 21. Section 5.1 says that we record the result of that age check and keep a separate, unalterable record when it replaces the date you entered, that if identity verification did not return a date of birth we keep the date you entered and the result of the check on the same terms, that we retain these records for eight years after the end of your relationship with bartendersNow™ (or longer where a legal hold, audit, investigation, or legal claim requires it), and that a record of a correction made by our support team is held separately and destroyed twenty-four months after the correction. Section 12.1 says that most of your information can be updated in account settings, that your date of birth is locked there once you complete identity verification, and that to correct it, or a verified legal name or address, you contact us and we verify both the request and the corrected detail before we change it. Section 2.2 says that the campaign parameters describe the link you used, not you, that we discard any value shaped like an email address, phone number, or account identifier, and that we do not use these parameters to identify you.

Why it changed. The Privacy Policy did not say that we receive and use the date of birth on your identity document, or how long we keep the age-check records, and it told verified Bartenders to update a date of birth that account settings do not let them change. The campaign-parameter sentence was broader than what our link-tagging code can guarantee. Each statement now matches what the platform does.

Effect on Hosts, Bartenders, and visitors. None to how the platform works. Bartenders: if the date of birth on your account is wrong after identity verification, contact us rather than account settings, and we will verify the correction before we make it.

Prior text. The superseded lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Privacy Policy — Section 4.1 (Between Platform Users), the "Public Profile Information" passage. Last Updated September 27, 2026 → October 8, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms the document to how the platform already works. Nothing about what we publish changed on this date. What changed is that the Privacy Policy now describes it accurately. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date. Under "Public Profile Information" it listed "Bartender profiles visible to potential Hosts," "Professional credentials and certifications," "Reviews, ratings, and feedback," and "Service offerings and availability."

What it says from this date. A Bartender's profile is public: it can be seen by anyone who visits the Platform, including people who are not signed in and have no account, whether or not the Bartender chooses to be featured in our marketing. The section lists what the profile shows: first name and last initial, a profile photograph once it has been screened, the city and state the Bartender serves, an approximate location within about a mile that is never a street address, rates and the services, equipment, and add-ons offered, skills, languages, bio, and experience, and certifications, shown as self-reported and not independently verified. It says that if a Bartender has not set a working location, the city, state, and approximate location are based on the address they gave us, and that they can set a working location at any time. It says that ratings, reviews, and the number of completed events are shown only to signed-in users and are not part of the public profile, and that we do not publish a street address, email address, phone number, date of birth, or payment details.

Why it changed. "Visible to potential Hosts" named an audience narrower than the real one, and listing reviews and ratings as public overstated what anyone without an account can see. A privacy notice has to be accurate in both directions.

Effect on Hosts, Bartenders, and visitors. None to how the platform works. Bartenders: if you have not set a working location and would rather your home area not be the basis of what your profile shows, set a working location in your profile.

Prior text. The superseded lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Terms of Service — Section 6.8 (Consumable Add-On Characterization). Marketplace Facilitator Compliance — Section 3.2. Each document's Last Updated date moves to 2026-10-08; no Effective Date moves.

Classification: minor correction. No fee, payout, cancellation, refund, dispute-resolution, or data-practice term changes; it is not adverse to anyone; it conforms both documents to the add-ons the platform offers. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. That "Ice Service, Disposable Materials, and Trash & Recycling Disposal add-ons are charges for services performed by the booked Bartender."

What they say from this date. That "Ice Service and Trash & Recycling Disposal add-ons are charges for services performed by the booked Bartender." The rest of each passage is unchanged.

Why it changed. Bartenders no longer offer a Disposable Materials add-on. The Stock List already gives Hosts the cups, napkins, straws, and picks their event needs.

Effect on Hosts, Bartenders, and visitors. No booking ever included this add-on, so none is affected. Hosts supply their own cups and other bar supplies.

---

Documents affected: DMCA & Copyright Policy — "Child Safety & Exploitation Fast-Path Reporting." Last Updated September 27, 2026 → October 5, 2026. The Effective Date does not move.

Classification: minor correction. No fee, payout, cancellation, refund, dispute-resolution, data-practice, or intellectual-property term changes, it is not adverse to anyone, and it does not change how you report. The Terms of Service version is unchanged and no re-acceptance is required.

What the Policy said before this date. When a photo or a message attachment is reported in the app as a child safety concern, "our system is designed to restrict access to it automatically and preserve it while it is reviewed."

What it says from this date. When a photo or a message attachment is reported in the app as a child safety concern, "our system is designed to restrict access to many such reports automatically, and every report is preserved and reviewed promptly."

Why it changed. We may have a person review some reports before access is restricted, to help prevent the report option from being misused to take down content that does not violate our policies. The earlier sentence said that access is restricted automatically for every report. Every report is still preserved and reviewed promptly, and we still report apparent child sexual exploitation to NCMEC as the law requires.

Effect on Hosts, Bartenders, and visitors. None to how you report. If a child is in immediate danger, call 911 first, then report to the NCMEC CyberTipline and in the app.

Prior text. Quoted above; the full superseded text is available on request at legal@bartendersnow.com.

---

Documents affected: Cookie Policy — Section 2.1 (Essential Cookies) and Section 11.1 (Essential Cookies, now headed "Essential Cookies and Similar Storage"). Last Updated September 27, 2026 → October 2, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms the Cookie Policy to how the platform already works. No cookie category changes, no new purpose, no new provider, and no new category of personal information, so we are not asking you for your cookie choices again. The Terms of Service version is unchanged and no re-acceptance is required.

What the Cookie Policy said before this date, in its own words. Section 2.1 gave as examples "Authentication cookies," "Security cookies," "Shopping cart cookies: Remember items in your booking cart," "Load balancing cookies: Distribute server load for optimal performance" and "Accessibility cookies," listed "Session identifiers and authentication tokens" among the data collected, and gave a retention period of "Session cookies expire when you close your browser; persistent cookies expire based on their specific function (typically 1-12 months)." Section 11.1 was a table of four named essential cookies: session_id (user authentication, session), csrf_token (security protection, session), cart_data (booking cart contents, 7 days) and user_prefs (accessibility settings, 1 year).

What it says from this date. Section 2.1 describes essential cookies and similar browser storage by function — authentication, security, booking state, and accessibility — lists "Session identifiers and authentication state" among the data collected, and says that session storage clears when you close your browser and that persistent storage is kept until it is no longer needed for its function, you sign out, or you clear your browser storage. Load balancing is no longer listed. Section 11.1 is headed "Essential Cookies and Similar Storage" and, in place of the table, says that bartendersNow™ uses only strictly necessary first-party cookies and similar browser storage (such as local storage and session storage) to keep you signed in, maintain security, and remember your platform preferences, and that we do not use advertising or cross-context behavioral advertising cookies for these purposes.

Why it changed. Neither our web application nor our marketing website sets the four cookie names that Section 11.1 listed. Most of the essential state in our web application is kept in browser storage (local storage and session storage) rather than in cookies, and the principal storage keys we use are listed in Section 11.5. We also had no evidence that either surface sets a load-balancing cookie, and the "typically 1-12 months" range did not describe anything we set: signed-in state, for example, is kept until you sign out or clear your browser storage. The copy of this policy shown in our app already described essential storage by what it does rather than by cookie name; this entry brings the published policy into line with that approach.

Effect on Hosts, Bartenders, and visitors. None. This entry corrects how the policy describes our essential cookies and storage; it does not change what we collect, how long we actually keep it, or the choices you have, and you will not be asked for your cookie choices again because of this entry.

Prior text. The superseded Section 2.1 wording and Section 11.1 table are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Dispute Resolution Policy — Sections 1.4 (Platform Role in Disputes), 2.1 (Service Quality and Conduct) and 5.3 (Post-Event Quality Complaints). Last Updated September 27, 2026 → September 29, 2026. User Agreement & Code of Conduct — Section 10.1 (Compliance Requirement). Last Updated September 27, 2026 → September 29, 2026. Liability Disclaimer & Limitation — Sections 1.1, 9.1 (California Law Application) and 9.2. Last Updated September 25, 2026 → September 29, 2026. California Alcohol Service Compliance Notice — Section 14.5 (No Discipline or Supervision). Last Updated September 27, 2026 → September 29, 2026. Bartender Payout Policy — Section 11.3 (IRS Form 1099-K Reporting). Version 1.7 → 1.8. Last Updated September 21, 2026 → September 29, 2026. Insurance Requirements Guide — the Executive Summary and the closing note. Last Updated July 20, 2026 → September 29, 2026. The Effective Date of each document does not move. The same sentence in Section 11.3 of the payout part of our Payment & Cancellation Policies will be corrected in a later entry.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms these documents to how the platform already works. It changes nothing about the relationship between bartendersNow™, Hosts, and Bartenders: each document still says that we do not provide bartending services, are not a party to agreements between Hosts and Bartenders, and do not supervise, direct, or control how services are provided. The Liability Disclaimer is still governed by California law. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. The Dispute Resolution Policy said "bartendersNow™ is a marketplace facilitator, not a party to agreements between Hosts and Bartenders," and twice said that bartendersNow™ "is a marketplace facilitator" and is not liable for the quality of bartending services. The User Agreement & Code of Conduct said "bartendersNow™ is a marketplace facilitator and does not supervise, direct, or control how you provide or receive services." The California Alcohol Service Compliance Notice said "As a marketplace facilitator, bartendersNow™ does not" impose fines, require corrective training, or use supervision or progressive discipline. The Bartender Payout Policy began its Form 1099-K section "As a marketplace facilitator utilizing Stripe Connect as our payment settlement partner." The Liability Disclaimer headed Section 1.1 "Marketplace Facilitator Only" and said "WE ARE A TECHNOLOGY PLATFORM AND MARKETPLACE FACILITATOR, NOT A BARTENDING SERVICE PROVIDER." Its Section 9.1 said the Disclaimer is governed by California law, "which provides specific protections for marketplace facilitators and technology platforms," and listed "Civil Code Section 1714 (alcohol liability limitations)," "Business and Professions Code protections for technology platforms" and "Consumer protection law safe harbors for marketplace facilitators." Its Section 9.2, headed "Federal Law Compliance," said the Disclaimer "complies with applicable federal laws, including" Section 230 of the Communications Decency Act, "Electronic Commerce Protection Act provisions" and "Federal Trade Commission guidelines for marketplace platforms." The Insurance Requirements Guide said it "reflects California marketplace facilitator law" and was based in part on "marketplace facilitator regulations."

What they say from this date. Each of those sentences now describes bartendersNow™ as an online marketplace; the rest of each sentence is unchanged. Liability Disclaimer Section 1.1 is headed "Online Marketplace Only" and says "WE ARE A TECHNOLOGY PLATFORM AND ONLINE MARKETPLACE, NOT A BARTENDING SERVICE PROVIDER." Section 9.1 says the Disclaimer is governed by California law, as provided in Section 12.6 of our Terms of Service, and no longer lists protections. Section 9.2, now headed "Federal Law," says that nothing in the Disclaimer limits any protection available to us under federal law, including Section 230 of the Communications Decency Act. Section 3.1 of the Disclaimer continues to describe California Civil Code Section 1714. The Insurance Requirements Guide no longer refers to marketplace facilitator law or regulations.

Why it changed. For the reason given in the entry below: in California, "marketplace facilitator" is a sales and use tax term for a platform that facilitates other sellers' retail sales of goods, and bartendersNow™ arranges bartending services. That entry corrected the Terms of Service and the Marketplace Facilitator Compliance document; this one corrects the same description everywhere else it appeared. The Liability Disclaimer also said that California law gives marketplace facilitators specific protections and consumer-protection safe harbors, and that the Disclaimer complied with an "Electronic Commerce Protection Act." We could not identify a law that says those things — the Electronic Commerce Protection Act was a proposed Canadian law that was never enacted, not a law of the United States — so we removed them rather than describe protections we cannot point to.

Effect on Hosts, Bartenders, and visitors. None. No booking, payout, cancellation, refund, or fee changes, the law that governs our Terms and this Disclaimer does not change, and nothing about how Bartenders work with the platform changes. Form 1099-K reporting is unchanged.

Prior text. The changed lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: Terms of Service — Sections 2.1 (Service Description), 2.2 (Platform Role) and 14 (California Consumer Notices). Last Updated September 27, 2026 → September 29, 2026. Marketplace Facilitator Compliance — Sections 1.2 (Platform Classification), 3.1 (California Sales Tax Requirements), 3.2 (Service vs. Goods Classification), 3.3 (Compliance Procedures) and 6.1 (Transparency Requirements). Last Updated September 25, 2026 → September 29, 2026. The Effective Date of each document does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms both documents to how the platform already works. It changes nothing about the relationship between bartendersNow™, Hosts, and Bartenders: the Terms still say that we do not provide bartending services and do not employ Bartenders, and that Bartenders are independent contractors who operate their own businesses. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. The Terms of Service said "bartendersNow™ is a marketplace facilitator that connects independent contractor bartenders" with event hosts, "WE ARE A MARKETPLACE FACILITATOR, NOT A BARTENDING SERVICE PROVIDER OR EMPLOYER," and "As a California marketplace facilitator, we comply with California Consumer Privacy Act (CCPA/CPRA) requirements and AB 2426 digital goods disclosures." The Marketplace Facilitator Compliance document said "bartendersNow™ operates as a marketplace facilitator under California law" and "We comply with all applicable marketplace facilitator regulations." Its Section 3.1 described the California sales tax registration threshold as "Sales of tangible personal property in California exceeding $500,000 in current or preceding calendar year" that "Applies to facilitated transactions for California delivery," and Sections 3.2 and 3.3 said that no platform transaction counted toward "the California marketplace facilitator threshold described in Section 3.1" and that we reviewed our exposure on the basis that threshold uses.

What they say from this date. The Terms of Service say that bartendersNow™ is an online marketplace that connects independent contractor bartenders with event hosts, and "WE OPERATE A MARKETPLACE; WE ARE NOT A BARTENDING SERVICE PROVIDER OR EMPLOYER." The rest of Section 2.2 is unchanged. Section 14 now says that our Privacy Policy describes how we handle personal information and your rights under the California Consumer Privacy Act, and keeps the statement that digital software tools are licensed on a temporary basis, not sold. The Marketplace Facilitator Compliance document says that we operate a marketplace for bartending services and maintain the compliance measures it describes. Section 3.1 explains that the $500,000 threshold applies to sellers without a physical presence in California, and that because bartendersNow™ operates from California, it would need to register before its first sale if it ever made or facilitated retail sales of goods, whatever the amount. Sections 3.2 and 3.3 say that the platform's transactions are not retail sales of goods, whether by the platform or facilitated through it, and that we review registration requirements, including seller's-permit requirements, with our tax advisors.

Why it changed. In California, "marketplace facilitator" is a sales and use tax term for a platform that facilitates other sellers' retail sales of goods. bartendersNow™ arranges bartending services; it does not sell goods or facilitate their sale. Using the term to describe ourselves said something about us that is not true. The earlier description of the $500,000 threshold also suggested that the threshold would decide whether we must register; for a business operating from California it does not, and the corrected text says so.

Effect on Hosts, Bartenders, and visitors. None. No booking, payout, cancellation, refund, or fee changes, and nothing about how Bartenders work with the platform changes. We did not charge sales tax on bookings before this date and do not after it.

Prior text. The changed lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

---

Documents affected: DMCA & Copyright Policy — "Child Safety & Exploitation Fast-Path Reporting." Last Updated stays September 27, 2026 (it moved to that date in the safety-routing entry below); the Effective Date does not move.

Classification: minor correction. No fee, payout, cancellation, refund, dispute-resolution, data-practice, or intellectual-property term changes, it is not adverse to anyone, and it conforms the Policy to how reporting already works. The Terms of Service version is unchanged and no re-acceptance is required.

What the Policy said before this date. Report such content "immediately using our in-app Child Safety report option or by emailing safety@bartendersnow.com," and child safety reports "trigger immediate content quarantine and public URL revocation, and are escalated directly to our Compliance Officer."

What it says from this date. If a child is in immediate danger, call 911 first. Report the content to the NCMEC CyberTipline (report.cybertip.org or 1-800-843-5678, available 24 hours a day). If it is in a message you received or a photo in a bartender's gallery, also report it in the app — Report message or Report photo, then Child Safety; for anything else on the Platform, email safety@bartendersnow.com. Do not download, copy, forward, or attach the content; tell us where it appears. When a photo or message attachment is reported in the app this way, our system is designed to restrict access to it automatically and preserve it while it is reviewed. We remove or disable violating content, preserve it as the law requires, and report to NCMEC under 18 U.S.C. § 2258A.

Why it changed. Emergency services and NCMEC are available around the clock and our inbox is not. The Policy also described the in-app option without saying where to find it or which content it covers, and described our internal handling more broadly than it applies — automatic restriction happens only for photos and message attachments reported in the app.

Effect on Hosts, Bartenders, and visitors. None to how the platform works. In an emergency, call 911 first.

Prior text. Quoted above; the full superseded text is available on request at legal@bartendersnow.com.

Documents affected: Cancellation Policy — Sections 2.5 and 6.5. Version 1.6 → 1.7. Last Updated September 13, 2026 → September 27, 2026. Payment & Cancellation Policies — the same two passages (Sections 2.5 and 5.5 of the cancellation part). Version 1.14 → 1.15. Last Updated September 21, 2026 → September 27, 2026. Terms of Service — Section 17 (Contact Information). Community Guidelines — Sections 6.1 and 8. Dispute Resolution Policy — Sections 5.1 and 10. User Agreement & Code of Conduct — Section 13. Alcohol Service Compliance — Section 13. Privacy Policy — Section 15. Cookie Policy — Section 10. DMCA & Copyright Policy, Affiliate Disclosure and Legal Resources — contact information. Each document's Last Updated date moves to September 27, 2026; no Effective Date moves.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms these documents to how our contact channels actually work. Every email address still works. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. For a safety concern — including service of alcohol to a minor or to a visibly intoxicated guest — the Cancellation Policy and the Payment & Cancellation Policies said to "contact safety@bartendersnow.com or call (888) 548-9469 right away" and that these concerns were "handled separately and immediately." The Terms of Service listed "Emergency Safety: safety@bartendersnow.com | (888) 548-9469." The Community Guidelines, Dispute Resolution Policy, User Agreement & Code of Conduct and Alcohol Service Compliance listed the same phone number for safety emergencies or urgent safety matters. The User Agreement listed support "Available: Monday-Friday, 8 AM - 6 PM PST," and the Privacy Policy listed our privacy team's availability as "Monday-Friday, 9 AM - 5 PM PST."

What they say from this date. If anyone is in immediate danger or needs medical help, call 911 first. Then email safety@bartendersnow.com as soon as you can safely do so. That inbox is not monitored around the clock. Our phone number is listed as voicemail wherever it appears and is not offered for urgent safety matters. Office hours are removed, and response times are stated as what we aim for.

Why it changed. Our phone line takes voicemail only and is not answered live, and the hours these documents listed did not match the hours our phone greeting gives. A safety emergency — including a concern about alcohol service — needs emergency services first, not a voicemail box.

Effect on Hosts, Bartenders, and visitors. None to how the platform works, and no contact address has changed. In an emergency, call 911 first; then email safety@bartendersnow.com.

Prior text. The changed lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: User Agreement & Code of Conduct — new §4.5 (Profile Photo (Bartenders)) and §5.2 (Prohibited Discrimination). Last Updated September 19, 2026 → September 27, 2026. Community Guidelines — §4.1 (Profile Content) and §4.2 (Photos and Images). Last Updated August 1, 2026 → September 27, 2026. Privacy Policy — §3.1 (Platform Operations) and §3.2 (Safety and Security). Last Updated September 23, 2026 → September 27, 2026. The Effective Date of each document does not move.

Classification: a new standard for Bartenders, with notice before it applies, and a new disclosure in the Privacy Policy. It is not a minor correction: it adds a requirement for Bartenders and describes how we review and use profile photos. It changes no term of the Terms of Service and moves no fee, payout, cancellation, refund, or dispute-resolution term. It collects no new kind of information and shows the photo to no one new: a Bartender's profile photo was already displayed on their public profile. We do not sell or share it, and the review does not use facial-recognition technology. A Bartender who already has an account is emailed before the standard applies to them, and it does not apply to them sooner than 14 days after that email. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. The Code of Conduct had no photo standard, and its list of prohibited discrimination in Section 5.2 began with "Refuse service based on protected characteristics" and did not address how a Host chooses among Bartenders. The Community Guidelines said, for everyone: "Photos: Use clear, professional photos that accurately represent you or your business." Their Section 4.2 said all images shared on the platform should "Be appropriate for a professional business context." The Privacy Policy said we "Screen images you upload for explicit or violent content, using automated tools, before they are displayed publicly," and did not list showing a Bartender's photo to Hosts among the ways we use information.

What they say from this date. New Section 4.5 of the Code of Conduct sets the standard: a recent photo of the Bartender, and only the Bartender, with the full face clearly visible from forehead to chin and nothing covering it — no sunglasses or tinted lenses, masks, filters, heavy editing, logos, or graphics. Religious or medical head coverings are welcome as long as the face is visible, everyday glasses are fine, and a Bartender for whom a disability or religious practice makes the standard hard to meet can contact support@bartendersnow.com. A person on our team reviews each photo before it is shown; if we decline one, we say why, and the Bartender can upload a new one. Once the standard applies, an approved photo is needed to appear in search and to send or accept booking requests. Section 5.2 now says users may not choose, decline, cancel, or rate a Bartender because of a protected characteristic, including how a Bartender appears in their profile photo. The Community Guidelines point Bartenders to that standard and no longer ask anyone for a "professional" photo, and Section 4.2 now says images should "Follow the content rules in Section 4 of our Code of Conduct." The Privacy Policy now says we show a Bartender's profile photo to Hosts, including on the booking and on the day of the event, so the Host can recognize the Bartender who arrives, and that we review images before they are displayed publicly, using automated tools to screen for explicit or violent content and a person to check profile photos against our photo standard.

Why it changed. A Host needs to recognize the Bartender who arrives at their event, and that only works if the photo clearly shows the Bartender's face. Automated screening catches explicit or violent images but cannot tell whether a face is clearly visible, so a person now reviews every profile photo. The standard asks only for what recognition needs; it sets no standard for attire, grooming, hair, makeup, or background. Because a photo shows how someone looks, we also state plainly that a Host may not choose among Bartenders on that basis. This review is not identity verification: it checks the photo against the standard and does not confirm that the photo is of the account holder.

Effect on Hosts, Bartenders, and visitors. Bartenders: once the standard applies to you, you need an approved photo to appear in search and to send or accept booking requests. If you already have an account, we will email you first, and the standard will not apply to you sooner than 14 days after that email. Hosts: you will see a Bartender's photo on the booking and on the day of the event, and you may not choose, decline, cancel, or rate a Bartender because of a protected characteristic, including how they look in their photo. Visitors: none. No fee, payout, cancellation, or refund term changes.

Prior text. The superseded Section 5.2 opening line, Community Guidelines lines, and Privacy Policy line are quoted above. The full superseded text of each affected section is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Liability Disclaimer & Limitation — Section 2.2 (Safety and Security Disclaimer) and Section 4.4 (Third-Party Claims). Last Updated July 20, 2026 → September 25, 2026. Marketplace Facilitator Compliance — Section 6.2 (User Protection Features). Last Updated September 6, 2026 → September 25, 2026. Both changes were published on September 26, 2026. The Effective Date of each document does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms both documents to how the platform already works. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. Under "Identity Verification," Section 2.2 of the Liability Disclaimer listed among the things we are not responsible for "Accuracy of identity verification processes," "Completeness of background checks," "Current validity of professional licenses" and "Ongoing character or conduct of verified users." Section 4.4 listed "Background check limitations or errors" among third-party claims. Section 6.2 of the Marketplace Facilitator Compliance document listed "Professional standards enforcement" among our platform safety measures.

What they say from this date. Under "Identity Verification," Section 2.2 now lists "Accuracy or completeness of the identity verification performed by our third-party provider," "Any screening we do not perform — we do not conduct background checks, criminal-history screening, or reference checks, and we do not verify certifications, licenses, training, or insurance" and "The character, conduct, competence, or fitness of any user, before or after identity verification." The background-check line is removed from Section 4.4; the line for identity verification service errors remains. "Professional standards enforcement" is removed from Section 6.2, with nothing in its place.

Why it changed. bartendersNow™ does not conduct background checks. Every bartender completes identity verification through Stripe Identity before they can accept a booking, and that confirms identity only. Disclaiming the "completeness" or the "limitations" of background checks suggested that we run them, and our Terms of Service say we do not. Listing "professional standards enforcement" as a safety measure also described something we do not do: we do not supervise or direct how Bartenders provide their services.

Effect on Hosts, Bartenders, and visitors. None to how the platform works. Bartenders were not background-checked before this change and are not after it, and identity verification is unchanged. No booking, payout, cancellation, refund, or fee changes.

Prior text. The changed lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com. This entry was added to the log after the change was published.

Documents affected: Accessibility Statement — §3.2 (Keyboard Navigation), §4.2 (Search and Discovery), §9.1 (Accessibility Feedback), §9.3 (Alternative Access Methods), §12 (Contact Information) and §13.1 (This Statement). Last Updated September 23, 2026 → September 24, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms the statement to the features and support we actually offer. Every email address the statement listed still works. The Terms of Service version is unchanged and no re-acceptance is required.

What the Accessibility Statement said before this date. Section 3.2 listed "Keyboard shortcuts for common actions." Section 4.2 listed, for search results, "Skip links for efficient browsing," "Clear pagination with keyboard support," "Bookmark and save functionality" and "Print-friendly result formats." Section 9.3 listed "Phone support for platform functions when needed." Section 12 named an "Accessibility Team" with an "Accessibility Coordinator" available "Monday-Friday, 9 AM - 5 PM PST" and a "Technical Accessibility" contact available "Monday-Friday, 9 AM - 6 PM PST", listed "Live Chat: Available through platform (accessible)" and support "Hours: Monday-Friday, 8 AM - 6 PM PST," and listed urgent@bartendersnow.com under "Emergency Support." Section 13.1 said the statement was available in "PDF format optimized for screen readers."

What it says from this date. Those lines are removed or corrected. Section 3.2 lists its other keyboard items, unchanged. Section 4.2 keeps its search features and the heading structure of results, and now says that more results load automatically as you scroll and that, if you have trouble reaching them with assistive technology, you can email accessibility@bartendersnow.com and we will help. Sections 9.1 and 12 describe our phone number as voicemail. Section 12 lists the same four email addresses by what each one is for, without office hours, and says that urgent@bartendersnow.com is flagged for priority attention but is not monitored around the clock. Section 13.1 says the statement is a web page on our website and in the app, and that we will provide it in another format, such as plain text or large print, on request.

Why it changed. The statement described things we do not have. The platform has no keyboard shortcuts; search results have no pagination, bookmarking, saving, print format, or skip links of their own (the skip-to-content link in Section 3.2 remains); there is no live chat; and there is no PDF of this statement. Our phone line takes voicemail only and is not answered live, and the hours the statement listed did not match the hours our phone greeting gives. We are a small team, without a separate technical accessibility team or round-the-clock coverage. An accessibility statement should describe only what exists, so that people who rely on it can plan accurately.

Effect on Hosts, Bartenders, and visitors. None to how the platform works, and no contact address has changed. If you had planned to use live chat, a PDF, or phone support during business hours, please email accessibility@bartendersnow.com instead; we will help you complete a task on the platform or send you this statement in the format you need.

Prior text. The removed and corrected lines are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Privacy Policy — §2.2 (Information Collected Automatically), §2.4 (Information from Non-Users), §3.4 (Communications), §5.1 (Retention Periods), §8.4 (Email Tracking Technologies), §12.2 and §12.3. Last Updated September 21, 2026 → September 23, 2026. The Effective Date does not move.

Classification: a new disclosure, published before the collection begins. When you ask us to email you a copy of a Stock List from our free tool, you will be able to make two more optional choices: to have us keep the event details you entered when you subscribe to our news and updates, and to let us email you once after your event to ask how the list worked out. Today, none of this is happening — we keep no event details with any email address, and neither choice is offered yet. This entry is the notice that they are about to be; neither goes live until this text is published, and they apply only to choices made after that. No one who asked for a copy or subscribed before this date has had event details kept, so no one's existing information is used differently. It moves no fee, payout, cancellation, refund, or dispute-resolution term, it changes nothing about any account or any message a Host or Bartender receives, the Terms of Service version is unchanged, and no re-acceptance is required.

What the Privacy Policy said before this date. When you asked us to email you a Stock List, we used the event details you entered to produce the copy "and we do not keep those details together with your email address," and we kept your address only if you subscribed to news and updates. Section 2.2 said that if you declined our Performance and Analytics cookie category, or your browser sent a Global Privacy Control signal, "we record nothing about your calculation." It said nothing about a follow-up after your event.

What it says from this date. If you make neither choice, nothing changes: we keep nothing about your calculation with your address. If you subscribe, we also keep the event details you entered — including the event date and the ZIP code or city of your event — with your address, and use them only to fill them in if you create your event with us and to decide which of our news and updates about that event to send you. We delete them at the earliest of the day after your event date, 90 days after our last message about that event, twelve months, or when you unsubscribe or ask us to, and you can ask us to delete them without unsubscribing. If you choose the follow-up, which is a separate optional box, we email you once after your event and keep your address with your event details, keeping the date no more precisely than its month and the area no more precisely than the state and the first three digits of the ZIP code. We delete your address, and its link to those details, no more than 90 days after the follow-up, or twelve months if we never send one; what we keep after that to improve the tool is de-identified, contains no email address, and is kept for no more than 24 months. Section 2.2 now says that declining the analytics category means we record no planning-tool summary, and that this does not override a choice you make here. Section 8.4 now says these messages may carry the same delivery, open, and click measurement as our other email.

Effect on Hosts, Bartenders, and visitors. None to anything about a booking, a payout, a cancellation, or a fee, and none to any message sent to an account holder. For a visitor who makes either choice once it is live, the effect is the one described above.

Prior text. The superseded sentences of Sections 2.4 and 2.2 are quoted above. The full superseded text of each affected section is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Accessibility Statement — §6.3 (Progressive Web App Features). Last Updated August 1, 2026 → September 23, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it conforms the statement to how the app actually works. The Terms of Service version is unchanged and no re-acceptance is required.

What the Accessibility Statement said before this date. Section 6.3 listed "Offline functionality with accessible feedback" among the accessibility features of our web app.

What it says from this date. That line is removed. Section 6.3 lists the other four items, unchanged.

Why it changed. The app has no offline mode to describe. It does not save your information on your device between visits, and saving changes needs an internet connection; if your connection drops while the app is open, information you have already loaded stays on screen, and that is all. An accessibility statement should describe only features that exist.

Effect on Hosts, Bartenders, and visitors. None to how the app works. If you use assistive technology and had planned around an offline mode, please note that saving changes needs a connection, and contact accessibility@bartendersnow.com if that creates a barrier for you.

Prior text. The removed line is quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: This Legal Change Log only — the Administrative and physical safeguards paragraph of the 2026-09-07 entry headed "Security section corrected: the Privacy Policy said our messages were end-to-end encrypted. They are not." No legal document changes. The Privacy Policy, including Section 6.1, is not changed by this entry, and neither is its Last Updated date.

Classification: a correction to this log's own record. It changes no term of any legal document — no fee, payout, cancellation, refund, dispute-resolution, or data-practice term — and it is not adverse to anyone. The Terms of Service version is unchanged and no re-acceptance is required.

What this log said before this date. Explaining why we removed the Privacy Policy's claim of "Incident response procedures and breach protocols" from Section 6.1, the 2026-09-07 entry said "we do not have a written breach-response runbook", and that we would not publish a claim to one while we were writing it.

Why it changed. That statement is out of date. We completed a first version of a written incident-response and breach-notification procedure on September 7, 2026, the same day as that entry, and adopted a reviewed and corrected version on September 23, 2026. This log is meant to be relied on for what we did and when, so it should not carry an out-of-date statement about our own practices. The 2026-09-07 entry now gives the reason that was true at the time — the procedure had not yet been reviewed — and marks the correction where it was made, rather than changing the text quietly.

What this does not change. The removal described in the 2026-09-07 entry stands: Section 6.1 of the Privacy Policy does not list incident-response procedures among our safeguards. This entry corrects the reason this log gave for that removal; it does not change the Privacy Policy. If we add a statement about incident response to Section 6.1, that will be a change to the Privacy Policy, and it will get its own entry here.

Effect on Hosts, Bartenders, and visitors. None. Nothing about how we handle your information changed on this date. What changed is that this log no longer misdescribes one of our practices.

Prior text. The superseded wording is quoted above. The full superseded text of the 2026-09-07 entry is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Bartender Payout Policy — Section 14 (Frequently Asked Questions). Version 1.6 → 1.7. Last Updated September 8, 2026 → September 21, 2026. Payment & Cancellation Policies — the Bartender Payout Questions FAQ. Version 1.13 → 1.14. Last Updated September 8, 2026 → September 21, 2026. Privacy Policy — Section 4.3 (Legal and Safety Requirements). Last Updated September 19, 2026 → September 21, 2026. The Effective Date of each document does not move.

Classification: a minor correction that conforms three documents to what we already do. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to anyone, and it corrects wording that described something we do not do. The Terms of Service version is unchanged and no re-acceptance is required.

What the documents said before this date. Two documents answered "What's the 12% platform fee for?" by listing, among other things, "insurance support." The Privacy Policy's list of who we may share information with, under Safety and Security, read "Insurance providers: For claims processing and verification."

What they say from this date. The fee answer no longer lists "insurance support." bartendersNow™ does not provide, arrange, verify, or support insurance — as our Terms of Service (Section 4.4) and Insurance Requirements Guide have said throughout. The fee still covers identity verification, payment processing, in-app messaging, booking management, customer support, and our algorithms. The Privacy Policy line now reads "Insurance providers: Our insurers, in connection with an incident, dispute, or liability claim involving bartendersNow™," so it is clear we may share information with our own insurer if there is an incident or claim involving the company, and that we do not process or verify your insurance and do not sit between you and any insurer.

Why it changed. The old wording could be read to mean the platform provides insurance or handles insurance claims. It does not: Bartenders and Hosts are independent and responsible for their own coverage, and we do not require, provide, verify, coordinate, or communicate with insurers about your coverage or claims. We corrected the copy to match that.

Effect on Hosts, Bartenders, and visitors. None to any booking, payout, cancellation, or fee — the 12% fee and everything it covers are unchanged — and none to any message you receive. The change is to wording only.

Prior text. The superseded fee-answer wording and the superseded Privacy Policy line are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Privacy Policy — §2.4 (Information from Non-Users), §3.4 (Communications), §5.1 (Retention Periods), §8.4 (Email Tracking Technologies), §12.2, §12.3 and §12.4. Last Updated September 15, 2026 → September 19, 2026. The Effective Date does not move.

Classification: a new disclosure, published before the collection begins. Our free Stock List tool on the marketing website is getting a "Send me a copy" option: you can ask us to email you the list you just generated, and you can separately choose to subscribe to our news and updates. Neither exists for the public yet — this entry is the notice that it is about to, and the option does not go live until this text is published. It moves no fee, payout, cancellation, refund, or dispute-resolution term, it changes nothing about any account or any message a Host or Bartender receives, the Terms of Service version is unchanged, and no re-acceptance is required.

What the documents said before this date. The Privacy Policy described one kind of collection from people without an account besides legal and abuse reports: launch-notification requests. It said nothing about emailing a copy of a planning-tool result to someone who asks for one.

What they say from this date. If you do not have an account and you ask us to email you a copy of a Stock List, we collect your email address and your confirmation that you are 21 or older, we use the event details you entered to produce the copy, and we do not keep those details with your address. If you do not subscribe, we do not keep your address at all. Subscribing is a separate, optional choice that is never pre-selected, you get your copy whether or not you make it, and we do not add you to the list until you confirm by clicking a link in a message we send you. We do not sell or share any of it. Section 5.1 now carries the retention periods, including that we delete an unconfirmed subscription request once it is more than thirty (30) days old. We also corrected one sentence about launch-notification requests, which listed the email address and area but not the age confirmation we have collected with them since September 8, 2026. We also state in Section 8.4 that the copy we email when you ask us for a Stock List, and the message we send to confirm a subscription, carry the same delivery, open, and click measurement as the other email we send, which we use only to confirm that the message you asked for was delivered and worked.

Effect on Hosts, Bartenders, and visitors. None to anything about a booking, a payout, a cancellation, or a fee, and none to any message sent to an account holder. For a visitor who uses the option once it is live, the effect is the one described above.

Prior text. The superseded Section 12.2 sentence is quoted in substance above. The full superseded text of each affected section is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Cookie Policy — §11.5 (heading, introduction, and the bhm-marketing-attribution-v1 row). Last Updated September 12, 2026 → September 19, 2026. Privacy Policy — §2.2 (Information Collected Automatically). Last Updated September 15, 2026 → September 19, 2026. The Effective Date of each document does not move.

Classification: a minor correction plus one new disclosure, and no fresh cookie-consent request. The Cookie Policy change is a scoping correction: Section 11.5 described only our web application, and the storage key it lists is now written by our marketing website as well. The Privacy Policy sentence is a new disclosure of something the Cookie Policy already described, closing a gap between the two documents. No cookie category changes, no new purpose, no new provider, and no new category of personal information, so we are not asking you for your cookie choices again. The Terms of Service version is unchanged and no re-acceptance is required.

What these documents said before this date, in their own words. The Cookie Policy's Section 11.5 was headed "App Storage — Similar Technologies" and its introduction read "The bartendersNow™ web application uses a small number of first-party browser-storage keys (local and session storage) rather than cookies for these functions." The bhm-marketing-attribution-v1 row gave its purpose as "Captures marketing-attribution parameters (e.g., UTM tags) from the link that referred you, for first-party attribution," and its Type read "Functional / analytics (first-party)." The Privacy Policy said nothing about campaign parameters at all: Section 2.2 listed platform usage, location, performance, and analytics data, and no campaign, referral, or attribution information.

What they say from this date. Section 11.5 is headed "App and Marketing-Site Storage — Similar Technologies" and its introduction covers the web application and the marketing website. The bhm-marketing-attribution-v1 row now names the three parameters it holds — utm_source, utm_medium, and utm_campaign — says that we pass them to our app when you continue there, states that it contains no name, email address or account identifier, and names both surfaces. Its Type now reads "Essential / functional (first-party)." The Privacy Policy's Section 2.2 now lists those same campaign parameters under a "Marketing Attribution" heading and states that they contain no information about you.

Why it changed. Our marketing website now keeps the campaign parameters carried by the link you arrived on, for the length of your browser session, and passes them to our app if you continue there, so that we can understand which channels bring people to bartendersNow™. The section that inventories that storage key described only the app, and the key's stated type did not match how we treat it. Both are corrected here, and the Privacy Policy is brought into line with what the Cookie Policy already disclosed.

Effect on Hosts, Bartenders, and visitors. None to anything about a booking, a payout, a cancellation, or a fee, and none to any message you receive. The key is cleared when your browser session ends. Your cookie choices are unchanged, and you will not be asked for them again because of this entry. The re-prompt described in Section 11.4 is triggered when the choices themselves change — a new or re-scoped category, a new purpose, a new provider, or a new category of personal information — and not by every update to this document's date; none of those changed here.

Prior text. The superseded Section 11.5 heading, introduction, and row are quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Privacy Policy — new §8.4 (Email Tracking Technologies), §11.1 (Twilio SendGrid sub-processor row), §12.2 (Internet/Network Activity categories). Last Updated September 13, 2026 → September 15, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to any user, and it conforms the document to a practice already in place (our email provider's standard delivery/open/click measurement). The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before. It disclosed that our email provider (Twilio SendGrid) processes "engagement data" and "email interaction logs," scoped the SendGrid row to "transactional email delivery, account notifications," and, in Section 8 ("Cookies and Tracking Technologies"), described cookies and web beacons on the website. It did not specifically say that the product-and-service (lifecycle) email we send contains an open pixel and click-tracked links.

What it says from this date. A new Section 8.4 explains that lifecycle email contains a small invisible image (a "pixel" or "web beacon") that measures opens, and links that route through our email provider so we can measure clicks; that we use this only to measure whether our own messages are delivered, opened, and acted on; that SendGrid processes it as a service provider; that we do not use it for cross-context behavioral advertising and do not sell or share it; and that turning off product-and-service email also stops the measurement. Section 11.1's SendGrid row and Section 12.2's category list are updated to name email open and click events.

Why it changed. We are turning on delivery/open/click measurement for our lifecycle email and are stating that plainly rather than relying only on the existing "engagement data" language.

Effect on Hosts and Bartenders. None to how any message is sent or how you turn it off. Unsubscribing from product-and-service email — the link in any such message, or your account settings — stops both the messages and their measurement. Transactional messages remain undisableable.

Prior text. The superseded Section 11.1 row and the pre-8.4 state are retained in the version record and available on request at legal@bartendersnow.com.

Documents affected: Privacy Policy §3.4 (Communications) and §7.2 (Communication Preferences), Last Updated September 12, 2026 → September 13, 2026. The Effective Date does not move.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, it is not adverse to any user, and it conforms the document to a practice already in place. The Terms of Service version is unchanged and no re-acceptance is required.

What the Privacy Policy said before this date, in its own words. Section 3.4 grouped our non-transactional email under a heading "Marketing Communications (with consent)" — platform updates and new features, educational content and tips, promotional offers and incentives, and user surveys. Section 7.2 said, of email, "Marketing emails: Can be disabled via unsubscribe or account settings" and "Newsletter and updates: Optional subscription." The word "consent" read as a promise that we ask you to opt in before we send you any of this.

That did not match how the platform has always worked, and we are stating the correction rather than quietly swapping the text. We have never collected a separate marketing opt-in at sign-up. Product and service email — platform updates, tips, re-engagement reminders, our own offers, and surveys — has always been sent to registered account-holders by default, on the account relationship you started when you signed up, with a one-click unsubscribe in every message and an off switch in your account settings. That is an opt-out model, and calling it "with consent" over-stated the basis.

What it says from this date. Section 3.4 now describes this email as "Product and Service Communications (sent on an opt-out basis)", states that we send it to registered account-holders by default, and states that you can turn it off at any time through the unsubscribe link in any such message or in your account settings — and that doing so never affects the transactional messages that are necessary to run the service. A separate heading, "Newsletter and Third-Party Promotional Communications (with your consent)", keeps the true opt-in cases opt-in: a general-interest newsletter, and any message featuring a third party's products, are sent only if you affirmatively opt in. Section 7.2 is rewritten to match. Marketing SMS stays opt-in — nothing about text-message consent changes.

Why it changed. The stated basis should describe what actually happens. Aligning the policy to the opt-out model it has always followed removes an internal inconsistency (the policy already described email as opt-out in Sections 7.1 and 7.2) and lets us describe our first-party email accurately.

Effect on Hosts and Bartenders. None to how any message is sent or how you turn it off: product and service email was, and remains, on by default with a working unsubscribe, and transactional messages remain undisableable. What changes is only the description. Newsletters and any third-party promotional messages remain opt-in, and marketing SMS remains opt-in.

Prior text. The superseded Section 3.4 and Section 7.2 wording is quoted above. The full superseded text is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Cookie Policy §2.2 (Last Updated August 21, 2026 → September 12, 2026) and Privacy Policy §2.2 and §5.1 (Last Updated September 7, 2026 → September 12, 2026). The Effective Date of each document does not move.

Classification: a minor correction plus a new disclosure, with a fresh cookie-consent request. Two different things happened here. The change to the Cookie Policy's Legal Basis line is a minor correction: it removes wording that could be read as saying nothing in this category ever needs a consent gate. The planning-tool summaries described in this entry are gated on your consent, and the line now says so. The paragraphs describing free planning-tool summaries are a new disclosure: they tell you about something we intend to start doing, before we start doing it — and as of this date we are not doing it yet. Because a stored summary of what you typed is a different kind of record from what this category previously described, we are asking for your Performance and Analytics choice again through the cookie banner on our marketing website. The Terms of Service version is unchanged, nothing in the app asks you to accept anything again, and no re-acceptance is required.

What these documents said before this date, in their own words. The Cookie Policy's Performance and Analytics category listed three kinds of data: pages visited and time spent on each page, browser and device information, and feature usage and conversion metrics. Its Retention Period line read, in full, "Used only for internal operational analytics" — a purpose with no period attached to it. And its Legal Basis line read "Business Purpose Exception (Cal. Civ. Code § 1798.140(e)); does not require a consent gate or opt-out." The exception is correctly cited, but the clause after the semicolon could be read as permission to record this category without asking you, and we do ask. The Privacy Policy described our first-party analytics and the coarse location it includes, and said nothing at all about our free planning tools.

What they say from this date. Both documents now describe a de-identified summary of each calculation you run with one of our free planning tools, such as the bartendersNow™ Stock List: the guest counts, the service duration, the occasion, the drinks you selected, any event date you gave us, the quantities the tool recommended, and the state and the first three digits of a ZIP code. They state what such a summary does not contain — no name, no email address, no account, device or session identifier, and no IP address — that we do not link it to you or to your device, and that we do not attempt to re-identify anyone from it. They state plainly that we never store a full ZIP code, a city name, a street address, or a precise device location in one. The Cookie Policy's Retention Period line now carries a period where it had none: an individual summary, and the aggregated counts derived from it, are kept for no longer than 24 months, and the Privacy Policy's retention section says the same in its own terms. The Legal Basis line now says that we gate these summaries on your consent — that we record one only where you have accepted the category through our cookie banner, and that we honor a Global Privacy Control signal.

Why it changed. The law we work to requires that you be told what we collect at or before the point we collect it, and we would rather publish a notice early than start a practice and describe it afterwards. We also narrowed what the notice promises before publishing it: an earlier draft of this disclosure described the region as a city or a five-digit ZIP code, and that was more precise than the purpose needs — for a low-volume event, a date and a five-digit ZIP can point at a household. So the published commitment is the narrower one: the state and three digits, and never a city name. Separately, the Legal Basis line needed fixing at the source rather than being worked around in the new paragraphs, because a sentence that reads as authority to drop the consent gate should not sit above a category we gate.

Effect on Hosts, Bartenders, and visitors. Today, none — we are not recording these summaries yet, and this entry is the notice that we intend to. What changes today is the cookie banner: because the Performance and Analytics category now covers a kind of record it did not cover before, our marketing website will ask for your choice on that category again, and a choice you made before this date is not carried across. If you decline the category, or your browser sends a Global Privacy Control signal, nothing about your calculation is recorded. If you accept it, then once we do begin, what is kept is the de-identified summary described above and nothing more — for no longer than 24 months. Nothing about a booking, a payout, a cancellation, or a fee changes on this date.

Prior text. The superseded Retention Period and Legal Basis lines are quoted in full above. The full superseded text of each affected section is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Payment Failure Policy Section 6.2 (Version 1.5 → 1.6); Payment & Cancellation Policies Part 2, Section 6.2 and Part 4, Sections 8.2 and 8.3 (Version 1.12 → 1.13); Bartender Payout Policy Sections 8.2 and 8.3 (Version 1.5 → 1.6, Last Updated September 7, 2026 → September 8, 2026). All three documents were corrected in the same words on the same day. The two payment policies moved a version earlier the same day for the separate correction recorded in the companion entry below, and move again here — each published correction gets its own version.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term. It is not adverse to any user. It conforms these documents to a practice already in place. The Terms of Service version is unchanged and no re-acceptance is required.

What these documents said before this date, in their own words. The two host-facing payment policies ended their Bartender Payment Protection section with a flat statement: "Bartenders are not told about a Host's payment issues." The bartender-facing sections said the same thing from the other side: "We don't send you updates about a Host's payment problems. If a Host's payment isn't resolved, the booking simply doesn't confirm, or is cancelled — there's nothing for you to act on." And both documents told Bartenders, of a booking cancelled for non-payment, "You are not notified of the failed payment itself."

That was not accurate, and we are stating it rather than quietly swapping the text. When a booking is cancelled because a Host's payment could not be collected, we send the Bartender a notification headed "Booking Cancelled — Payment Issue" which tells them the booking was cancelled because the host's payment could not be collected, that they have been released, and that no payout applies. It also invites them to contact support if being released left them out of pocket. So the closing line "there's nothing for you to act on" was wrong twice over: it said we send nothing, and it told a Bartender there was nothing to do at the exact moment we were pointing them at support.

What they say from this date. The host-facing policies now say we do not share a Host's payment method or billing details with their Bartender, and that if a booking is cancelled because payment was not collected, the Bartender is told the booking was cancelled, that the payment was not collected, and that no payout applies. The bartender-facing sections say the matching thing: we do not pass on a Host's payment details or the steps they are taking to resolve a problem, and if a booking is cancelled for non-payment we tell you that, that the payment was not collected, and that no payout applies — and if being released left you out of pocket, contact support.

Read this narrowly, because we mean it narrowly. This says Bartenders are told when a booking is cancelled for non-payment. It does not say Bartenders are notified of a Host's payment problems generally. A payment difficulty a Host resolves inside the grace period is not announced to their Bartender, and a Host's payment details are still never shared.

Why it changed. A published statement about what our system does has to be true, and this one described a silence our software does not keep. The correction was made on all four sections across three documents at once, and in the same words, because the host-facing and bartender-facing accounts of the same event are deliberately kept aligned so they cannot contradict each other. Fixing one and leaving the others would have left our own policies disagreeing in public, which is worse than a uniform error.

Effect on Hosts and Bartenders. None. The notification described here has been sent since we stopped issuing payouts on non-payment cancellations; nothing about it changed on this date, and what changed is that these documents now describe it. If you are a Host who understood from these policies that your Bartender would never learn a payment had failed, that understanding was wrong, and you should read the corrected sections. If you are a Bartender who was told there was nothing to act on, there is: contact support if a cancellation left you out of pocket.

Prior text. The superseded sentences are quoted in full above and are retained in the version record, available on request at legal@bartendersnow.com.

Documents affected: Payment Failure Policy Section 6.2 (Version 1.4 → 1.5, Last Updated September 4, 2026 → September 8, 2026) and Payment & Cancellation Policies Part 2, Section 6.2 (Version 1.11 → 1.12, Last Updated September 5, 2026 → September 8, 2026). Both documents carry this sentence, and both are corrected in the same words.

Classification: minor correction. It moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term. It is not adverse to any user. And it conforms these two documents to a condition already in force and already published elsewhere — Terms of Service Section 6.6, and Section 15 of the Bartender Payout Policy. The Terms of Service version is unchanged and no re-acceptance is required. Each policy's own version moves by one.

What these documents said before this date. Both describe what happens when a Host's payment fails and the Host resolves it inside the grace period, and both ended that line the same way: "standard process, and your Bartender is paid on the normal schedule." Stated without qualification, that was not accurate, and it has not been since completing payout setup became a step a Bartender takes separately from accepting work.

What they say from this date. The same line now carries the condition that has applied all along: a Bartender is paid on the normal schedule provided their payout setup is complete — and if it is not, their earnings are held for them and released when they finish. The money is not forfeited and it is not ours. It waits with our payment processor until the Bartender completes setup.

Why it changed. Neither of these is the document where a Bartender learns how they are paid; that is the Bartender Payout Policy, which has described the held-earnings condition since it was introduced. But both are read by Hosts, and both gave a Host an account of another person's payment timing that left out a condition we do apply. The right correction is to state the condition, not to keep a clean sentence that is incomplete. These two policies duplicate this section deliberately, so that they cannot disagree with each other; both were therefore corrected in the same words on the same day.

Effect on Hosts and Bartenders. None. Nothing about when or whether anyone is paid changed on this date — the condition described was already in force under the Terms of Service and the Bartender Payout Policy, and what changed is that these two documents now describe it. A Bartender who has completed payout setup is paid exactly as before. A Bartender who has not is in exactly the position they were in the day before: earnings held, and released on completion.

Prior text. The superseded sentence is quoted in full above, and is retained in the version record and available on request at legal@bartendersnow.com.

Documents affected: Privacy Policy §2.2, §5.1, §5.2, §6.1, §11.1 (Last Updated September 6, 2026 → September 7, 2026; the closing line of Section 16 had been left at August 31, 2026 and now carries the same date as the header)

Classification: minor correction. No fee, payout, cancellation, refund, dispute-resolution, or data-practice term changed. None of the practices described below changed either — every one of them was already in place, and what changed is that the document now describes them correctly. That includes the coarse-location disclosure: the measurement it describes was already running, so disclosing it conforms the document to a practice already in place rather than announcing a new one. The Terms of Service version is unchanged and no re-acceptance is required. The Privacy Policy's own version moves from September 6, 2026 to September 7, 2026.

One of these corrections is uncomfortable, and it is named rather than buried. Removing a false statement that our messages were end-to-end encrypted is a minor correction by every element of the test above — it moves no operative term, and your position is identical before and after, because the practice never changed. But a reader who relied on that statement did rely on something we should not have published, and the remedy for that is disclosure, not a fresh click on an acceptance button. That is why this entry states what the policy said, in its own words, instead of quietly swapping the text.

What the Privacy Policy said before this date, and why it was wrong.

Encryption. Section 6.1 listed, as the first of our Technical Safeguards, "End-to-end encryption for sensitive data." That was not true, and we are stating it plainly rather than quietly deleting the line. End-to-end encryption means the provider cannot read the content; we can, and in narrow circumstances we do. It also could not have been true alongside a commitment we take seriously: our child-safety reporting obligations under 18 U.S.C. §2258A require us to read reported message content and report it to the National Center for Missing & Exploited Children. Those two statements cannot both stand, and the reporting obligation is the one that describes what actually happens.

Section 6.1 also claimed "Secure Socket Layer (SSL) for all transmissions" (accurate in substance, but SSL has been superseded by TLS and the corrected text names TLS), "Regular security audits and vulnerability assessments," and "Multi-factor authentication for administrative access." The last two described controls we could not substantiate, so they have been removed rather than reworded.

Administrative and physical safeguards. Section 6.1 claimed "Regular security training for employees" — Midnight Logic has no employees; it is founder-operated. It claimed "Incident response procedures and breach protocols" — our written incident-response and breach-notification procedure had not yet been reviewed, and we were not going to publish a claim to one before it was. (Corrected on September 23, 2026: this sentence originally said we did not have a written breach-response runbook. We completed a first version on September 7, 2026, the same day as this entry, and adopted a reviewed and corrected version on September 23, 2026. The correction is recorded in this log's entry dated 2026-09-23.) And under a heading describing our physical safeguards it listed "Secure data centers with restricted access," "Environmental controls and monitoring," and "Secure disposal of hardware and storage media." We operate no data centre and dispose of no storage media; that security is provided by our cloud provider, and the corrected text says so.

Analytics retention. Section 5.1 said analytics data was "Anonymized and retained for platform improvement," and Section 5.2 said "Some information may be retained in anonymized form for analytics." Neither was accurate. Our analytics event records carry your account and device identifiers for as long as we hold them, and we run no process that anonymizes them. The second sentence was also an open-ended exception to your right to have information deleted, which is not what we do.

One-time codes. Our sub-processor table (Section 11.1) attributed "SMS multi-factor authentication (OTP)" to Twilio. All three parts of that were wrong: the code we send you is an email, not an SMS; it is delivered by SendGrid; and it verifies your email address when you sign up — it is not a second factor when you log in.

Analytics location data. The table's Google Analytics row did not disclose that our analytics measurement includes coarse location.

What the Privacy Policy says from this date.

Encryption. Section 6.1 now describes the protections that actually exist: every connection uses HTTPS with TLS and we require it; stored information is encrypted at rest with AES-256 keys managed by our cloud provider; your card details are tokenized by Stripe under the PCI Data Security Standard and we never store your full card number; and access to systems holding personal information is limited by role, with access to the content of your messages additionally requiring an open, linked abuse report and being written to an audit log. It then states affirmatively that the Platform is not end-to-end encrypted, that encryption in transit and at rest protects your information from outsiders and from other users but does not put it beyond our own reach, and that we will access message content where the law requires it — including our child-safety reporting obligations.

Administrative and infrastructure. Section 6.1 now says only what is true: access to personal information is limited to what a person needs to do their work; personnel and contractors are subject to confidentiality obligations and access controls, with background screening where appropriate and permitted by law; we keep a record of administrative access to message content; and the physical security of the facilities where your information is stored is provided by Google Cloud Platform under its own security programme, not by us.

Analytics retention. Sections 5.1 and 5.2 now say that individual analytics event records are linked to your account and device identifiers while we hold them, that they are not anonymized, and that they are scheduled for deletion 90 days after they are recorded, whether or not your account is active. Aggregated counts — totals that contain no account, device, or session identifier and cannot be traced back to you — are kept after the underlying records are deleted, we keep them only in aggregated form, we do not attempt to re-identify anyone from them, and we require anyone who receives them from us to do the same. We do not otherwise keep an anonymized copy of information you asked us to delete.

One-time codes. The Twilio row now describes what Twilio actually does — operational SMS alerts about your bookings, where those are enabled — and the SendGrid row now names the delivery of the one-time codes used to verify your email address.

Analytics location data. The Google Analytics row and a new paragraph in Section 2.2 disclose that our measurement includes coarse location — the state, the city, and the first three digits of a ZIP code — used to understand where our services are being requested, including areas where we are not yet available. We do not send Google Analytics your full ZIP code, your street address, or precise device location such as GPS coordinates, and we do not use this measurement for advertising.

Effect on Hosts and Bartenders. Nothing about how the Platform handles your information changed on this date; the description of it did. Concretely: your messages were never end-to-end encrypted, so nothing about them is less protected today than it was yesterday — but if you had understood from Section 6.1 that we could not read your messages, that understanding was wrong, and you should read the corrected Section 6.1 before deciding what to put in a message. Your rights are unchanged, including your right to ask us to delete your personal information.

Why it changed. A security representation in a privacy policy has to be true. These were not, and they described a company and a set of controls that do not exist. Publishing a list of security measures is voluntary — nothing requires it — so an inaccurate item on that list is all downside, and the right correction is to narrow the list to what we can stand behind rather than to soften the wording.

Prior text. The superseded text of each affected section is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Privacy Policy (Last Updated August 31, 2026 → September 6, 2026) §§3.2, 4.2, 11.1, 12.1, 12.3

Classification: a minor correction plus a new disclosure. Two different things happened here. The change to the automated-decision line is a minor correction: it moves no fee, payout, cancellation, refund, dispute-resolution, or data-practice term, and it replaces a statement that was not accurate with one that is. The additions describing automated image screening are a new disclosure: they tell you about something we are starting to do, before we start doing it. Neither changes the Terms of Service, whose version is unchanged, and neither asks you to accept anything again. The Privacy Policy's own version moves from August 31, 2026 to September 6, 2026.

What this document said before this date. It described how we use and share your information without mentioning that images you upload are screened by an automated tool before they are shown publicly. Its sub-processor table named Google Cloud Platform / Firebase for hosting, database, authentication and push notifications, and did not name profile photographs among the data categories that provider processes. And under Right to Opt-Out, it listed a right to "opt out of profiling for automated decision-making" — a right we published without ever building a way for you to use it.

What it says from this date. That we screen images you upload for explicit or violent content, using automated tools, before they are displayed publicly — stated in the section on how we use your information, in the section on who we share it with, in the sub-processor table (naming the provider and adding profile photographs and other uploaded images to the data categories), and in the sensitive-information section. A footnote to that table states that the screening classifies an image only: it identifies nobody, analyses no facial geometry, creates and stores no biometric template, that under the provider's terms the images are not used to train the provider's models and are deleted after processing, that we keep only the outcome, and that a photo the automated screen flags is reviewed by a person before any decision is made.

The opt-out line is replaced with what is actually true: we do not use automated decision-making to make decisions producing legal or similarly significant effects concerning you; no automated tool decides whether you may use the platform, appear in search, be booked, or how much you are paid; and if we ever use automated decision-making for a decision of that kind, we will give you notice and a way to opt out before we do.

Why it changed. The automated screen is new, and a sub-processor table that names each provider's function and data categories has to name this one. The opt-out line was the more serious problem: it published a right with no mechanism anywhere in the product, so it promised something we could not deliver. Removing it is not a reduction of what you can actually do — nothing was ever there to use — and it is replaced by a statement of what we do not do, plus a commitment to give notice and a real opt-out before that ever changes.

Effect on Hosts and Bartenders. From this date, a photo you upload goes through an automated check for explicit or violent content before it appears publicly, instead of waiting for a person to look at it — so most photos will appear sooner. A photo the automated check flags is still looked at by a person, and every decline and take-down remains a human decision. This is a content check: it does not confirm that a photo is of you, and it is not identity verification.

Prior text. The superseded text of each affected section is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Bartender Payout Policy (Version 1.3 → 1.4) §§1, 3.1–3.3, 6.2, 7.1–7.2, 10.1–10.2 · Payment & Cancellation Policies (Version 1.10 → 1.11) §§1, 3.1–3.3, 6.2, 7.1–7.2, 10.1–10.2

Classification: minor correction. No fee, payout, cancellation, refund, dispute-resolution, or data-practice term changed. Every dollar figure, percentage, cancellation tier, and payout timing commitment in these documents is unchanged. The Terms of Service version is unchanged and no re-acceptance is required.

What these documents said before this date. That the full price of a booking was your "gross earnings," that our 12% fee was "deducted from" those earnings, and that what reached you was your "net payout." Those three labels appeared in the Key Principles, in the payout formula and both worked examples, in the cancellation and Captain examples, and in the payout receipt and year-to-date dashboard summary described in Section 10.

What they say from this date. The full price of a booking is the "gross service total" — a figure for the job, not a statement of what you earned. Our "platform fee" is retained before your payout, rather than deducted from your earnings. What reaches you is "your payout." This is the same vocabulary your event earnings screens in the app already use. A sentence added to the payout-receipt section explains that your payout counts toward the total reported on your Form 1099-K, that the platform fee is never settled to you and so is not part of that total, and that it is not a further deduction against it.

Why it changed. Our 12% fee is retained before any payment is made to you, so it is never money that reached your account. Calling the pre-fee figure your "earnings," with our fee "deducted" from them, described a payment structure we do not use — and it contradicted the Form 1099-K correction published in the entry below on 2026-09-04, which these documents were meant to match. The labels now say the same thing everywhere.

Effect on Bartenders. None on what you are paid. Your payout is 88% of your service total plus 100% of your tips, on the same schedule, under the same cancellation tiers, with the same rights: the words changed and the money did not. Every worked example keeps its original figures — $400 minus $48 leaves $352; $480 minus $57.60 leaves $422.40; a 50%-tier cancellation of $200 minus $24 leaves $176; a $50 Captain fee minus $6 leaves $44.

Prior text. The superseded text of each affected section is retained in the version record and is available on request at legal@bartendersnow.com.

Documents affected: Terms of Service §6.2 · Bartender Payout Policy §11.3 · Payment & Cancellation Policies §11.3

Classification: minor correction. No fee, payout, cancellation, refund, dispute-resolution, or data-practice term changed. The Terms of Service version is unchanged and no re-acceptance is required.

What these documents said before this date. That amounts reported on IRS Form 1099-K would reflect the total gross service allocations facilitated through the platform prior to platform fee deductions — that is, a Bartender's service total before our 12% fee.

What they say from this date. That reported Form 1099-K amounts reflect the total gross amount settled to the Bartender's connected payout account — the 88% settlement payout, 100% of in-app tips, and any cancellation payout or labor-overage distribution paid the same way. The Host Marketplace Fee and the Platform Retained Fee are not settled to the Bartender and are not included.

Why it changed. The earlier wording described a payment structure we do not use. Our fee is retained before any distribution to a Bartender, so it is never part of a payment made to a Bartender and cannot be reported as one. The corrected wording matches how Bartenders have always been paid and how our reporting has always been configured.

Effect on Bartenders. None on what you are paid: 88% of your service total plus 100% of your tips, on the same schedule, unchanged. Your taxable income is also unchanged — the corrected figure simply excludes a fee that was never paid to you and that you would not deduct.

Prior text. The superseded text of each affected section is retained in the version record and is available on request at legal@bartendersnow.com.