To protect a new sex toy idea, protect the information before you protect the document. Identify what is confidential, release it in stages, limit who receives it, record every transfer, and put ownership and exit rights in the development agreement. Sign confidentiality terms before you disclose anything non-public, product-identifying or commercially valuable. An agreement supports that system. It does not replace it.

Most idea leaks are not dramatic. A 3D file reaches a subcontractor nobody named. A mould sits on a factory floor after a project stops.

• Sign before the disclosure, not after a set number of emails
• Name the subcontractors, not just the factory
• Ownership belongs in the development contract, and paying an invoice does not settle it

Who This Article Is For

You are a brand, importer, distributor or ecommerce seller taking an original concept to a Chinese factory. This is not legal advice. Enforceability, remedies and IP ownership rules vary by jurisdiction, so have qualified counsel review your agreement for the factory location, the governing law, and every market where you need protection. Treat what follows as things to raise, not a document to sign.

How to Protect a New Sex Toy Idea Through Staged Disclosure

Match the paperwork to the risk, not the calendar. Each stage raises what a leak would cost you, so decide what leaves your desk before you write the message.

Do not rely on a retroactive clause to rescue an earlier disclosure. An agreement can expressly cover information shared before signature, but whether that works depends on the wording and the governing law. If you have already disclosed, have counsel identify the materials, dates and channels and decide what remedial terms are worth adding.

A mutual agreement is not automatically the right one. It fits when both sides will disclose. When disclosure runs mainly from you, a one-way document is often clearer. Let counsel match the form to the information flow.

What Your NDA Should Cover

Define information, recipients, permitted use, exceptions, duration, and return or destruction. A one-page template usually covers the factory and nobody else, and that gap is where files travel.

An agreement creates contractual duties and a basis for remedies. It cannot physically stop a leak, and it does not replace access controls, file permissions and version records, the measures that keep information qualifying as a trade secret. The WIPO trade secrets overview explains why commercially valuable information depends on reasonable steps to keep it secret.

Raise three points with counsel rather than copy them from a template. Restrictions on manufacturing or selling your design for others, non-circumvention, and non-compete terms all vary in enforceability by jurisdiction, duration, territory and scope.

Duration needs the same treatment. Trade-secret obligations are often tied to how long the information stays secret, while ordinary confidential information may sit under a reasonable fixed term. Governing law and negotiation decide it, not a rule of thumb. Settle the boring parts early too. Use a bilingual version, state which language governs if the two disagree, and fix the governing law and the forum before you sign. An agreement your factory’s legal team cannot read is slower to sign and weaker in practice.

Patent and Design Timing

Assess registrable rights before you disclose, not after. Review the basic WIPO patent guidance with qualified counsel for the markets that matter to your project. Public disclosure ahead of filing can affect novelty in some jurisdictions, grace periods differ where they exist at all, and rights are territorial.

Ask counsel three questions. Is anything here worth filing as a patent or registered design? Does my planned disclosure count as public? Which countries matter, given where the product is made, sold and likely copied? An agreement is not a substitute for registration, and a home-market filing does not automatically protect you elsewhere.

The Ownership Schedule

List every asset and name its owner in writing. Ownership, possession, exclusive use, storage, maintenance, transfer and disposal are separate questions, and there is no safe universal default to fall back on.

The app catches people out. Some factories, including this one, run a proprietary in-house app and offer interface customisation on top of it. That shortcut is useful, and it means the platform stays with the factory. Read our app-controlled toy page, then settle the data questions before tooling: who controls and who processes user data, where it sits, whose privacy notice applies, whether accounts migrate, whether data can be exported or deleted, whether service continues after termination, and whether source code sits in escrow against a defined trigger.

Define exclusivity by scope, not by adjective. Does it cover the whole product, one mould, one structural feature, one colour, one territory, one channel, or one customer group? Our OEM manufacturing overview shows where contracts, tooling and exclusivity sit in the sequence.

Change Control

Number every change and approve it in writing. Most development disputes are not theft, they are memory: you remember asking for a softer tip, the engineer remembers you approving the harder one, nobody wrote it down.

