Draft For lawyer review before publication. Prepared 19 Aug 2026. Entity name pending (Q14).
Jelly

Privacy Policy

Last updated: 19 August 2026 · Effective: [LAWYER: effective date on publication]

1. What this covers

This policy explains what [JELLY ENTITY — Q14] (“Jelly”, “we”, “us”) collects when you use the Jelly iPhone app and the Jelly website at onjelly.com, what we do with it, and who else sees it.

It is written to describe what our systems actually do. Where we say we do not do something, we mean the system does not do it.

2. What we collect

2.1 When you create an account

2.2 Your profile

2.3 Delivery details

Addresses and phone numbers are used solely to dispatch and complete a courier delivery. They are never shown to another member and never appear in any listing, order, message or public page.

2.4 What you do on Jelly

2.5 Messages

2.6 If you join the waitlist

2.7 Technical

3. What we do with it

We do not use your information to build advertising profiles, and we do not run behavioural advertising.

4. Who else sees it

4.1 Stripe — payments

Card payments and lender payouts are processed by Stripe. Your card details go to Stripe directly. Jelly never receives or stores your card number. Lender payouts run through Stripe Connect, and Stripe collects the identity and bank details it needs to pay you. Stripe handles that information under its own privacy policy.

4.2 Courier partners — delivery

When a delivery is booked, we send the pickup and drop-off addresses, and a contact phone number, to a courier partner — Uber Direct or DoorDash Drive. A courier needs an address to drive to it.

Jelly is the sender and recipient of record on every leg. The courier receives what it needs to complete the job. Members never receive each other’s addresses or phone numbers.

4.3 Service providers

We use hosting and infrastructure providers to run the app, the API and the website. They process data on our instructions and for no other purpose.

[LAWYER] Name the processors on publication, and confirm each has a data-processing agreement.

4.4 Legal

We may disclose information where the law requires it, or to protect the safety of members or the public, or to establish or defend a legal claim.

4.5 Business transfer

If Jelly is acquired or merges, member information may transfer as part of that transaction.

[LAWYER] Notice obligations on transfer.

4.6 We do not sell your personal information

We do not sell your personal information, and we do not share it for cross-context behavioural advertising. There is no advertising SDK in the Jelly app, no ad network integration in the API, and no advertising or analytics tracker on onjelly.com.

5. What other members see

Other members see, from your profile and your listings:

Other members never see your full name, email address, phone number, or street address. This is enforced in the code: every payload that can reach another member passes through a single shaping layer that strips those fields, and a test asserts it.

6. Mona

Mona is the stylist in the app. What you tell her is used to find Items you can actually book — your size, your dates, your city.

Mona’s replies are produced by Jelly’s own software running on Jelly’s servers. Your conversations with Mona are not sent to a third-party AI provider.

7. Cookies and the website

The Jelly website at onjelly.com sets no advertising cookies and runs no third-party analytics or tracking scripts.

The app stores a session token on your device so you stay signed in. That is not advertising technology and is not shared with anyone.

[LAWYER] Cookie disclosure and consent banner requirements if any analytics, tag manager, or conversion pixel is added before launch — the answer above stops being true the moment one is.

8. How we protect it

No system is perfectly secure.

[LAWYER] Breach-notification obligations, including the New York SHIELD Act’s reasonable-safeguards and notification requirements.

9. How long we keep it, and how to delete an account

We keep your account information for as long as your account is open, and keep transaction records after that where we need them for accounting, tax, fraud prevention and legal claims.

There is no self-serve account deletion in the app today. To close and delete your account, write to [email protected] and we will do it.

[LAWYER] A retention schedule — how long each category is kept after deletion, what is retained for legal or accounting reasons, and what is anonymised rather than erased.

10. Your rights

[LAWYER] This section is a placeholder and must be drafted.

Whatever the final drafting says, the underlying facts are the ones in sections 2 to 5.

11. Children

The Services are for people 18 and over. They are not directed to children, and we do not knowingly collect personal information from anyone under 13. Do not give us the personal information of anyone under 13 — for delivery or for any other reason.

If you believe a child has given us information, write to [email protected] and we will delete it.

12. Where your information is held

Jelly operates in the United States and holds member information in the United States.

