1. Information you choose to provide
Account and profile information can include your name, email address, role, general neighborhood, languages, schedule pattern, weekly-hour range, compensation range, general child age groups, duties, experience and profile text. Do not place a child’s name, exact home address, school, diagnosis, government identifier, financial account number or medical record in an ordinary profile or message.
2. Marketplace activity
We process job posts, applications, saved items, messages, interview requests and offer details so the people involved can use the matching and hiring experience. Early matching is designed around a general neighborhood rather than an exact address.
3. Trust information
Account access, identity checks, references and background screening are separate signals. If optional verification partners are introduced, their notices will describe the information they collect, their purpose and the consent required before data is sent to them.
4. How information is used
Information is used to operate accounts, let a human moderator compare practical schedule, compensation and care-duty fit, present relevant matches, support conversations and hiring steps, privately return a pilot-review stage when the correct reference and email are supplied, manage follow-up, protect the service, prevent misuse, improve reliability and comply with legal obligations. Structured pilot details do not make an automated hiring decision. Nanny Gigs does not sell profile or care-search information.
5. Referral links
After submitting a pilot request, you may receive a random referral link designed to invite someone on the other side of the marketplace. If that person submits a request, Nanny Gigs records the referral relationship for cohort operations. The referrer cannot see the referred person’s form, email, review status or private details. Nanny Gigs does not ask you to upload contacts; share a link only with someone who has agreed to receive it. No referral reward or review incentive is currently offered.
6. Human-coordinated introductions
An authorized moderator may create a private introduction record between an approved family request and an approved nanny request. The record can include the two request identifiers, contact emails, general fit details already submitted, separate permission timestamps, a contact-handoff timestamp, introduction stage, follow-up date, outcome and a private operational note. Contact-sharing permission expires after 14 days when no handoff occurs and can be revoked. The handoff record does not copy phone numbers, addresses, message content or the conversation. It is not a public endorsement, automated ranking or hiring decision.
7. Private introduction feedback
An authorized moderator may send a family or nanny a single-use feedback link that expires after 14 days. The form does not request an email address; it records what happened, a 1–5 clarity rating, an optional note, a safety-concern flag and the time the notice was accepted. The link itself is stored only as a one-way hash. A safety flag remains in the private moderator queue until its follow-up state is recorded as resolved, with the authorized reviewer and time kept in the audit history. Responses are visible only to authorized pilot operations staff, are not published as reviews or testimonials, do not earn a reward and do not automatically change an introduction outcome, pilot priority or hiring decision.
8. Optional website measurement
Website measurement is off until you choose “Allow useful measurement.” When enabled, the site records anonymous page, call-to-action, app-store handoff, referral-link copy, pilot-funnel milestone and Core Web Vitals events. A pilot-funnel event can show that an account flow began, a family or nanny role was selected, or an account step completed; it never contains the form values or referral code. These events use coarse device and platform categories plus short campaign labels. They do not include names, email addresses, profiles, messages, childcare needs, exact locations or advertising identifiers. The choice is saved only on your device, can be changed from “Measurement choices” in the footer and respects supported browser privacy signals. Launch measurement records are automatically removed after 90 days.
9. Who can see information
Profile and marketplace details are visible only as needed for the relevant product experience. Other members should not receive your private account email through the public profile. Service infrastructure may process information to host and secure the product. When automated form protection is configured, Cloudflare Turnstile processes the limited device and challenge information needed to distinguish ordinary submissions from automated abuse.
10. Retention and deletion
Account data is kept while it is needed to provide the service. The public account-deletion page lets a member request deletion without signing in or immediately delete a signed-in shared account across supported platforms. Pilot requests that do not progress and closed introduction records are removed after their limited operational review periods; private introduction feedback is removed after one year; resolved support records are removed after their operational retention period. Expired feedback links are removed after a short cleanup period, and one-way connection keys used to limit repeated public status lookups are removed after two days. Safety evidence or legally required records may be de-identified or isolated from ordinary product use and retained only for the necessary purpose.
11. Children’s information
Nanny Gigs is for adults arranging or providing childcare. Adults should share only the minimum child-related context needed for a match and should not create accounts for children or publish a child’s exact address, school details or sensitive records.
12. Your choices
You can limit what appears in your profile, choose when to continue a conversation or introduction, decline or omit optional feedback, update your information in the product, change website-measurement preferences and request deletion. Device and browser controls can also limit permissions such as camera access.
13. Changes to this policy
Material changes will be reflected on this page with a new effective date. The policy will be updated before new data uses, payment systems or third-party screening flows are introduced.