Acceptable Use Policy

Effective date: 6 October 2026

1 Purpose and scope

SomeBooking helps businesses and their guests manage genuine bookings. This policy sets the rules needed to protect those users, their information and the reliable operation of the service. SomeBooking is operated by HELP TECHNOLOGIES LIMITED, registered in England and Wales under company number 16794762, trading as SomeBooking. SomeBooking is a product of Helplexa. Our registered office is 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ.

Business customers must make authorised staff and contractors aware of this policy and take reasonable steps to ensure compliance. Public bookers must follow the rules relevant to their use of booking pages. The commercial payment obligations, indemnity and liability cap in the business subscription terms do not become obligations of a public booker merely through this policy.

Use only features and integrations actually provided or expressly authorised. Nothing in this policy removes a right that cannot lawfully be restricted, or prevents good-faith complaints, honest reviews, legally protected disclosures or lawful exercise of privacy rights.

2 Genuine businesses and bookings

• Only create or administer a business, group or location if you have authority to do so. Use accurate business details and identify the operator guests are dealing with. Do not impersonate another venue, person, brand or public body, or claim an endorsement or affiliation you do not have.
• Use booking pages for genuine reservations and enquiries. Do not deliberately submit false bookings, occupy capacity you do not intend to use, send disruptive bulk cancellations, automate speculative reservations, manipulate waiting lists or interfere with another business’s availability. Reasonable testing is allowed in an authorised test environment or on your own clearly identified test data without sending unwanted messages or affecting real guests.
• Do not use SomeBooking for fraud, unlawful discrimination, exploitation, harassment, illegal trade or activities prohibited by applicable law. Where a venue lawfully serves alcohol or other age-restricted products, the business remains responsible for licences, age checks and lawful marketing. SomeBooking is not permission to bypass those requirements.

3 Account security and permissions

• Use your own authorised identity. Keep email and Google accounts, verification links, codes, sessions, device PINs and integration credentials secure. Do not access records outside your assigned business, location or role, and do not manipulate custom roles or membership settings to obtain access you have not been granted.
• Do not share a staff identity to evade the Free plan’s one-user allowance or bypass individual permissions and audit records or lend an account to an unauthorised person. Shared tablets and phones must use supported access and locking controls. Do not defeat session expiry, change device settings to bypass access restrictions, or continue using another person’s unattended session.
• Administrators must review permissions, remove departed staff promptly and take reasonable precautions when converting a business into a group or giving group-level access. A business relationship or shared payer is not automatic permission to view another entity’s guest records.
• Promptly report suspected compromise. Do not conceal a security incident, tamper with audit records or knowingly misattribute actions to another person. These duties do not excuse a failure of SomeBooking’s own security obligations.

4 Guest information and sensitive notes

• Collect and use personal information only for lawful, explained purposes. Obtain required permissions and provide appropriate privacy information to guests and staff. Do not upload purchased, scraped, leaked or unlawfully obtained contact lists, or use a booking history as permission to contact people for unrelated purposes.
• Booking notes must be relevant, proportionate and reasonably accurate. Do not record abusive labels, discriminatory comments, unsupported allegations of criminal conduct, or irrelevant intimate information. Limit allergy, health and accessibility information to what is necessary for the guest’s request, establish the required legal basis and special-category condition, and restrict access.
• Do not store full payment card numbers, card security codes, passwords, authentication links, bank-login credentials, identity documents or clinical records in ordinary booking fields, uploads or support conversations. Use the supported Stripe payment flow for payment details. SomeBooking is not designed as a medical record system or general-purpose sensitive document store.
• Do not disclose guest or staff information publicly, to another business, or through an integration unless there is lawful authority and an appropriate purpose. Group membership does not automatically make marketing consent transferable. Secure exported files and delete them when no longer needed. Respect correction, deletion, restriction and objection requests as required by law.

5 Public pages branding and uploaded content

• Publish only content you own or are authorised to use. This includes photographs, logos, menus, descriptions and other material used to style public pages. Do not infringe copyright, trademarks, privacy or other rights, or upload malicious code disguised as an image or document.
• Public descriptions, prices, availability claims and booking conditions must not mislead guests. Do not hide the identity of the actual seller, disguise payment requests or place fraudulent links on a booking page. Do not represent a pending request as a guaranteed booking or a refund instruction as a completed refund.
• Do not publish threats, unlawful hate content, content exploiting children, non-consensual intimate material, or content encouraging violence or serious unlawful harm. Keep public pages connected to the legitimate business and booking purpose of the service.
• Do not place private guest information or internal staff records in publicly visible text or images. Public pages may be indexed or cached, so removing a page may not immediately remove copies held by search engines or third parties.

6 Messages notifications and marketing