[LAWYER] International transfer language if any processor stores or accesses data outside the US — confirm hosting and courier partner regions on publication.

13. Changes to this policy

If we change this policy we will post the new version here and update the date at the top. Where a change is material we will tell you in the app or by email.

14. Contact

[JELLY ENTITY — Q14]
Privacy and support: [email protected]

[LAWYER] Registered business address for publication; and whether a privacy contact separate from support is required.

Internal — remove before publication

Appendix: source map

Provenance: this document is not Pickle-copied. Pickle’s operative Privacy Notice could not be captured (docs/pickle-legal.md §2 — HTTP 429 on every attempt, no Wayback, no usable snippets). Every statement above is a factual description of Jelly’s own system, read off the code. Pickle’s Privacy & Safety FAQ — a help-centre article, not their operative notice — corroborates the shape of several sections and is marked “corroborated” where it does. It is never the source.

§StatementSource
2.1Email, handle, name at signupSystem: auth.js /auth/signup
2.1scrypt hash + per-user salt, constant-time compareSystem: auth.js hashPassword / verifyPassword
2.1Only the first name is shown to othersSystem: pub.js pubUser
2.2Fit profile, fit note, notification prefsSystem: me.js PATCH /me whitelist
2.3Address fields; contact phoneSystem: me.js /me/addresses; auth.js (phone on the user record); services/courier/*.js
2.3Used solely for courier dispatch, never exposedSystem: me.js header comment; pub.js; orders.js. Corroborated by Pickle FAQ (“home address … never shared with other users”)
2.4Orders, listings, reviews, saves, follows, requests, credits, claims, referralsSystem: db.js table list; orders.js, routes.js, claims.js, me.js
2.5Member messages and Mona threads storedSystem: db.js (messages, threads, monaThreads, monaMessages)
2.6Waitlist = email + timestamp onlySystem: routes.js POST /waitlist
2.7Sessions: 30-day sliding expiry, deleted on logoutSystem: auth.js SESSION_TTL_MS, tokenUser, /auth/logout
2.7Failed sign-ins held in memory for rate limitingSystem: auth.js loginFails
3UsesSystem: orders.js, pricing.js, mona.js, notify.js, claims.js
3No advertising profilesSystem: no ad or analytics dependency in apps/api or apps/landing/public
4.1Stripe processes payments; Jelly never stores card numbersSystem: services/payments/stripe.js; no card field in any Jelly table. Corroborated by Pickle FAQ (“All payments are processed by Stripe”)
4.2Uber Direct / DoorDash Drive receive addresses + a phoneSystem: services/courier/uberDirect.js, doordashDrive.js; CSV Q3
4.2Jelly is sender and recipient of recordCSV Q4; system: orders.js
4.3Service providers[LAWYER] — processors not yet named
4.4Legal disclosure[LAWYER] — standard scaffolding
4.5Business transfer[LAWYER] — standard scaffolding
4.6No sale of personal information; no ad trackersSystem: nothing in the codebase transfers member data to a third party except Stripe and the courier providers, both for the transaction itself; index.html loads no third-party script
5What other members seeCSV Q4; system: pub.js, asserted by the anonymity walk in apps/api/test/api.test.js. Corroborated by Pickle FAQ (public profile = “username, profile photo, and bio”)
6Mona runs on Jelly’s own software; no third-party AI providerSystem: mona.js — deterministic, no model call. Must be revisited if the documented LLM seam is filled.
7No cookies, analytics or trackers on the websiteSystem: apps/landing/public/index.html — no third-party script or pixel
8Security measuresSystem: auth.js
9No self-serve deletion; deletion by requestSystem: no delete-account route exists in apps/api/src
9Retention schedule[LAWYER] — none defined
10State privacy rights (CCPA / SHIELD)[LAWYER] — entire section is a placeholder
1118+; under-13 information bardocs/pickle-legal.md §1 (Pickle ToS age floor); docs/legal/TERMS.md §2
12International transfer[LAWYER] — hosting and courier regions unconfirmed
13ChangesStandard scaffolding
14Contact [email protected]voice.md §9; landing footer

Back to Jelly · Terms · Accessibility · [email protected]

Jelly is a marketplace and is not a party to the rental agreement between users.