1. Information we collect
Account information can include a worker or advocate name, phone number, business or trade, service area, profile photo, account status, payout status, and payment-provider identifiers. Makewrk should not store full card or bank account numbers; payment providers process those details.
Referral and communications data can include link identifiers, taps, inbound phone numbers, call or text channel, timestamps, delivery status, message content needed to route or investigate a contact, attribution status, lead progress, reward status, IP address, user agent, referring page, and campaign parameters.
Security and operations records can include rate-limit events, provider receipt IDs, administrative action, the operator identifier supplied for a sensitive change, and the affected account or record ID. Audit records should not contain card details, verification codes, or message bodies.
2. How we use information
We use information to verify accounts, operate referral links, route contacts, count qualifying contacts, detect fraud, fund and deliver rewards, support subscriptions, answer support requests, secure the service, comply with law, and improve product reliability. We should use aggregated or de-identified data for product analysis when practical.
3. When information is shared
Information can be shared between a worker and their advocate as needed to show link progress and reward status. A prospect's contact is delivered to the worker they chose to contact. We also use service providers for hosting, databases, messaging, phone routing, payment processing, fraud prevention, monitoring, and support. Those providers receive only the information reasonably needed for their role.
We may disclose information to comply with legal process, protect users, investigate abuse, enforce policies, or complete a business transaction subject to appropriate safeguards. Makewrk does not sell personal information for money. Counsel must confirm any jurisdiction-specific definitions of sale, sharing, or targeted advertising before launch.
4. Cookies and link analytics
Makewrk uses encrypted session cookies for account access and can record referral-link activity needed for attribution, abuse prevention, and aggregate analytics. We should not place advertising cookies on personalized referral cards. Product analytics must not receive phone numbers, message bodies, verification codes, or payment credentials.
5. Retention
We keep information only for the time needed to operate accounts, resolve rewards and disputes, prevent fraud, meet tax and accounting duties, and satisfy legal requirements. The current default schedule redacts raw telephony content after 30 days and raw provider and referral-analytics fields after 90 days. Completed background-job data is pruned after seven days. Non-identifying aggregates, append-only operator audit events, account consent, and financial records can be kept longer for security, disputes, accounting, or law. Backup and external log copies can remain for a limited recovery period under their own approved schedules.
6. Security
We use safeguards designed to protect information, including encrypted sessions, access controls, provider signature checks, rate limits, and encrypted transport. No service can promise absolute security. Do not send sensitive medical, financial, or identity documents through a referral text unless a separately approved workflow asks for them.
7. Your choices and rights
You can ask to access, correct, export, or delete personal information by contacting privacy@makewrk.com. We may need to verify the request and retain information required for fraud, disputes, accounting, or law. You can stop promotional messages using the instructions in the message, while operational and security messages can still be required for an active account.
8. Children, locations, and changes
Makewrk is not intended for children under 18. The service is currently designed for United States use; cross-border processing and local privacy obligations require additional review. We will identify policy changes by version and date and request new consent when required.