YoBeSE Privacy Policy

This notice covers YoBeSE on the website and the YoBeSE Android and iOS applications (MobileAPP). They use the same backend, accounts and marketplace records. Signing out or uninstalling the app does not delete your shared account.

1. Who is responsible and how to contact us

The data controller is Dariusz Dębowski, self-employed / sole trader in the United Kingdom, trading as YoBeSE.

Contact address: 400 Main Road, Sheffield, S9 4QL, United Kingdom.

For privacy questions or data-protection requests, email privacy@yobese.co.uk or write to the contact address above. General contact: contact@yobese.co.uk. Account and service support: support@yobese.co.uk.

2. Information you provide

We process registration and account information such as your name, email address, password credentials, verification status and account roles. Depending on how you use YoBeSE, records include Customer contact and postcode information; Provider business details, service areas, descriptions, availability, prices, team information and verification submissions; Jobs, offers, bookings and invoices; messages, enquiries, reviews, questions and answers; saved searches, saved professionals, notification preferences, reports and blocks.

Uploads may include profile and business images, work examples, Job photos and videos, advertisement artwork and private verification documents. Only upload information you are entitled to share. Private verification documents are reviewed by authorised administrators; they are not public profile images.

3. Technical information and mobile storage

Session identifiers, authentication and verification records, request metadata such as IP information, security events and audit records support access control, fraud prevention, troubleshooting and moderation. The website uses session cookies and browser storage for account and application functions. The mobile app uses secure device storage for authentication and recovery state, and temporary files or caches when selecting, uploading or viewing media. These records are distinct from public profile content.

The app asks for access needed by the media features you choose to use. You can control device permissions in system settings; declining access can prevent the relevant upload. Device permissions do not themselves make your uploads public.

Cookies, first-party analytics and technical logs

Website session cookies keep account access working. Browser application state and cached public assets support navigation and loading. Referral attribution uses the signed cookie described in section 7. With your permission, optional first-party Provider statistics record profile views, search appearances and offer views. Marketplace outcome counts needed for requested services are separate. Deduplication uses hashed identifiers derived from account/session information or an IP-derived value. These identifiers can still relate to you and are treated as personal information. Providers receive their aggregate activity statistics, not a public visitor identity list.

Server diagnostics, security and audit logs support reliability, access control and investigation. The applicable retention criteria are explained in section 9. Where consent is required for optional cookies or similar technologies, the lawful bases below do not replace that requirement.

Your optional privacy choices

Use Privacy choices to Accept optional, Reject optional or Manage choices separately for referral attribution and activity statistics. Rejection is offered alongside acceptance. Essential sign-in, security and storage needed for services you request continue to work. No optional referral or activity tracking is enabled by merely visiting the site, using the app, accepting Terms or confirming that you are 18.

The website remembers your explicit choice in a signed, first-party privacy-preference cookie for up to 30 days, equally for acceptance and rejection. It contains purpose choices, a notice version and decision/expiry times, without an account identifier. This choice record is used to respect your preferences, not for advertising. The separate 30-day referral cookie is set and used only with referral permission; cookies from the earlier implementation do not grant permission.

In MobileAPP, Privacy choices is available alongside the Privacy Policy link. Permission is held only for the current app/account session and resets when the app restarts or the account session changes, or when it expires, no later than 30 days. Browser and app choices are separate. Withdrawal stops future optional processing and clears the browser referral cookie when referral permission is removed; it does not automatically erase records already collected. If a preference change cannot be confirmed, an error is shown rather than claiming it succeeded. Contact us to exercise your rights concerning existing records.

4. Location

Postcodes, towns, service areas and stored geographic coordinates are used for marketplace search and matching. Broad locations may appear publicly; exact private coordinates and private account contacts are not published as public search data. Where postcode lookup through postcodes.io is enabled, that service receives the postcode to return location information. These locations come from marketplace details, rather than background device location tracking.

5. Processing purposes and UK GDPR lawful bases

