use someoneCollect what is needed. Reveal it only when needed.
Use Someone is designed around data minimisation. The information needed to understand a request is not automatically the information that should be shown to another person.
1. Information you provide
Depending on how you use Use Someone, this can include account details, free-text requests, capability descriptions, approximate location, exact job address when required, access instructions, messages, photos, files, credential information, availability, reports and job outcomes.
If you enable a public Capability Passport, Use Someone may publish only the profile fields you have chosen for that purpose, such as your public display name, approximate base area, languages, capabilities and relevant verified trust signals. Your legal identity, home address, email, phone number and credential reference numbers are not public profile fields.
2. Request and capability interpretation
Use Someone may process free text, conversation context and optional images to understand what a Buyer is trying to get done or what a Someone says they can do. AI interpretation is used for understanding and guidance. It does not itself grant legal permission, professional authority or job eligibility.
3. Location privacy
Before commitment, matching should use a suburb, postcode or approximate area where that is enough. For a physical job, an exact Buyer address can be disclosed only to the relevant committed participants when the job requires it. A Someone's home address is not shown to Buyers simply because location data is used for coverage or travel calculations.
4. Messages, files and automatic translation
Job messages can include text, photos and files. If automatic translation is used, Use Someone keeps the original message and stores or displays the translation separately. A translation is labelled as automatic and users can view the original. Reports, blocks and safety actions may require relevant message context to be retained.
A limited pre-commitment question channel may store questions and replies needed to clarify a proposed job before acceptance. It is separate from the private Job Space conversation. Use Someone may retain the original message and any generated translation separately so the original wording remains available.
5. Credentials and verification
For professional or regulated work, Use Someone may need credential details such as credential type, authority, jurisdiction, scope, status and expiry. Public presentation should reveal only the verification outcome needed for the job, not unnecessary credential data.
Credential records may also include the credential category, issuing authority, issue or expiry dates, verification method, verification source and the capabilities or activities to which the credential is relevant. Public surfaces should show only the minimum verification signal needed for the relevant context.
6. Reliability, safety and job history
Commitments, cancellations, no-shows, scope changes, completion outcomes, reports, blocks and appeals may be recorded so capability and reliability can be treated separately and serious decisions can be reviewed.
7. Service providers
Use Someone may use service providers for hosting, authentication, AI processing, email, notifications, analytics and automation. Access is limited to the purpose for which the provider is used. Analytics and similar tools are enabled only when they are actually configured for the service and handled under the applicable privacy settings.
8. Security and access
Account, message, job and file access should be restricted to authorised users and relevant job participants. Administrative access is separate from the public product and sensitive actions should be auditable.
9. Retention and deletion
Use Someone aims to keep personal information only for as long as it is needed for the platform purpose, safety, disputes, fraud prevention, security, legal obligations or legitimate record keeping. Account deletion does not necessarily erase records that must reasonably be retained for those purposes.
10. Questions and privacy requests
Contact contact@usesomeone.au for privacy questions or requests. The privacy obligations that apply to Use Someone will depend on the operating entity, activities and applicable Australian law at the relevant time.
Additional job and recipient data
When a Buyer arranges help for someone else, Use Someone may store limited recipient information such as first name, relationship to the Buyer, whether the Buyer expects to be present, and job-specific information needed for safety and eligibility. We aim to avoid collecting information that is not needed for the job.
Prices, recurring work and resolution records
Use Someone may store service price proposals and agreements, materials allowances, repeat or recurring schedules, reschedule proposals, Resolution Centre cases, responses and evidence notes. Real payment data is not processed by Use Someone unless a payment system is separately activated in the future.
Automated interpretation and decisions
Automated systems can interpret requests, identify possible risks, support eligibility routing and help rank suitable candidates. AI interpretation is kept separate from deterministic rules used for permission-sensitive decisions. We can store the model or rule version, matching reasons and review history so important outcomes can be explained and reviewed.
Fraud and security information
We may record security events and limited fraud-risk signals, such as a message pattern associated with requests for account secrets or unusual payment methods. A risk signal is not automatically a finding that a user acted dishonestly. Serious account action should support review and an audit trail where appropriate.
Files and photo metadata
Job files are private to authorised participants and relevant administrators. Supported images are prepared before upload to remove embedded image metadata where the product can do so. Use Someone does not claim that every uploaded file has been malware-scanned unless a scanning service is actually configured and reports the file as checked.
Trusted contacts and safety check-ins
If a user chooses an optional safety check-in, Use Someone may store a trusted contact and the limited information the user chose to share. A safety check-in is optional and is not continuous location tracking.
Marketing choices and quiet hours
Transactional notices about an account or job are separated from optional marketing communications. Marketing email requires its own choice. Notification preferences can include quiet hours and digests, while urgent security or safety notices may still need to be delivered.
Access, export and retention
Account tools can support requesting an export of Use Someone data. Retention depends on the type of record, account status, safety, dispute and legal requirements. Exact addresses and other sensitive data should not be retained simply because collection is technically possible. Detailed retention periods must be reviewed before production launch and updated as the service changes.