Last updated September 6, 2026
This policy explains what HelpU collects when you use the app, why, who else touches it, and what you can do about it. It describes the app as it actually works today — not a template.
These documents are currently available in English only. Greek and the other languages HelpU supports will follow once the translations have been reviewed; until then the English text is the one that applies.
Who is responsible
HelpU is the trading name used by __REQUIRED_LEGAL_NAME__, operating as __REQUIRED_LEGAL_FORM_OR_SOLE_TRADER_STATUS__. The controller's geographic address is __REQUIRED_FULL_GEOGRAPHIC_ADDRESS_CYPRUS__. Registration number: __REQUIRED_REGISTRATION_NUMBER_OR_NOT_APPLICABLE__. VAT number: __REQUIRED_VAT_NUMBER_OR_NOT_APPLICABLE__. You can contact the controller at saleemmatar6@gmail.com or __REQUIRED_PUBLIC_TELEPHONE__. HelpU currently operates only in all five districts of the Republic of Cyprus within the government-controlled areas (Larnaca, Nicosia, Limassol, Paphos and the free Famagusta area); selecting a district does not promise that a provider is currently available there.
Any value on this page beginning with __REQUIRED_ is an explicit pre-release placeholder, not a business identity. The production release check fails while any such value remains, so this beta cannot be represented as legally complete until the operator supplies and verifies those details.
What we collect
Only what the app needs to arrange and record a job:
•
Account details — your first and last name, and your email address or phone number, depending on how you sign in.
•
A profile photo, if you choose to add one. It is a picture of your own face, and inside the app it is shown to nobody but you. It is stored at a public link: anyone who has that link can open the picture, and the link goes on working until the file itself is taken down.
•
Addresses — street, unit, area, city and postcode for each address you save, plus any access notes you add. Access notes often contain a gate or door code, which is the single most sensitive thing in the app; it is treated accordingly.
•
Bookings — what you booked, when, with whom, the price breakdown, and any note you attach to the job.
•
Job photographs, if you add them — up to five photographs of the space for a booking. They sit in private storage and are available to you and the provider for that booking.
•
Messages — the messages you send to a provider through the app, and theirs to you.
•
Reviews — your rating, the tags you pick, and any note you write.
•
Safety and moderation records — reports you submit, the account or content reported, your reason and details, accounts you block, and the review decisions and audit events created by the authorised moderator.
•
Preferences — your chosen language and appearance (light, dark or system).
•
Technical and security records — request-rate counters, authentication events and limited hosting or website telemetry used to keep the service secure and diagnose failures.
•
Payment identifiers — the card brand, the last four digits and the expiry, so you can recognise a saved card. Nothing more.
•
If you sign up as a provider — your business or display name, service area, bio, business photo, VAT number if you give one, your services, your team members, and any links to your own website or social accounts that you add.
•
If you sign up as a provider, up to twelve photographs of your work and the captions you write for them. These are meant to be seen: they are shown on your public profile to anyone browsing the app. Each one is stored at a public link too, so anyone who has that link can open the photograph whether or not they use HelpU.
•
If you publish a provider offer, its title, discount, dates and optional marketing photograph. Offer photographs are stored at public links while the underlying object remains.
•
If you sign up as a provider, the documents we ask you to upload so your listing can be checked, and what kind each one is. There is a section on those below, because they are the most sensitive thing in the app.
•
If you receive payouts, the status and identifiers for your Stripe Connect account, whether onboarding requirements are complete, and payout amounts, status and arrival dates. Stripe collects its own identity and bank information under its terms; HelpU stores only the Connect status needed to operate and reconcile the marketplace.
•
If you are a provider and you switch live sharing on while you are travelling to a job, your position at that moment, for as long as that job says you are on the way. One point, overwritten, never a trail.
•
Tips, if you leave one: the amount, the booking it belongs to, and whether the payment went through.
HelpU does not collect your location in the background, does not read your contacts, and does not track you across other apps or websites. The live sharing described below is foreground only and stops the moment the job does; the app asks for no background location permission of any kind, on either platform.
Your card details never reach HelpU
Payments run through Stripe. When you enter a card, it goes from your device to Stripe directly, inside their own payment sheet. HelpU never sees, receives or stores your card number, expiry-plus-CVC pair, or any authentication data. What comes back to us is a token plus the brand, the last four digits and the expiry month and year, which is what the app shows you on the payment methods screen.
Why we are allowed to hold it
•
To perform the contract you entered into — arranging, pricing, delivering and paying for a booking. This covers your account, your addresses, your bookings, your messages and your payments.
•
To comply with legal obligations — bookings are financial records and Cypriot bookkeeping and tax rules require them to be kept.
•
For our legitimate interests — keeping the marketplace safe, preventing fraud and abuse, and being able to investigate a dispute between a customer and a provider. We do not use these interests to profile you or to market to you.
•
With your consent, where the app asks for it — for example before it uses a device permission.
•
Identity, licensing and insurance verification is used to perform the provider agreement, identify businesses trading through the marketplace and protect marketplace safety. The requirement register records the purpose and legal-basis reference for each document kind and service scope.
•
HelpU does not currently request or accept police-clearance, child-protection or other criminal-offence documents. That intake remains paused unless and until Cyprus counsel confirms the specific Cyprus or EU authorisation and safeguards, the requirement register is updated, and the notice and review process are approved. HelpU does not rely on legitimate interests alone for criminal-offence data.
•
A provider's position while they are on the way is shared on their consent, given for that journey and withdrawn by switching it off. It is used for one purpose, which is letting the customer see them approaching.
•
A tip is part of the contract for that booking, and once it is paid it is a financial record we are required to keep.
Who else processes it
The services below may receive data for the stated purpose. Their role depends on the data and service: some act as processors on HelpU instructions, Stripe also acts independently for payment and financial-compliance data it collects itself, and Apple or Google control their app-store billing services.
•
Supabase — hosts the database and the authentication service. The project runs in an EU region, so your account, addresses, bookings, messages and reviews are stored in the European Union.
•
Stripe — processes payments. Stripe is an independent controller for the payment data it collects directly from you, under its own privacy policy, and may process it outside the EEA under the European Commission’s standard contractual clauses.
•
Apple App Store or Google Play — processes a provider’s native Featured subscription, store account and billing transaction under the terms and privacy notice of the store used for the purchase. HelpU receives the product, entitlement and transaction state needed to provide or stop the Sponsored placement, not the store account’s card details.
•
RevenueCat — validates and synchronises Apple App Store and Google Play Featured subscription status for HelpU. It receives the app user identifier, product and entitlement state, transaction identifiers, store, dates and limited device or app metadata needed to provide that service; it does not receive the provider’s store payment-card details from HelpU.
•
Netlify — hosts helpu.cy. The public website currently loads Netlify Real User Monitoring, which receives ordinary web-request and performance data such as IP address, browser information, page and timing data.
•
Expo and EAS — deliver signed app updates and the infrastructure needed to distribute the mobile app. Request, device and update-delivery metadata may be processed when the app checks for an update.
•
OpenFreeMap and its map infrastructure — receive the map-tile and glyph requests needed to draw maps. The saved pin itself remains in HelpU, but an IP address and requested map region accompany ordinary tile requests.
•
Google Maps or Apple Maps — receive the destination only when you choose to open directions in that external app. Their own terms and privacy notice then apply.
•
The authentication, email or SMS provider you choose — receives the identifier and message needed to sign you in or deliver a service message. HelpU must update this list and its transfer record before enabling a provider in production.
HelpU does not sell or rent personal data, use it for another company’s marketing, or use cross-app advertising trackers. This does not mean no third party receives technical data: the hosting, map, update, authentication and payment services above receive what is necessary for their function. The production vendor register records the selected provider, role, region and transfer safeguard before release.
What a provider can see, and when
This is enforced in the database, not just in the app, so it holds no matter what a provider’s device does.
•
While a booking is waiting to be accepted, a provider sees your first name, your area and your city. That is enough to decide whether to take the job.
•
Your phone number, your full street address, your access notes and whatever you typed into the booking’s own notes box are released only once the job is live — accepted and running — and stay available for 24 hours after it ends, so a provider can follow up on the day.
•
After that window, the provider loses access to all of it.
•
Your review is visible with your first name, as reviews are on any marketplace.
Provider verification documents
A provider must complete the currently configured identity, trade, licence or insurance verification scope for the services they offer before the HelpU Checked badge can be granted. The requested scope, legal-basis reference, reviewer and decision are recorded rather than left as an informal checklist. HelpU does not currently request or accept police-clearance, child-protection or other criminal-offence documents.
•
What is collected now: the file, its document kind, upload time, the notice version shown before upload, the service scope that required it, and its review history. Depending on the work, this can be an identity document, trade or professional registration, licence, or proof of insurance.
•
What you see before choosing a file: You are about to upload a private verification file. HelpU records the document type, upload time, review outcome and the file in its private provider-docs storage. Only you and an authorised HelpU reviewer may access it. Identity, licensing and insurance documents are used to verify your listing. HelpU does not currently request or accept police-clearance, child-protection or other criminal-offence documents; that intake remains paused unless and until Cyprus counsel and HelpU approve the exact authority, safeguards, requirement, notice and review process. Replaced and rejected files remain in the review history until the configured retention rule or an approved erasure applies. Do not upload a document that this screen has not requested for your service.
•
Why: identity, trade registration, licensing and insurance are checked to identify the provider and verify the listing. Criminal-record intake remains disabled. It may be considered only after Cyprus counsel confirms the exact legal authorisation and safeguards and HelpU approves the requirement, notice, access, review, retention and erasure process.
•
Where the files sit: a private storage bucket in the same EU hosted project as the rest of the database, under a path tied to your provider account. The bucket is not public, and there is no public link to any file in it.
•
Who can see them: you and an authorised HelpU reviewer. No customer sees a document and no provider can see another provider's file. A provider cannot approve, reject or annotate any document, including their own.
•
What a customer sees instead: one yes or no. HelpU Checked means the provider has a current operator approval for the exact configured requirement set and service scope, and every supporting document remains currently approved. It disappears when the scope, requirement set or evidence changes. It does not expose the documents or warrant the quality of the work.
•
If a document is rejected the reviewer leaves a short reason and you can read it, so rejected is never a dead end. That note is visible to you and to HelpU, and to nobody else.
•
A replaced or rejected file remains in the immutable review history until the applicable verification-retention rule allows removal. The configured period is shown in the retention section. Account deletion withdraws the badge, deletes the active document metadata and puts every private object path into the operator cleanup queue.
•
Your export includes the details of each document you uploaded, but not the scans. Those are sent by a person if you ask for them, because a policy should not be able to hand out an automatic link to a passport scan.
Live location while a pro is on the way
When a provider marks a job as on the way, they can share their position so you can watch them approach instead of guessing. It exists for that one status and nothing else, and the limits below are enforced in the database rather than by the app remembering to behave.
•
It is the provider's choice and it is off unless they turn it on. Sharing needs both the switch and the location permission on their phone.
•
Turning it off really stops it. The app releases the GPS rather than continuing to watch and quietly skipping the upload, and the last point that was stored is removed at the same time, so the map you are watching loses the dot rather than freezing it.
•
It is foreground only. Nothing is shared while their app is in the background or closed.
•
It is one point, not a trail. A single row per booking holds a latitude, a longitude and the time it was written, and every update overwrites the last. A new position goes up roughly every fifteen seconds while sharing is on.
•
It is deleted the moment the booking stops saying on the way. That deletion happens in the same database transaction as the status change, not in a nightly cleanup, so there is no window in which it lingers. There is no history table and there is not going to be one.
•
Only the customer on that booking, and the provider whose phone is sharing it, can read the position, and only that provider can write it. No one else can see where anybody is.
•
The dot on your map is only ever a real reported position, and only a recent one. Nothing is smoothed, interpolated, or slid along a road it was not reported on, and no arrival time is calculated from a distance nobody measured. If about a minute passes with no new position, the dot is removed instead of being left where it was, because a pro whose phone has gone quiet is not somewhere, they are unknown.
•
Your own location is a separate thing and is not part of this. It is used on your device to centre the map while you place a pin on an address, and the only thing that leaves your phone is the pin you save, which goes to the pro who takes your job.
Tips
After a completed job you can add a tip. HelpU takes nothing from it, not a percentage and not a fee. There is nowhere in the database to record a commission on a tip, which is the strongest way we know to say it.
•
What is recorded: the amount, which booking it was for, who paid, who it was for, whether the payment succeeded, and, if the money is ever sent back, how much was refunded and whether a chargeback is open. A tip carries no message and no note, so there is no free text in it at all.
•
The card is handled by Stripe exactly as any other payment, and the card number never reaches HelpU.
•
One tip per booking. A failed attempt is retried on the same record rather than creating a second one, so a single gesture cannot become two charges.
•
The provider sees a total for the tips they received in the last 30 days on their Earnings screen, and nothing more: there is no per-tip line for either of you, no notification, and nothing about the tip on your booking afterwards. The record is kept, and both of you can ask for it.
•
A tip is money that moved, so it is kept as a financial record in the same way a booking is, and it survives account deletion. There is no name, address or note in it to scrub, and removing it would destroy the record rather than protect you.
How long it is kept
Account/profile data is kept while the account is active and then handled under the deletion section. Completed booking, payment, refund, payout, subscription, package and tip records are retained for __REQUIRED_COUNSEL_VALIDATED_FINANCIAL_RETENTION_PERIOD__. Provider-verification material is retained for __REQUIRED_COUNSEL_VALIDATED_VERIFICATION_RETENTION_PERIOD__. Moderation and safety reports are retained for __REQUIRED_COUNSEL_VALIDATED_MODERATION_RETENTION_PERIOD__; security and rate-limit records for __REQUIRED_COUNSEL_VALIDATED_SECURITY_LOG_RETENTION_PERIOD__; and deleted data can remain in backups for up to __REQUIRED_CONFIRMED_BACKUP_ERASURE_WINDOW__. Each placeholder is a production release blocker until counsel and the operator confirm the actual period and the deletion job that enforces it.
We keep only what has a documented purpose for the applicable period. A surviving financial, consent, moderation or deletion record is linked to an internal identifier rather than retaining profile contact details after deletion. The next section explains the current erasure path and its storage cleanup queue.
Deleting your account
You can delete your account from inside the app. If you cannot sign in, https://helpu.cy/account-deletion explains how to submit the same request. Deletion cannot be undone. The database anonymisation is immediate; storage objects that the device could not remove are placed in an operator queue and remain subject to the backup window above. Here is what the current deletion path does:
•
Your name, email address and phone number are cleared from your profile.
•
Your profile photo is removed from storage, so the picture stops being served at its public link. This is the one item on this list that is not guaranteed. The removal is made from your own device, with your own session, in the moments before the account goes, and it can fail: if it does, the fact that there was a photo is recorded and passed to the operator so the file is taken down by hand. Until that happens the picture is still reachable by anyone holding the link.
•
Every saved address is scrubbed in place — street, unit, area, city, postcode and access notes are wiped. The gate codes go.
•
The notes and access notes stored on your bookings are deleted.
•
Your optional onboarding answers are deleted.
•
Job-photo metadata is deleted and the private object paths are added to the deletion queue. Removing the metadata immediately ends the provider’s database-backed access; the operator then removes any object the device did not remove.
•
Your saved payment methods are deleted, and any active HelpU+ subscription billed by Stripe is cancelled so it cannot renew for an account you no longer have.
•
Any of your own bookings that have not happened yet are cancelled with the account, at no charge, and refunded in full to the card that paid.
•
If you were a provider, every customer’s booking with you that has not happened yet is cancelled on the same terms — no charge, refunded in full — the moment your account goes. This reaches people who are not deleting anything themselves, so it is worth telling them yourself before you do it.
•
Any package you bought is cancelled. Every visit in it that has not happened yet is cancelled with it, at no charge, and every session you paid for and did not use is refunded to the card that paid. Deleting your account ends a standing schedule you prepaid for, so this is the one thing here you may want to finish or cancel yourself first.
•
If you sold packages, they are cancelled too, on the same terms. Your customers lose the visits you can no longer perform, and every session they paid for and did not use is refunded to the card that paid. Combined with the bookings cancelled above, this is the largest thing deleting a provider account does to other people, so it is worth telling those customers yourself before you do it.
•
Your messages keep their place in the thread but their text is replaced, so the other person’s conversation does not develop holes.
•
Your reviews keep their score — other customers relied on it, and a provider should not lose their rating because you left — but the written note and the tags are deleted.
•
If you were a provider, your listing is unapproved and de-identified, your services are taken offline, and any website or social links on it go with it.
•
If you were a provider, the photographs of your work are removed from storage on the same terms as your profile photo, and their file paths are recorded and passed to the operator so anything that removal did not finish is taken down by hand.
•
If you were a provider, your offers are taken offline, their user-written titles are replaced, their public photograph links are cleared and the object paths are added to the operator queue.
•
If you were a provider, the active verification-document rows are deleted and the file paths are passed to the operator so the scans themselves are removed from storage. The immutable verification audit retains the document kind, service scope, outcome, reviewer, time and decision reasons for the configured verification-retention period. It does not retain the scan after storage cleanup.
•
Any live position row is deleted outright, even if a booking was left sitting in the on the way state, so an erasure never depends on a trigger having fired.
•
A paid Featured placement is stopped immediately. If Apple or Google bills that subscription, HelpU cannot cancel it for you: deleting the HelpU account does not cancel the app-store subscription, so you must cancel it in the App Store or Google Play to prevent another renewal. The deletion screen offers the store subscription manager before deletion.
•
RevenueCat uses the provider UUID to synchronise Featured status. The current app detaches that identity from the device, but subscriber-record erasure is a separate verified operator process and does not cancel the store subscription. Public release remains blocked until that process is approved and evidenced as __REQUIRED_COUNSEL_APPROVED_EXTERNAL_LEGAL_HOLD_AND_ACCOUNT_ERASURE_PROCESS__.
•
Your block list is deleted. Reports and moderation decisions already filed may be retained under the safety-report period above, attached only to the internal account identifier needed to preserve the audit trail.
•
The immutable record that you accepted or acknowledged a specific legal document is retained with its document version, hash, time and method. It contains no copy of your name, email, phone or address and exists to prove which agreement governed a transaction or provider listing.
•
Your login is permanently disabled: the password is destroyed, the email and phone are released, every session is ended, and the credential is banned. There is no route back in, including password reset and one-time codes.
We keep one deletion record: the internal account identifier, time, whether financial records existed, and the object paths or flags needed to finish storage and external-processor cleanup. Paths cover avatars, business/gallery/offer photographs, job photographs and verification files. Cleanup fields are cleared after the operator verifies removal. The record does not preserve your profile name, contact details, address, messages or the image bytes themselves.
Your rights
Under the GDPR and Cyprus Law 125(I)/2018 you can ask for any of the following, and it is free:
•
Access and portability — write to saleemmatar6@gmail.com and we will send you a machine-readable export covering both sides of your bookings and messages, your profile and addresses, reviews, provider listing and operations, payment/refund/payout and subscription records, package activity, photo metadata, moderation/block records, legal acknowledgements and verification-document metadata. Private document scans are delivered through a separately verified process rather than an automatic public link.
•
Rectification — correct anything wrong, mostly from the profile and address screens.
•
Erasure — delete your account, as described above, subject only to the booking records we are legally required to retain.
•
Restriction and objection — tell us to stop a particular use.
•
Withdrawal of consent, where a use was based on consent, without affecting what happened before you withdrew it.
Write to saleemmatar6@gmail.com for anything the app cannot do for you. We answer within one month.
If you are not satisfied
You can complain to the Cypriot supervisory authority: the Office of the Commissioner for Personal Data Protection (Γραφείο Επιτρόπου Προστασίας Δεδομένων Προσωπικού Χαρακτήρα), Nicosia, Cyprus — dataprotection.gov.cy. You may also complain to the authority in the EU country where you live or work.
Security
Traffic between the app and our servers is encrypted in transit. Access to data is enforced row by row in the database itself, so your rows are reachable only by you and — for the limited window described above — the provider doing your job. This is a young product and we do not claim it is perfect; if you find a problem, please write to us and we will fix it.
Children
HelpU is for adults. It is not directed at children and accounts may not be created by anyone under 18. If you believe a child has given us data, write to us and we will delete it.
Changes to this policy
Each version is stored with a stable document key, effective date and SHA-256 hash. Material changes are shown before they take effect where notice is required, and a fresh acceptance is requested where the change requires agreement. The immutable acceptance history shows which version applied. Older published versions are retained in the legal archive.