We use personal information for the following purposes, on the applicable lawful basis:

• Account and requested marketplace services — contract, Article 6(1)(b): registration, sign-in, account roles, requested profile and Job publication, offers, messages, bookings and service/payment administration needed to provide the services you request, or take steps at your request before a contract.
• Security and marketplace integrity — legitimate interests, Article 6(1)(f): proportionate access controls, abuse and fraud prevention, verification review, moderation, audit and service reliability. Our interests are maintaining a safe service and protecting users, balanced against your rights. You may object as explained in section 11.
• Required records and rights requests — legal obligation, Article 6(1)(c), where applicable: processing necessary to meet applicable accounting, regulatory or data-protection obligations.
• Optional activity statistics and referral attribution — consent, Article 6(1)(a): these purposes are off until you allow them. You can refuse either purpose without losing access to YoBeSE and withdraw permission for future processing at any time. Limited administration of referral arrangements and previously collected records may require a separate justified basis and retention assessment.
• Consent, Article 6(1)(a), where required: where an optional activity requires your consent, that consent must be obtained separately. You may withdraw it without affecting the lawfulness of processing before withdrawal.

Accepting this notice, granting an operating-system permission or creating an account is not blanket consent for unrelated processing. If necessary account or transaction details are not provided, the related feature may not be available. Providing optional profile or upload material is your choice.

Service messages and marketing

Account verification, password recovery and service reminders support your account and requested services. In-app notification preferences, including optional saved-search alerts, control those features; they are not blanket consent to marketing. No separate newsletter or marketing-email subscription is offered by the current application. Any future marketing activity requiring consent would need its own valid opt-in and withdrawal process.

6. What other people can see

Published Provider information, approved marketplace content, broad locations and published reviews or questions may be visible to visitors, other users and search engines. Messages, booking information and contact information made available by the marketplace are visible to the relevant participants under the existing access rules. Administrators can access information needed for support, verification, safety and moderation. Publication and paid visibility are separate from identity verification.

Another participant can retain a message or contact detail they have already received. Removing content from YoBeSE cannot guarantee removal of copies downloaded by someone else or cached by an independent search engine.

7. Physical-service invoices, payments and referrals

Where website checkout is enabled, Stripe handles payment collection. YoBeSE stores the purchase, status, amount, currency and payment references needed for fulfilment, invoices and reconciliation; card entry is handled by the payment provider rather than a public YoBeSE profile. Physical-service payment records and digital promotions or credits have distinct rules. Purchases of digital promotions and credits are currently unavailable in MobileAPP.

Physical-service invoices and payment records can include the Customer and Provider identity, invoice number, service description, linked Job or booking, dates, currency, amounts, deposits, balance and payment status. The relevant participants can access their records. These records support service administration, reconciliation, accounting and handling a dispute; they are not public profile data. A booking or invoice record is not itself proof that a payment was collected.

With your referral permission, referral arrangements use a referral code, attribution and event records such as a visit, registration or completed Provider onboarding. The signed website referral cookie has a 30-day attribution lifetime. If you decline, no new optional attribution is recorded. To use a referral after allowing it, follow the referral link again if you are no longer on that page. Account-linked attribution and aggregate partner statistics are separate from that cookie; cookie expiry does not mean every related database record has been deleted.

8. Service providers and disclosures

Hostinger is used for YoBeSE email and hosting administration. YoBeSE uses shared account, database and media-storage services for the website and mobile applications. The application server is hosted in the United Kingdom. Hostinger Email is our established email provider. The exact database and email storage countries, production media-storage provider/location and any replication locations have not yet been confirmed. Stripe receives payment information when you use its hosted checkout. When postcode lookup is enabled, postcodes.io receives the submitted postcode to return location information. Service providers receive information needed for the service they perform. The remaining processing locations and the applicable contractual arrangements remain to be confirmed. Stripe may act as a processor or as a controller for its own purposes, depending on the service and its legal obligations.

