BeSeen Local App Privacy Policy
Updated 13 October 2026. This policy covers the BeSeen Local mobile application.
1. Who handles your data
Bogdan Teleuca, trading as BeSeen Local in the United Kingdom, is the controller responsible for personal data used to operate BeSeen Local. Contact contact@beseenlocal.co.uk for privacy questions, requests or information about our data protection arrangements.
BeSeen Local connects businesses with food delivery drivers who display campaign advertising on their vehicles. This policy explains how information is used in the mobile application.
2. Information used in the application
Account information includes your name, email address, telephone number, postcode, account role, authentication information and, for business users, business details. We record the versions and time of your acceptance of legal documents.
Driver information includes vehicle details and registration, driving licence images or PDFs, vehicle photos, delivery-platform profile screenshots, completed delivery activity evidence, installation photos and review results or notes. Uploads may contain your name, photograph, address, date of birth and licence or platform identifiers. Hide unrelated customer names, addresses, order details and other information we do not need.
Campaign information includes requests, advertising materials, campaign areas and requirements, assignments, acceptance and participation records, administrator reviews and communications.
Payment records include prices, currency, payment and refund status, payment references and recorded driver payout amounts and dates. Checkout payment details are entered directly with Stripe. BeSeen Local does not store full card numbers or card security codes.
We also use notification preferences, device push tokens, device name, platform, app version, notification delivery results, technical or security logs and account-deletion records. Providers may receive IP addresses and request metadata when your device connects to their services.
3. Why information is used
We use account, campaign, assignment and payment information to provide and administer the service and take steps you request before an agreement. The legal basis is performance of a contract or steps before entering a contract.
Verification and security information is used to check driver eligibility, review evidence, prevent misuse and protect users and campaigns. The legal basis is our legitimate interests in operating a reliable and secure service and preventing fraud.
Information required for tax, accounting and other legal duties is processed on the basis of legal obligation. Information needed to establish, exercise or defend legal claims is processed for our legitimate interests in protecting legal rights.
Optional marketing relies on consent where required. You can change available marketing preferences or contact us to withdraw consent. Withdrawal does not affect processing that was lawful before withdrawal.
Required account, verification or campaign information is necessary to use that part of the service. Without it we may be unable to create an account, approve a driver or arrange a campaign. Reading or acknowledging this policy is not consent to every use of personal data.
4. Permissions and review
The camera is used when you choose to photograph verification documents or installed campaign advertising. Photo and file selection is used when you choose to upload evidence. You can refuse or revoke device permissions and use an available alternative upload method.
The app does not track your live GPS location. User-supplied postcodes and campaign areas support area-based campaign administration.
Administrators review drivers, documents, campaigns and installation evidence. Automated checks validate inputs, access permissions, payment status and campaign requirements. We do not sell personal data or use it for personalised third-party advertising.
5. Service providers and access
Authorised administrators review documents and manage campaigns. Participants can access relevant campaign and assignment information according to their role. Driver verification uploads are not published in a public directory.
Supabase provides authentication, database and file storage, and account emails through its configured email services. The primary project region is eu-north-1 in the European Economic Area. Its data processing information is available in the Supabase Data Processing Addendum.
Stripe processes checkout payments, transaction and refund information and related fraud prevention. Stripe may act as an independent controller for parts of its services. See Stripe's Privacy Policy.
Resend delivers application notification emails and receives recipient addresses and message content. See the Resend Data Processing Addendum.
Expo's push service receives push tokens and notification content and routes notifications through Google Firebase Cloud Messaging on Android or Apple Push Notification service on iOS. See Expo's Privacy Policy.
This public policy page is published on beseenlocal.co.uk. The website hosting provider receives technical request information, such as IP addresses, needed to deliver and protect the page. Website cookies and any website analytics are covered by the website's separate privacy and cookie information. This policy describes the mobile application's use of personal data.
We may disclose relevant information where legally required, to investigate fraud or to protect legal rights. We limit disclosure to the information needed for that purpose.
6. International processing and security
Our primary Supabase project data is stored in the EEA. Provider services, support and subprocessors may process information outside the UK or EEA, including in the United States. The primary region does not mean every provider operation occurs only there.
Providers describe the transfer safeguards applicable to their services in the privacy and data processing information linked above. These include adequacy arrangements such as the UK Extension to the EU-US Data Privacy Framework where applicable, and contractual safeguards such as standard contractual clauses and the UK Addendum where required. Contact us for information or a copy of the safeguards relevant to your data where applicable.
We use HTTPS connections, authenticated access and role-based access controls. Driver evidence is held in restricted storage. Access is limited to administrators and providers who need information for the purposes described above. No system can guarantee complete security.
7. Retention and account deletion
Account and verification information is kept while needed to administer your account and relevant assignments. Account settings provides a deletion request with a 30-day grace period. You can cancel during that period before processing begins.
Driver verification files are deleted when account deletion is completed after the 30-day grace period, unless they must be retained for an active campaign, a dispute or a legal obligation. Outstanding campaign or payment obligations may require review before completion. The grace period is not a guarantee that every associated record is erased on day 30.
Campaign, payment and payout records, and a limited deletion audit record, are kept only for as long as needed for legal and accounting duties, disputes and security. Retention is determined by applicable record-keeping requirements, unresolved obligations or claims, and whether records remain needed to investigate misuse or demonstrate deletion. Retained records do not keep a deleted account active.
Installation photos, including replaced submissions, are retained during the campaign. Completed campaigns are reviewed for photo disposal after 90 days, once payments and driver payouts are settled. This is our operational review period, not a statutory requirement to keep every photo. An administrator checks for disputes, investigations or other specific reasons to retain evidence before permanently removing photo files. Where a reason remains, access stays restricted and disposal is postponed for review.
As a sole trader, we retain necessary accounting records for at least five years after the 31 January Self Assessment submission deadline for the relevant tax year. Records may need to remain longer for unresolved enquiries, legal obligations or very late returns. The review date is not an automatic deletion date. After account deletion, the name and business name needed to identify a financial transaction may remain separately with restricted access, together with campaign, payment and payout references and amounts. This accounting archive does not include passwords, device tokens, verification photographs or telephone numbers.
Technical and delivery logs are kept for troubleshooting, delivery verification and security under applicable provider retention settings. Backup copies expire under the provider's backup retention cycle; deletion from active systems may not erase every backup immediately. Payment providers may retain records for their own legal or regulatory duties.
If you cannot access the app, email contact@beseenlocal.co.uk with the subject “Account deletion” and your account email address. We will verify your identity and handle the request under the applicable deletion process. Uninstalling the app does not delete your account.
8. Notifications and local storage
You can manage available email, push and marketing preferences in Account settings and notification permission in your device settings. Account and security messages may still be necessary to operate the service.
Signing out on a device deactivates its registered push token for that account. Signing out everywhere removes the account's registered push tokens. Notifications already dispatched may still arrive.
The app stores authentication session information locally to maintain your sign-in. Signing out clears the app's active sign-in session.
9. Your privacy rights
Subject to the applicable conditions, you can request access, correction, erasure, restriction or portability of your personal data. You can object to processing based on legitimate interests and to direct marketing. Where processing relies on consent, you can withdraw it.
Email contact@beseenlocal.co.uk to make a request. We may need information to verify your identity and understand your request. We will explain any lawful reason why we cannot fulfil a request in full.
You can complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint/. You can contact us first, but you do not have to do so before contacting the ICO.
10. Changes to this policy
We will update this policy when our data practices change. The version and effective date are shown at the top. Where required, material changes will be communicated through the application or a service message.
