Data We Collect
We collect account data, language preference, provider profile fields, service details, optional prices, location fields, proof-of-work media metadata, contact requests, reports, and support messages users choose to send.
Last updated: July 1, 2026
How Wasta handles account, profile, contact, report, and media data.
We collect account data, language preference, provider profile fields, service details, optional prices, location fields, proof-of-work media metadata, contact requests, reports, and support messages users choose to send.
We use data to operate search, authentication, provider review, messaging, support, safety moderation, reporting, abuse prevention, and account deletion workflows.
Public app access uses Supabase public keys with Row Level Security. Server-only operations use protected backend functions. Service-role credentials are not shipped in Flutter or browser-visible website code.
Signed-in users can request account deletion in the app settings. Deletion removes the auth account and cascades owned app rows where the database schema requires it. Some safety reports may be retained with the reporter identity removed.
For privacy questions, use the support page or email support@wasta.app.