Information may also need to be disclosed for a valid legal obligation, a dispute or protection against fraud or security threats. Public advertising placement does not itself grant an advertiser access to private messages or verification documents. Built-in text assistance can provide rules-based suggestions generated on the YoBeSE server.

International processing and transfers

YoBeSE is operated from the United Kingdom. Service providers may process information in other countries. Hosting backups are stored in Germany, outside the UK. Germany is in the European Economic Area, which has UK adequacy recognition. This does not establish every onward processing location or safeguard: other processing destinations and the applicable arrangements with our providers have not yet been confirmed. Hostinger and Stripe publish data-processing and international-transfer terms; their publication alone does not confirm which terms apply to YoBeSE. This candidate does not guarantee UK-only storage. Contact the privacy address in section 1 for information about these arrangements.

9. Retention and deletion criteria

There is no single retention period for every record. Operational account information is used while needed for the account and marketplace relationship. Expiry, cleanup and retention rules depend on the record type and lifecycle state. Deletion removes or anonymises account content, while minimal financial, security, dispute and shared-transaction history may remain with restricted access where justified. Case-specific holds can delay removal of relevant records.

We retain a minimal record of account deletion to help prevent a deleted account from being reactivated when a backup is restored. Media removal may need to be retried, and files shared with other records or subject to a valid hold may remain. Retention decisions take account of the ongoing service relationship, outstanding transactions, applicable legal obligations and the resolution of safety matters or disputes. A complete production retention schedule has not yet been confirmed.

Some records have specific retention criteria: closed safety reports become eligible for minimisation after three calendar months and removal after twelve calendar months, subject to case-specific holds and scheduled cleanup. A deletion confirmation can be recovered for 30 days. That recovery window does not determine how long the minimal record needed to preserve your deletion after a backup restore is kept.

Our Hostinger account is configured for daily automated backups stored in Germany. The full backup coverage, backup-retention, expiry and deletion schedule have not yet been confirmed. Removing information from active records does not mean it is immediately removed from every backup. Records of account deletion support reapplying the deletion if a backup is restored; this does not erase the original backup itself.

10. Deleting your account

Read Delete your YoBeSE account without logging in or reinstalling the app. Sign in through that page to request deletion. In MobileAPP, use Settings → Delete Account. The existing process requires your current password and the confirmation phrase shown on screen.

Deletion applies to both Customer and Provider access across web, Android and iOS. It signs you out across devices and withdraws your Provider profile, contacts, promotions and account media. Complete or cancel current and future bookings first. Ordinary message and review content is removed; minimal history needed by the other party and legally required financial, security or dispute records may remain. Deletion does not issue a refund. Privileged administrator accounts require a separately reviewed process.

11. Your rights and complaints

Depending on the circumstances and lawful basis, UK data protection law provides rights of access, correction, erasure, restriction, portability and objection, and withdrawal of consent where consent is used. These rights are not absolute. Reasonable identity checks may be needed before disclosing or changing account information. Send your request to privacy@yobese.co.uk or the postal address in section 1, identifying the account and the right you wish to exercise. Do not send your password. We may need proportionate information to confirm your identity and locate the relevant records; the applicable statutory requirements govern the response and any justified limitation.

You can complain to the UK Information Commissioner’s Office: ico.org.uk/make-a-complaint. ICO information for the public explains your rights.

12. Security, children and changes

Access controls, authenticated private routes, restricted uploads and audit mechanisms protect information, but no service can guarantee absolute security. Keep your password and device access private. Do not submit another person’s sensitive information without an appropriate reason. YoBeSE is for adults aged 18 and over. This applies to all Customers and Providers on the website, Android and iOS. Registration requires you to confirm that you are at least 18 years old. We rely on your declaration; this is not independent age verification, and we do not collect your date of birth for this declaration. Read the Terms & Conditions — eligibility. If you have a concern about a child’s information on YoBeSE, contact privacy@yobese.co.uk.

Changes to this notice will be shown on this page with their effective date. The proposed date above does not make this candidate an approved policy.