Clue Birth Control is a software application for contraception for women ages 18 - 45 years old, to monitor their fertility and prevent pregnancy. Clue Birth Control is suitable for women with predictable 20 - 40 day cycles, who have not recently used hormonal birth control.
Device Story
Clue Birth Control is a mobile software application for contraception. It uses a proprietary algorithm based on Fertility Awareness Based Methods (FABM). Users input period start dates; the device processes this data to predict 'high risk' and 'low risk' days for conception. Users are instructed to abstain from sex or use barrier contraception on high risk days. The device is intended for patient self-use. It aids clinical decision-making by providing fertility status, allowing users to manage pregnancy risk. Benefits include a non-hormonal method of contraception for eligible users.
Clinical Evidence
Prospective clinical trial (Dynamic Optical Timing trial) at Georgetown University with 718 women (ages 18-39) over 6,616 cycles. Primary endpoints: Pearl Index (PI). Results: Perfect-use PI of 0.8; Typical-use PI of 5.2 (95% CI: 3.4-7.7). Worst-case typical-use PI calculated as 12.
Technological Characteristics
Mobile-based software application. Proprietary algorithm for fertility prediction based on period start dates. Standalone software; no hardware components. Software documentation provided for major level of concern. Cybersecurity controls implemented per FDA guidance.
Indications for Use
Indicated for women ages 18-45 with predictable 20-40 day cycles (variability ≤ 9 days) to monitor fertility and prevent pregnancy. Contraindicated for women who have not completed at least 3 cycles (4 periods) after stopping hormonal birth control or following pregnancy.
Regulatory Classification
Identification
A software application for contraception is a device that provides user-specific fertility information for preventing a pregnancy. This device includes an algorithm that performs analysis of patient-specific data (e.g., temperature, menstrual cycle dates) to distinguish between fertile and non-fertile days, then provides patient-specific recommendations related to contraception.
Special Controls
1. Clinical performance testing must demonstrate the contraceptive effectiveness of the software in the intended use population.
2. Human factors performance evaluation must be provided to demonstrate that the intended users can self-identify that they are in the intended use population and can correctly use the application, based solely on reading the directions for use for contraception.
3. Software verification, validation, and hazard analysis must be performed. Documentation must include the following:
a. A cybersecurity vulnerability and management process to assure software functionality; and
b. A description of the technical parameters of the software, including the algorithm used to determine fertility status and alerts for user inputs outside of expected ranges.
4. Labeling must include:
The following warnings and precautions: a.
i. A statement that no contraceptive method is 100% effective.
ii. A statement that another form of contraception (or abstinence) must be used on days specified by the application.
iii. Statements of any factors that may affect the accuracy of the contraceptive information.
iv. A warning that the application cannot protect against sexually transmitted infections.
b. Hardware platform and operating system requirements.
Instructions identifying and explaining how to use the software application, including C. required user inputs and how to interpret the application outputs.
d. A summary of the clinical validation study and results, including effectiveness of the application as a stand-alone contraceptive and how this effectiveness compares to other forms of legally marketed contraceptives.
*Classification.* Class II (special controls). The special controls for this device are:(1) Clinical performance testing must demonstrate the contraceptive effectiveness of the software in the intended use population.
(2) Human factors performance evaluation must be provided to demonstrate that the intended users can self-identify that they are in the intended use population and can correctly use the application, based solely on reading the directions for use for contraception.
(3) Software verification, validation, and hazard analysis must be performed. Documentation must include the following:
(i) A cybersecurity vulnerability and management process to assure software functionality; and
(ii) A description of the technical parameters of the software, including the algorithm used to determine fertility status and alerts for user inputs outside of expected ranges.
(4) Labeling must include:
(i) The following warnings and precautions:
(A) A statement that no contraceptive method is 100% effective.
(B) A statement that another form of contraception (or abstinence) must be used on days specified by the application.
(C) Statements of any factors that may affect the accuracy of the contraceptive information.
(D) A warning that the application cannot protect against sexually transmitted infections.
(ii) Hardware platform and operating system requirements.
(iii) Instructions identifying and explaining how to use the software application, including required user inputs and how to interpret the application outputs.
(iv) A summary of the clinical validation study and results, including effectiveness of the application as a stand-alone contraceptive and how this effectiveness compares to other forms of legally marketed contraceptives.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, with the letters "FDA" in a blue square. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
February 18, 2021
BioWink GmbH % Yarmela Pavlovic Partner Manatt, Phelps & Phillips, LLP One Embarcadero Center 30th Floor San Francisco. CA 94111
Re: K193330
Trade/Device Name: Clue Birth Control Regulation Number: 21 CFR§ 884.5370 Regulation Name: Software Application for Contraception Regulatory Class: II Product Code: PYT Dated: January 4, 2021 Received: January 4, 2021
Dear Yarmela Pavlovic:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
{1}------------------------------------------------
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies.
You must comply with all the Act's requirements. including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatoryinformation/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
For Monica D. Garcia, Ph.D. Assistant Director DHT3B: Division of Reproductive, Gynecology and Urology Devices OHT3: Office of GastroRenal, ObGyn, General Hospital and Urology Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K193330
Device Name Clue Birth Control
Indications for Use (Describe)
Clue Birth Control is a software application for women ages 18 - 45 years old, to monitor their fertility and prevent pregnancy. Clue Birth Control is suitable for women with predictable 20 - 40 day cycles, who have not recently used hormonal birth control.
| Type of Use (Select one or both, as applicable) | |
|-------------------------------------------------|--|
|-------------------------------------------------|--|
Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
#### CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
Image /page/3/Picture/1 description: The image shows the logo for the Clue period tracking app. The logo consists of a red geometric flower-like symbol on the left, followed by the word "Clue" in a red, rounded sans-serif font. A small registration mark is visible to the upper right of the "e" in "Clue."
# 510(k) Summary BioWink GmbH - Clue Birth Control K193330
### Submitter
BioWink GmbH Adalbertstrasse 8 10999 Berlin, Germany
Contact person: Carrie Walter phone: +49 151 62780 364 e-mail: regcontact@helloclue.com
Date prepared: February 16, 2021
### Name of Device
Trade name: Clue Birth Control Common name: Software application for contraception Regulation number: 21 CFR 884.5370 Regulation name: Software application for contraception Requlatory Class: II Product Code: PYT (Device, fertility diagnostic, contraceptive, software application)
### Predicate Device
Natural Cycles Nordic AB, Natural Cycles (DEN170052)
The predicate device has not been subject to a design-related recall.
### Device Description
Clue Birth Control is a feature of the Clue period tracker mobile application. Clue Birth Control's proprietary algorithm uses period start date information entered by the user to provide predictions of "high risk days" and "low risk days" for becoming pregnant based on a Fertility Awareness Based Method (FABM) of contraception. Identification of high risk days allows the user to determine the days on which her risk of conception is highest, and then make choices about either abstaining from sex or using a barrier method of contraception to prevent pregnancy.
To use Clue Birth Control, users go through an onboarding process from within the Clue app, during which they are asked to provide information that will determine whether they meet the Clue Birth Control use criteria. Clue Birth Control can only be used by women who are between
{4}------------------------------------------------
18 and 45 years old and their last 12 cycles were between 20 and 40 days and the difference between the lengths of the shortest and longest cycles is less than or equal to 9 days. In addition, users must have had at least three cycles (four periods) after stopping hormonal birth control (HBC) or since the end of a pregnancy.
## Indications for Use
Clue Birth Control is a software application for contraception for women ages 18 - 45 years old, to monitor their fertility and prevent pregnancy. Clue Birth Control is suitable for women with predictable 20 - 40 day cycles, who have not recently used hormonal birth control.
### Comparison of Intended Use and Technological Characteristics of the Subject and Predicate Devices
| Description | Subject Device<br>(Clue Birth Control: K193330) | Predicate Device<br>(Natural Cycles: DEN170052) |
|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Indications for Use | Clue Birth Control is a software<br>application for contraception for<br>women ages 18 - 45 years old, to<br>monitor their fertility and prevent<br>pregnancy. Clue Birth Control is<br>suitable for women with predictable<br>20 - 40 day cycles, who have not<br>recently used hormonal birth control. | Natural Cycles is a stand-alone software<br>application, intended for women 18<br>years and older, to monitor their fertility.<br>Natural Cycles can be used for<br>preventing a pregnancy (contraception)<br>or planning a pregnancy (conception). |
| Prescription /<br>Over-the-counter<br>use | Over-the-counter | Over-the-counter |
| Application Type | Mobile-based software supplication | Web and mobile-based software<br>application |
| User inputs | Period start date | Menstrual cycle information<br>(period start date and number of<br>days) Daily basal body temperature<br>measurements Optional: ovulation or pregnancy<br>test results |
| Device output | High risk days - Instructs user to abstain<br>from sex or use a back-up barrier<br>contraceptive | Use protection - Instructs user to abstain<br>from sex or use a back-up barrier<br>contraceptive |
| | Low risk days - States that the risk of<br>pregnancy is low | Not fertile - States that the user can<br>have sex without protection |
Table 1. Subject and predicate device comparison
{5}------------------------------------------------
| Description | Subject Device<br>(Clue Birth Control: K193330) | Predicate Device<br>(Natural Cycles: DEN170052) |
|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|
| User<br>Requirements | Women aged 18-45 years Women with cycles between 20 and 40 days and vary by $ \le $ 9 days Women who have recently been on hormonal birth control should have at least 3 cycles (4 periods) after the end of their protection period before using the device Women who have been recently pregnant should have at least 3 cycles (4 periods) before using the device | Women 18 years and older |
The subject and predicate device indications for use are not identical. In addition, the subject and predicate device have different use populations, as Clue Birth Control has a narrower population of users based on their cycle length, cycle variability, and prior HBC use as compared to the predicate device. However, the subject and predicate device have the same intended use of predicting fertile and non-fertile days for use in providing patient-specific recommendations related to contraception.
The subject and predicate devices have different technological characteristics, as Clue Birth Control has different device inputs as compared to the predicate device. Also, Clue Birth Control is only for use on mobile platforms, while the predicate can also be used on web-based platforms. The differences in technological characteristics between the subject and predicate devices do not raise different questions of safety and effectiveness.
### Performance Data
### Non-Clinical Testing
- . Software documentation provided in accordance with the 2005 FDA guidance document Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices to support device software with a major level of concern.
- . Cybersecurity information provided in accordance with the 2014 FDA quidance document Content of Premarket Submissions for Management of Cybersecurity in Medical Devices.
- . Human factors testing evaluated the potential for user errors when using the device. Testing focused on onboarding (eligibility criteria and understanding of risk), data input, and understanding of messaging (high risk, low risk, ineligible, etc.). Testing demonstrated that device users could safely use the device.
{6}------------------------------------------------
### Clinical Testing
Clinical testing in support of Clue Birth Control came from the Dynamic Optical Timing (DOT) clinical efficacy trial, which assessed the same algorithm used in the subject device.
The clinical trial was performed at the Institute for Reproductive Health at Georgetown University. The study was a prospective clinical trial that followed 718 women aged 18 to 39. who were living in the United States. Each woman participated in the study for a period of up to 13 cycles, providing 6616 cycles in total.
### Perfect- vs typical-use
Clue Birth Control has a perfect use Pearl Index of 0.8, which means that 0.8 out of 100 women who use the app perfectly for one year will get pregnant either because:
- They had unprotected sex on a "high risk" day that was incorrectly designated by the app as a "low risk" day (i.e., method failure); or
- They had protected sex on a "high risk" day but became pregnant because the barrier method of protection failed.
Clue Birth Control has a typical use Pearl Index of 5.2, which means that 5.2 women out of 100 get pregnant during one year of use due to all possible reasons (e.g., falsely attributed low risk days, having unprotected intercourse on high risk days, and failure of the contraceptive method used on high risk days).
| Study Date Range | # Women | Exposure [Woman-Years] | # Pregnancies [Worst-Case] | Typical-Use PI (95% CI) [Worst-Case] |
|-------------------|---------|------------------------|----------------------------|--------------------------------------|
| Feb 2017-Oct 2018 | 718 | 509 | 25<br>[58] | 5.2<br>(3.4-7.7)<br>[12] |
Table 2. Summary of clinical data from the efficacy trial
The table above includes worst-case values for the number of pregnancies in addition to the typical use rate. Typical Use Pl includes all pregnancies in the study over all cycles of exposure, including those due to improper use of the app. The worst-case Pl is calculated by assuming pregnancies for all 'possibly pregnant' users lost to follow-up.
### Conclusions
A comparison of intended use and technological characteristics combined with performance data demonstrates that Clue Birth Control. for its intended use population, is as safe and effective as the predicate device and supports a determination of substantial equivalence. Clue Birth Control meets the special controls outlined in 21 CFR 884.5370, Software application for contraception.
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.