Account information
This can include your name, email address, login details, profile details, and settings connected to your account.
Privacy
Giggly needs certain information to run the marketplace, help buyers and sellers connect, support payments, maintain account security, and respond when problems happen. This page explains that in plain language.
For cookie details, see Cookies. For data-related requests, see GDPR Data Request.
The details below are meant to make the policy easier to understand, not to add unsupported promises.
The information Giggly handles depends on how you use the marketplace. These examples are practical, not an exhaustive list.
This can include your name, email address, login details, profile details, and settings connected to your account.
This can include tasks, offers, messages, reviews, profile content, and activity tied to using Giggly.
Accepted offers, payment status, payout setup, and provider-related payment details may be used to support Giggly's payment and payout flow.
This can include basic device or browser information, cookie choices, site usage, and similar information needed to keep the platform working and understand how it is used.
Giggly uses information for practical marketplace reasons. We keep the wording broad here because exact needs can depend on the task, account, payment state, or support request.
Account details help people sign in, manage profiles, and use Giggly consistently across visits.
Task and offer information lets buyers post work and sellers respond to jobs they want.
Messages and task context help both sides keep scope, timing, and expectations clearer.
Payment-related information helps connect accepted offers, payment status, completion, and seller payout setup.
Some data helps support trust features, reduce abuse, troubleshoot problems, and keep the platform reliable.
Support and data-request details help Giggly understand questions, account issues, privacy requests, or other platform problems.
Privacy is not separate from the marketplace experience. The information users add to Giggly helps other users understand the work, decide who to trust, and keep the task record clearer.
Giggly may rely on third-party service providers to operate important parts of the platform, such as hosting, account access, analytics where accepted, or payment-related functionality.
When that happens, information may be shared to the extent reasonably needed for those services to work. This page does not try to list every provider or describe every technical processing detail.
No private shortcut
Avoid sharing unnecessary personal or payment information with other users outside the platform flow.
You have practical ways to manage some information directly, and you can use the relevant support pages for privacy or data-related requests.
Giggly aims to use reasonable measures to protect user information, but no online service can promise complete security.
Users should also help protect their account by using strong login credentials, being careful with suspicious activity, and keeping unnecessary sensitive information out of public task descriptions.
Retention, in plain language
Information is retained as needed for the service, legal obligations, data requests, and platform safety needs. This page does not promise specific dates or periods.
These habits help keep marketplace information useful without sharing more than needed.
If you have questions about privacy, cookies, or data-related requests, use the most relevant support page so your request reaches the right place.