Run a log from the first drawing. One row per change, six fields.

• Change number and date. Sequential, never reused.
• Who requested it. A person, not a company.
• What changed. The dimension, material, mode, component or artwork file, described so an outsider understands it.
• Why. Cost, tooling limit, compliance, test result or appearance.
• What it affects. Price, tooling, lead time, certification, packaging, retest.
• Who approved it, and when. Named and dated in writing.

Version files in the file name itself. Approve by email or signed drawing, never by voice call or a chat message that scrolls away. Where a change touches safety or a claimed rating, note whether it forces a retest and check it against your certification overview and destination market. Our in-house laboratory supports development and process control. It does not replace accredited third-party testing where a market or certification scheme requires it.

Send the log to the factory monthly for confirmation. A mismatch found in month two costs an email. Found at pilot run, it costs a tool change.

Project Exit

Projects either launch or stop. Write both endings before either arrives.

• Files. Return or destruction on request, with written confirmation of which and by when, subcontractors included.
• Moulds. Who holds and insures them, storage duration, notice period and cost to ship them out, and a condition standard so you do not receive a worn tool.
• Samples and prototypes. Returned, destroyed, or kept as sealed reference.
• Firmware, app and data. What you receive, in what form, and whether users and their data migrate.
• Marketing material. Removal from factory catalogues, exhibition stands and websites, with a deadline.
• Surviving obligations. Confidentiality and any manufacturing restriction should outlive the project. State for how long.

An unclaimed mould sitting in a warehouse for three years is the quiet failure here. Nobody stole anything. The tool just stopped being anybody’s problem.

Questions to Ask Before You Disclose

Ask these seven before the first drawing leaves your desk. Judge the answers on specificity, not reassurance.

• Which legal entity signs, and does it actually manufacture?
• Who can access project files, and how is access granted?
• Which subcontractors will see anything, and when will you tell me?
• Who authorises a download, and is it logged?
• How is access closed when a project member leaves?
• How long are my files retained after the project ends?
• How would you evidence destruction if I asked?

A confident answer names people, channels and a retention period. A vague one is information too.

How a Factory Sees This

Clear terms make a factory faster, not slower. Settled ownership lets engineers propose instead of hedge.

With a change log, we quote a modification instead of relitigating a conversation. With subcontractors named up front, your files travel a shorter route. The published development sequence at WINYI runs from concept review through tooling, pilot sample and validation, as set out on our service page, and every stage works better against a signed scope than against goodwill. Our guide on how to work with us covers the steps that follow.

What This Means for Your Project

To protect a new sex toy idea, put paperwork before pixels. Assess registrable rights, sign terms matched to the actual information flow, name the subcontractors, schedule ownership of tooling, software, data and artwork, run a numbered change log, and write the exit before you need it.

Start a confidential ODM discussion by sending your category, target markets, expected annual volume and required confidentiality scope. We can confirm the route and the paperwork before you share full CAD, source code or an unpublished design.

FAQs

Is an NDA enough on its own?

Usually not. An NDA alone is not enough to protect a new sex toy idea. It creates contractual duties and a basis for remedies, but it does not decide who owns the mould, and restrictions on manufacture, sale or circumvention vary in enforceability. Pair it with access controls, version records and an ownership schedule.

Should I file a patent or registered design before approaching factories?

Ask counsel before you disclose. Disclosure ahead of filing can affect novelty in some jurisdictions, grace periods vary where they exist, and rights are territorial, so a home-market registration does not automatically protect you where the product is made or copied.

How long should confidentiality last?

It depends on the information and the governing law. Trade-secret obligations are often tied to how long the information stays secret, while ordinary confidential information may use a fixed term. Set it against your tooling and launch dates.

Can I show a physical prototype?

Only after signing, and only if you log what you sent. Record the serial or a photograph of the unit, state whether it returns, and treat it as a covered document.

This article provides general procurement information, not legal advice. Have qualified counsel review agreements for the relevant jurisdictions.