NSTALZ collects account, role, profile, verification, subscription, swipe, match, chat, notification, report, block, and analytics data needed to operate the two-sided marketplace.

This may include contact details, market ZIPs, service radius, trades, work preferences, company details, portfolio media, and account activity.

Profile details support role-aware discovery and matching. Swipe, match, and message records support marketplace progression, safety limits, and private match-gated conversations.

Users remain responsible for information they choose to place in their profiles and messages.

Insurance and license uploads are used for NSTALZ verification review and are not shown publicly by default.

Private document references use restricted storage behavior where configured. Verification is not a guarantee of skill, quality, safety, timeliness, or outcome.

Authentication is handled through Supabase Auth where configured. For the web app and installable PWA, billing is handled by Stripe or a manual Enterprise agreement.

NSTALZ does not expose provider secrets or store raw payment-card details in its application screens.

Notifications may be sent through email, SMS, and in-app channels where configured. At MVP, chat masks phone numbers and email addresses.

Reports, blocks, and moderation records may be retained and reviewed to protect marketplace users and enforce account restrictions.

Terms and Privacy acceptance is required at signup. Where implemented, NSTALZ logs acceptance with the applicable version, timestamp, and version hash.

Protected marketplace access may be paused when the account has not accepted the current material legal version.

NSTALZ may update its legal documents as the marketplace evolves. Material changes require users to review and accept the current Terms and Privacy Policy before continued protected use.