• Use booking communications for relevant and expected information about a genuine booking. Identify the sending business accurately. Do not use notifications, booking notes or public-page controls to send spam, phishing, deceptive payment requests, abusive messages or unwanted bulk communications.
• Promotional messages must comply with the law applicable to the recipient and channel. Obtain consent where required or meet every condition of another permitted route. Keep appropriate evidence, respect channel preferences, and provide and honour a simple opt-out. Do not disguise marketing as a necessary booking or security message.
• Do not infer permission to market merely because someone booked a table, gave an allergy note, accepted general terms, enabled device notifications or appears in a group database. Do not import purchased or rented lists for unsolicited campaigns. Respect suppression records and do not re-add someone after they object.
• Only use messaging functions SomeBooking actually provides. A permission to send a booking confirmation does not authorise unrelated bulk campaigns or circumvent a provider’s restrictions. Genuine private feedback requests still need an appropriate lawful basis; promotional review campaigns must also follow applicable marketing rules.

7 Payments deposits and refunds

• Accept deposits or prepayments only for genuine goods or services you are authorised to supply. State the amount, currency, seller identity, cancellation conditions and refund rules before the guest pays. Do not misrepresent a booking deposit, impose undisclosed charges or tell a guest that SomeBooking will fund a refund you owe.
• Do not submit unauthorised charges, test stolen cards, split transactions to avoid monitoring, misstate the business to Stripe, or route another legal entity’s payments through your account without the necessary authority and Stripe’s permission. Comply with applicable Stripe terms and restrictions.
• Do not use payment features for money laundering, sanctions evasion or fraudulent refunds. Promptly investigate genuine complaints and process refunds required by law or your disclosed booking terms. Do not refuse a lawful refund merely because processing fees are not returned to you.
• Keep subscription billing separate from guest-payment responsibilities. An offline booking record is not evidence of a successful charge. Use the processor’s transaction status and supported workflows rather than putting payment credentials into notes.

8 Technical misuse and fair use

• Do not attempt unauthorised access, credential attacks, exploitation, cross-account data access, malware distribution or denial-of-service activity. Do not defeat authentication, rate limits, subscription controls, business limits, staff limits or other safeguards. Do not create repeated free or trial accounts to evade paid limits or a justified suspension.
• Do not scan, penetration-test or load-test production systems without our prior written authorisation. If you discover a suspected vulnerability accidentally, stop before accessing others’ data, collect only the minimum evidence needed and report it privately using section 10. We welcome responsible reports; reporting does not authorise further testing or exfiltration.
• Do not scrape private booking data, harvest personal information, send abusive automated requests, or use the service as unrelated file hosting or computing infrastructure. Approved integrations and reasonable use of your own exports are allowed within their permissions and published limits. These rules do not prohibit ordinary public search indexing where authorised or rights protected by law.
• Unlimited bookings on an applicable paid plan means genuine business bookings without a numerical booking cap. High legitimate booking volume is not itself abuse. We may investigate traffic causing a concrete security or stability risk, apply proportionate temporary controls and work with you on a reasonable solution. This policy does not create an undisclosed booking cap or authorise unagreed extra charges.

9 Offline use and device handling

• Enable offline access only on devices the business can appropriately control. Secure the device, keep the app and operating system updated and restrict access to cached guest information. Do not use offline access to preserve information after your authority has ended or bypass an access restriction.
• Synchronise promptly after connectivity returns, check for failed changes and resolve conflicts. Do not knowingly represent an unsynchronised local change as confirmed by the central system. Do not deliberately exploit stale availability to create conflicting bookings or charges.
• Before disposing of, sharing or reassigning a device, follow the app and device instructions for removing data. Revoking access on the server may not immediately clear a disconnected device. Report loss or suspected exposure promptly. These precautions supplement SomeBooking’s own software-security duties.

10 Reporting and our response

Report abuse or an unlawful public page to [email protected]. Include the page address or booking reference, the nature of the issue, relevant dates and a safe contact method. Do not send unnecessary guest records or full card details. Security concerns can be sent to [email protected].

We assess reports in context and may ask for further information. Depending on severity, we may warn the user, request correction, remove specific content, restrict a function, suspend an account or terminate under the Terms and Conditions. We aim to use the least restrictive effective measure and normally explain the reason and give an opportunity to respond. We may act immediately where needed for security, protection of people or compliance with law.

We may preserve relevant evidence or disclose necessary information where law requires or permits, subject to our privacy and data-protection duties. We do not guarantee that all content is reviewed before publication. We will not knowingly leave confirmed unlawful use unaddressed simply because the customer pays for the service.

If you believe a restriction or removal is mistaken, contact [email protected] with the relevant notice and explanation. We will review the information and correct errors. Legitimate complaints or privacy requests are not grounds for retaliation. Data return and deletion follow the Terms and Conditions and applicable law, rather than automatic destruction as punishment.

11 Changes to this policy

We may update this policy to reflect the service, threats or law. Material changes affecting business customers will follow the notice and termination provisions in the Terms and Conditions; urgent protective changes may take effect sooner where justified. The effective date will appear above. We do not retroactively treat previously permitted conduct as a breach solely because the policy changes.