Privacy Policy

1. Who operates this service

Anapep is currently operated by an individual based in California, United States.

Privacy questions and data requests: contact@anapep.com.

2. Scope

This policy covers the Anapep web application. It does not cover any separate service you may connect to in future, or any website or product not operated as part of Anapep.

3. What Anapep is

Anapep is a consumer application for recording, organising, planning and analysing your own health and performance information. It keeps protocols and schedules, holds lab results you enter, estimates body measurements from photographs, imports a wearable history file you supply, and summarises all of that back to you.

It is not a healthcare provider, not a pharmacy, not a prescriber and not a telehealth service, and it is not intended to operate as a HIPAA-covered healthcare service. Using it creates no clinician–patient relationship. The Terms of Service set out what the application is and is not in more detail.

4. Information you provide

Almost everything Anapep holds is information you supplied yourself — typed in, or imported from a file you chose. Nothing in the following list is collected automatically, and none of it is required to open the application — you decide what to enter.

• Account information — your name, email address, and the credentials used to sign in. Your password is held by Anapep’s sign-in provider, Clerk, not by Anapep.
• A profile photo — only if you choose to upload one in Settings. It is held by Clerk with your sign-in account (section 6).
• Profile and onboarding details — age, sex, height, weight, and the goals and targets you set.
• Health metrics you log by hand — sleep, heart-rate variability, resting heart rate, steps, calories, workout minutes, recovery and strain scores, and body weight.
• Lab biomarkers — values from bloodwork that you enter by hand or import from a CSV, including hormone, metabolic, liver, kidney and inflammation markers, and the filename of an imported CSV.
• Body scans and photographs — images you choose to add for body-measurement estimates, and the measurements derived from them; and progress photos you upload to the Photo Timeline without a scan, with the date you give them and any caption. Uploaded progress photos are not analysed, and no measurement or estimate is derived from them.
• Progress measurements — weight and body-composition check-ins over time.
• Protocols and blueprints — the compounds, supplements, doses and schedules you plan.
• Inventory and dose logs — what you hold, and what you record having taken.
• Saved calculations — reconstitution and dose calculations you explicitly choose to keep.
• Wearable history you import — daily summaries read out of an export file you supply.
• Calendar information — scheduled events and whether you marked them complete.
• Notes — anything you write in the notes area.
• Generated reports — documents the application assembles from the above, and the references linking them back to their sources.
• AI Coach questions — what you ask, and a question queued from another page until the Coach reads it.
• Search history — recent searches within the application, kept so the search box can offer them again.
• Preferences — appearance settings, dismissed prompts, and which notifications you have read.
• Favorites — the compounds and supplements you star in the Compound and Supplement Libraries.
• Your acceptance of the medical disclaimer — that you accepted it, when, and which version.
• An AI Scan usage record — how many scans were run, by month, so that monthly limits can be applied. It holds an identifier, a timestamp and a month, and no photograph or measurement.

Not every category is treated the same way, and not every category can leave your browser. Section 6 explains where things rest, section 7 explains what leaves, and the sections after it take the features that matter one at a time.

5. Health information

Much of the above is sensitive. Lab results, body photographs, medications and compounds, and daily physiological metrics say a great deal about a person, and you should decide deliberately what you are willing to record.

Information you enter here is not the same as a medical record held by a clinician, hospital or insurer. Records kept by those organisations are governed by rules that apply to them as healthcare providers and insurers; Anapep is not one of those, so those particular rules are not what governs the copy you keep here. Which laws do apply to a consumer application like this one depends on where you live, and that is a question for qualified legal advice rather than something this document should decide on your behalf.

6. Where your information is stored

In your browser. Anapepkeeps the information you enter in your own browser’s storage (localStorage, and sessionStorage for a sign-in session you choose not to keep). Apart from the Basic Information described below, none of it is stored on an Anapep server.

Your account record is held on Anapep’s server. Anapep’s database, hosted by DigitalOcean (section 13), holds an internal Anapep account ID, the email address your sign-in provider has verified for you, the identifier your sign-in provider uses for your account, and when the record was created and last updated. It lets your account be recognised in any browser you sign in from. The account record itself contains no health or performance information.

Your Basic Information is saved to your account on Anapep’s server. When you finish onboarding, these answers are saved in the same database, linked to your Anapep account (they are not given to Clerk):

• age;
• sex;
• height;
• weight;
• target weight;
• target body-fat percentage;
• and whether you have completed onboarding.

A question you left blank is saved as blank. When you sign in from another browser or device, your Basic Information is loaded from your account, so you are not asked for it again. If you completed onboarding in a browser before this was introduced, your answers there are copied to your account the first time you open Anapep in that browser while signed in — provided they are valid and your account does not already hold Basic Information. Where your account already holds it, that copy is the one used, and answers kept in a browser are not uploaded over it.

You can view and change your Basic Information at any time in Settings, under Basic Information. A change is saved to your account, replaces the earlier answers there, and is what every browser or device you sign in from then loads. If your Basic Information was changed or cleared somewhere else after you opened it, your change is not saved and the latest answers are shown instead.

Only Basic Information is saved this way. The goals and experience you choose during onboarding, the protocol you describe there, and every other category in section 4 — labs, body scans and photographs, health metrics, wearable history, progress, protocols, inventory, dose logs, calculations, calendar, notes, reports and favorites — stay in your browser.

Favorites stay in the browser where you star them. They are kept separately for each account signed in on that browser, are not saved to your account on Anapep’s server, and do not appear on another browser or device.

Your sign-in details — name, email address and password — are held by Clerk, which runs sign-in for Anapep (section 13). So is your profile photo, if you upload one in Settings: Clerk stores it with your sign-in account, which is why it appears in any browser you sign in from. It is not kept in your browser’s storage. You can change or remove it in Settings, under Profile. Section 7 explains how the photo is shown, and what removing it does and does not do.

What follows from that:

• Apart from Basic Information, your information does not follow you between devices or browsers. A second computer, a different browser or a private window lets you sign in to the same account and loads your Basic Information, but starts without the rest of the information you entered elsewhere.
• Clearing this site’s data removes what is stored in that browser, and apart from your Basic Information, which stays with your account, there is no backup or copy of it elsewhere to restore from. It does not remove your account record, the Basic Information saved to your account, or your Clerk sign-in account; section 15 explains what does.

Anapep’s application contains groundwork for keeping more of your information on its server. Beyond Basic Information, that is not enabled, and this policy will be updated before any more of it is.

7. When information leaves your browser

Section 6 is about where your information rests. This section is about when it travels, which is a different question — and version 1.3 of this policy allowed the first to imply the second. It does not.

Some features cannot work without sending something to an outside service. Where that is true, it is named here and explained in its own section:

• The AI Coach sends your question and a structured summary of your information to Anthropic in order to answer it. See section 8. This is the one place where health information is sent to an outside service as a matter of course.
• Your Basic Information travels between your browser and Anapep’s server — when you finish onboarding, when you open Anapep while signed in, when you view or change it in Settings, and when you use either deletion control in section 15 — so that it can be saved to, loaded from, changed in and cleared from your account. See section 6.
• Signing in sends your email address and password to Clerk, which runs sign-in for Anapep, and Clerk may email you a verification code. See section 13.
• Uploading a profile photo. Before anything is sent, Anapep re-creates the image in your browser from its pixels alone, at most 1,024 pixels on its longest side. That removes the information stored inside the original file — such as where and when a phone photo was taken and which camera took it — and an animated GIF is saved as a still image. If the image cannot be re-created this way, nothing is uploaded. Only the re-created image is sent to Clerk, which stores it with your sign-in account and shows it from its own image service. That image is shown from a web address that is not protected by sign-in: anyone who has that address can open it. The address is long and hard to guess, and Anapep does not publish it, but it is part of the pages you see while signed in — so do not use a photo you would not want others to see, such as a body or health photograph. Removing or replacing your photo in Settings takes it off your sign-in account straight away, and Anapep stops showing it, but it does not by itself erase the image files Clerk has stored: in our testing, earlier image files sometimes stayed reachable at their previous addresses for minutes afterwards. See sections 13 and 16.
• A body scan downloads a pose model and its runtime from third-party file hosts. Your photographs are not part of those requests. See section 9.
• Loading the application at all involves ordinary web requests to whoever hosts it, which reveal ordinary network metadata — your IP address, and browser and device information — as any website does.

Everything else in the application — writing a protocol, logging a dose, entering a lab result, running a calculation, importing a wearable file, generating a report, starring a favorite — happens in your browser and sends your information nowhere.

8. The AI Coach and Anthropic

The AI Coach uses an external AI provider: Anthropic. When you ask the Coach a question, this is what happens:

• Anapep first works out its own answer on your device, from the information already in your browser.
• Your question, that answer, and a structured summary of your health and performance information are sent from your browser to an Anapep endpoint, which forwards them to Anthropic’s API.
• Anthropic’s response comes back to your browser and is shown to you.

What the summary may include. Anapep sends a deliberately limited, structured set of facts rather than your records. Depending on what you have entered and what is relevant, it can include: your question; the answer Anapepcomputed itself; your Optimization Score and its categories; lab summary figures, together with biomarker names and their recorded values; how many progress check-ins you have and your first and latest recorded weight; your protocol adherence figures; a summary of how two body scans compare; your Forecast confidence, assumptions and risks; your active protocol’s name and its compounds with their doses and frequencies; recent wearable metrics such as sleep, heart-rate variability, resting heart rate and recovery; averages from imported wearable history along with how many days each average covers; labels for the kinds of data you have not recorded; and up to four recent turns of the conversation you are having.

Not every request contains every category. These are the categories that may be included, when the information exists and is relevant to what you asked.

What is deliberately left out. The following are not included in what is sent, by design: your name; your email address; your account or user ID; your sign-in credentials or tokens; the raw contents of your browser storage; your body photographs or any image data; the filename of a lab file you imported; the lab file itself; raw wearable sensor samples; day-by-day wearable history; and anything you entered into the dose or reconstitution calculator, whether or not you saved it.

A question about what to take is answered without leaving your device. If you ask the Coach to make a treatment or dosing decision, Anapep declines to answer that question itself and the request is never sent anywhere.

Transmitted is not the same as stored. Your conversation is not saved by Anapep. It exists while the page is open and is gone when you navigate away. Up to four recent turns are nevertheless included in a request while that conversation is open, so a follow-up question makes sense — sent, but not kept.

What happens at Anthropic is governed by Anthropic. Once information reaches them it is handled under their own terms and privacy practices, which Anapep does not control and cannot describe on their behalf. This policy therefore makes no claim about how long they keep it, what they do with it, where it is processed, or who else may be involved. Those are questions for their own documentation.

If the AI layer is not configured for a particular deployment, the Coach answers entirely on your device from the information in your browser, and nothing is sent. The same happens if a request fails or times out.

9. Body scans and photographs

Your photographs are analysed on your own device. The pose-estimation models examine the image in your browser. Your photographs are not uploaded to Anapep, are not sent to Anthropic, are not sent to OpenAI, and are not sent to any external image-analysis service. There is no such integration in the application.

To do that, your browser downloads the models and their runtime from third-party infrastructure — jsDelivr and Google-hosted model storage. Those are ordinary file downloads, but like any web request they reveal ordinary network metadata to the host: your IP address, and browser and device information. No image and no health data is included in those requests.

The measurements are a separate matter from the photographs. A scan produces derived figures — estimated widths and lengths, and a comparison against an earlier scan — and those are ordinary health information stored with the rest. Selected derived scan information, such as a summary of how two scans compare, can be included in AI Coach context and therefore sent to Anthropic when you use the Coach. The images never are.

Photographs are stored with the scan record in your browser. If your browser’s storage fills up, Anapep keeps the measurements and drops the images rather than losing the scan.

Progress photos you upload are not analysed at all. You can also add photos to the Photo Timeline without a scan. No pose model looks at them, no measurement or estimate is made from them, and they do not count as an AI Scan. Anapep does not upload these progress photos to its servers or include them in requests to the AI Coach. Before one is saved, your browser re-creates it from its pixels: at most 1,024 pixels on its longest side, saved as a JPEG, which removes the information stored inside the original file, such as where and when it was taken and which camera took it. If that cannot be done, the photo is not saved. Uploaded photos, with the date you choose and any caption, are stored in your browser, kept separately from your scans. If your browser’s storage is full, nothing is saved and you are told so. You can delete them in the Photo Timeline, and both deletion controls in section 15 remove them.

10. Lab results

You can enter values by hand, or import them from a CSV file you supply. An imported CSV is read in your browser so its values can be shown to you for review before you save them; the file itself is not stored, and no copy of it is kept.

Anapep does record the filename of an imported CSV alongside the lab panel it created, so you can tell one import from another later — bear that in mind if your filename contains your name or other details. It also records the biomarker wording and the unit the file itself showed— for example “Testosterone, Total” and “ng/dL” — kept beside the result so you can check it against the report it came from. Nothing else from the file is retained: not its contents, and not the name of the laboratory, which Anapep neither asks for nor works out from the file.

Automatic extraction from a PDF or a photograph of a lab report is not available. Selecting a file of that kind tells you so and does nothing else: it is not read, nothing is derived from it, no values are produced, and its filename is not recorded. If that ever changes, this policy will be updated before the feature is turned on.

Lab information can reach the AI Coach. Biomarker names and their recorded values can be included in the summary sent to Anthropic when you use the Coach, as described in section 8. The imported file and its filename are not.

11. The dose and reconstitution calculator

The calculator is worth describing precisely, because computing and saving are two different actions and only one of them keeps anything.

Computing. When you enter numbers and the calculator works out a result, that is arithmetic performed in your browser on the values you supplied. Running a calculation does not create a protocol, does not create a dose-log entry, does not change your inventory, does not touch your calendar or your adherence figures, and does not store the numbers you entered. Leave the page without saving and those values are gone. Nothing you type into the calculator is sent to the AI Coach or to any other service.

Saving. Saving a calculation is a separate action you take deliberately. When you do, Anapepkeeps a record in your browser’s calculation history containing the label you gave it, the values you entered, the result that was worked out, the time you saved it, and — if the strength was filled in from something you track in inventory — a link to that item and the compound name. You can delete a saved calculation on its own, and both of the bulk controls in section 15 remove them.

Saved calculations are also not sent to the AI Coach. Neither your calculation history nor an unsaved calculation forms any part of what section 8 describes.

For what the calculator does and does not decide — it performs arithmetic and does not recommend, select or approve an amount — see section 5 of the Terms.

12. Wearables and connected devices

There is no live connection to any wearable. Oura, Garmin, WHOOP, Fitbit, Apple Health and Health Connect appear in the application as planned integrations that are not yet available. Anapep does not connect to any of them, holds no credentials for them, and receives nothing from them.

There are two ways wearable information can be in your account today:

• You typed it in — the manual metrics described in section 4.
• You imported a history file — an export you downloaded from Oura yourself and then chose to open in Anapep.

How a history import works. You pick the export file from your own device. It is read and interpreted in your browser; nothing is uploaded, and importing a file tells Oura nothing — they are not involved in it at all. Anapep keeps the daily summaries it understands, stored locally with the rest of your information.

Two things are deliberately left out of an import. Location data is never imported — if the export contains any, Anapep skips it and tells you that it did. High-volume raw sensor series, such as continuous heart-rate samples and motion data, are also not imported.

Imported history can reach the AI Coach. Averages for a period, and how many days each average covers, can be included in the summary sent to Anthropic. Day-by-day records and raw sensor samples are not.

13. Third parties

Who is involved in the current application, and who is not:

Active today:

• Anthropic — generates AI Coach answers, and receives your question and the structured summary described in section 8. Apart from DigitalOcean, which stores your Basic Information on Anapep’s behalf as the database host, this is the only third party that receives health information.
• Clerk — runs sign-in for Anapep. It holds your name, email address, password and any profile photo you upload (section 7 describes how that photo is stored and shown), sends any email verification codes it asks you for, and keeps the records it needs to maintain your signed-in sessions. Clerk does not receive your health information.
• DigitalOcean — hosts Anapep’s database (managed PostgreSQL). It stores the account record and the Basic Information described in section 6 on Anapep’s behalf.
• jsDelivr and Google-hosted model storage — serve the body-scan models and runtime when you run a scan, and receive ordinary network metadata. No image and no health data is sent to them.
• The hosting provider — whoever serves this application to you handles the ordinary web traffic required to load it, and its server logs may record that an AI Coach request was made, how long it took and whether it succeeded. Those operational records do not contain your question or your health information.

Not active, and receiving nothing today:

• Oura’s API, WHOOP, Garmin and other live device connections.
• OpenAI, and any external image or vision analysis service.
• Any payment or subscription-billing provider. Anapep does not take payments.

This policy will be updated before any of the inactive services above starts receiving your information.

14. Advertising, analytics and tracking

The application contains no advertising system, no product-analytics package, no error-monitoring service and no tracking pixels. No part of it is built to make your information available to anyone for advertising or ad targeting, and nothing in it profiles you for that purpose. Anapep does not trade in your information.

Words such as “sale” and “sharing” have specific meanings under some privacy laws that do not always match their everyday use. The statements above describe what the application technically contains and does; how a particular law classifies that is a legal question, and this policy does not attempt to answer it.

One qualification, stated plainly rather than glossed over: Anapepis built with Next.js, and the framework’s own anonymous build telemetry is a property of the deployment rather than of this application’s code. It concerns the framework’s usage, not your health information, but we would rather name it than claim that nothing is ever reported anywhere.

15. What you can delete today

This section describes controls that actually exist. Where something is missing, it says so.

Item by item, you can delete:

• Blueprints and protocols
• Inventory items
• Dose-log entries
• Saved reconstitution and dose calculations
• Saved reports

Two further controls are in Settings, under Data & Privacy. Both act immediately and cannot be undone; Anapep keeps no copy for you and offers no recovery period.

Delete Health & Performance Data clears the health and performance information held for your account and keeps the account itself, so you can carry on using Anapep with an empty record. It removes:

• Lab biomarkers
• Body scans and photographs, and the measurements taken from them, including progress photos you uploaded to the Photo Timeline
• Health metrics you logged, imported wearable history, and any wearable connection and sync history
• Recovery scores and progress check-ins
• Blueprints and protocol information
• Inventory, dose logs and saved calculations
• Calendar protocol information and completion history
• Optimization-score history and saved reports
• Recent searches made within the application
• Notes you wrote in the notes area
• Any AI Coach question waiting to be asked
• The setup details describing your body and aims — age, sex, height, weight, goals and targets — including the Basic Information saved to your account (see below)

It keeps your account and sign-in details, your display name and profile, your profile photo, your preferences, your favorites, your subscription state, your recorded acceptance of the medical disclaimer, and your AI Scan usage record. You stay signed in.

Why the AI Scan usage record is kept. It counts how many scans were run in a month, so that monthly limits can be applied. It holds an identifier, a timestamp and a month — no photograph, no measurement and nothing describing your body. Clearing it alongside your scans would mean deleting your data reset your monthly allowance, so it is kept for as long as the account exists. Delete Account removes it.

The Basic Information saved to your account is cleared first. Both controls clear it on Anapep’s server before they delete anything in your browser. What stays on the server is your account’s onboarding record with every answer removed and marked as not completed, so that a browser still holding your earlier answers cannot put them back. If the server cannot confirm that it has been cleared, nothing is deleted from your browser and the control tells you it failed; you can try again.

Delete Account — labelled Delete my data and sign out in Settings when you are signed in with an account, because it does not delete the account itself — clears the Basic Information saved to your account, as described above, and then removes the Anapep information held for your account in this browser — everything in the list above, plus your profile, preferences, favorites, subscription state, your AI Scan usage record and your recorded acceptance of the medical disclaimer — and then signs you out.

What Delete Account does not yet remove:

• Your account record on Anapep’s server— the internal account ID, your email address and the link to your sign-in account — and your account’s onboarding record, which by then holds none of your answers.
• Your sign-in account with Clerk — your name, email address, password and any profile photo. You can remove the photo yourself in Settings, under Profile; that takes it off your account, and section 16 explains what happens to the stored file. Signing out is not deleting it: you can sign in again, which returns you to the same Anapep account without the information above.
• Information stored in other browsers you have used. A deletion acts on the browser you make it in, and is not carried out remotely in any other. An earlier copy of your Basic Information that another browser still holds is not loaded back into your account. Any other browser or device where you are signed in stays signed in.

To have your account record and your sign-in account removed, write to contact@anapep.com. Removing them from within the application is planned and not yet available, so these requests are handled by hand. We will ask you to confirm the request from the email address on the account. We then delete your sign-in account with Clerk, which removes any profile photo from it, and your account record on Anapep’s server together with the onboarding record linked to it, and tell you when that is done. Deleting the sign-in account does not by itself erase image files Clerk has already stored (section 16). Copies in the database host’s backups remain until those backups expire (section 16), information already sent to an outside service is not reached, and information stored in your browsers stays there until you remove it.

It deletes that account’s information, not the browser. Settings belonging to the device rather than to your account — your appearance preference, for example — are left as they are, and if a second Anapep account has been created in the same browser, that account and its information are not touched.

There is still no in-application control to:

• Delete a single logged health metric, lab result or body scan on its own
• Export all of your information in one action

These controls act on the browser you are using and on the account you are signed in to. On Anapep’s server they clear the Basic Information saved to your account, and nothing else. They do not reach other browsers, your account record, or your Clerk sign-in account, as described above. If Anapep later keeps more of your information on its server, this policy will be updated to say how deleting it works.

What deletion cannot reach, in any configuration:

• Copies you exported or saved yourself, including generated reports you downloaded
• Screenshots and photographs you keep outside Anapep
• Backups your browser, device or operating system makes, which are outside our control
• Anything already sent to an outside service, such as a question and summary Anthropic has already handled. Deleting your Anapep information does not reach into a third party’s systems.

Separately from all of the above, clearing this site’s data through your browser’s own settings removes what is stored in that browser. That is a browser control rather than a feature of Anapep: it takes everything rather than one account, it applies only to the browser you do it in, and it cannot be undone. It does not delete your account record or your Clerk sign-in account, and it does not clear the Basic Information saved to your account.

16. Retention

Anapepdoes not expire or automatically delete anything, and no retention period is set. Information in your browser stays there until you remove it — using one of the controls in section 15, or through your browser’s own settings. Your account record on Anapep’s server stays until it is removed on request (section 15). The Basic Information saved to your account stays until one of the deletion controls in section 15 clears it.

Anapep’s database host may keep backups of the database; information removed from the database can remain in those backups until they expire.

How long an outside service keeps what section 7 describes — including Clerk’s records of your sign-in account — is that service’s own matter, and this policy does not state a period for it.

Profile photos. Removing or replacing your photo, or deleting your sign-in account, takes the photo off your account. It does not by itself erase the image files Clerk stored, including the re-created file that was uploaded (section 7). In our testing, removed and replaced images, and the stored files behind them, were sometimes still reachable at their previous addresses for minutes afterwards, and after a sign-in account was deleted, for at least five minutes. When Clerk deletes stored image files is decided by Clerk, and this policy does not promise a time.

17. Age

Anapep is intended for adults aged 18 and over. It is not directed at children and should not be used by anyone under 18.

You are asked to confirm your age when you accept the medical disclaimer. Anapep does not verify age or date of birth — that confirmation is taken at your word.

18. Changes to this policy

This is version v1.9, effective October 19, 2026. When it changes materially the version will change with it, and the new version will be shown here.

What changed in v1.9: progress photos. You can now upload photos to the Photo Timeline without an AI Scan. Section 4 lists them; section 9 says that they are not analysed and nothing is measured or estimated from them, that Anapep does not upload them to its servers or include them in requests to the AI Coach, that your browser re-creates them before saving so the location and camera details stored inside the original file are removed, and that they are stored in your browser separately from your scans; and section 15 says that both deletion controls remove them. Nothing else has changed.

What changed in v1.8:three changes. Favorites — the compounds and supplements you star — are now listed in section 4, and sections 6, 7 and 15 say that they stay in the browser where you star them, are never sent anywhere, are kept by Delete Health & Performance Data and are removed by Delete Account. You can now upload a profile photo in Settings; sections 4, 6, 7, 13, 15 and 16 say that Clerk stores it with your sign-in account; that it is re-created in your browser before it is sent, which removes the information stored inside the original file, such as location, and saves an animated GIF as a still image; that it is shown from a web address that does not require sign-in, so a body or health photograph should not be used; that you can remove it in Settings; that removing or replacing it, or deleting your sign-in account, does not by itself erase the image files Clerk stored; and that Delete Account does not remove it. Section 15 now also says that Delete Health & Performance Data removes your notes, which it always did; that Delete Account is labelled “Delete my data and sign out” when you are signed in with an account, and leaves other browsers signed in; and how a request to remove your account is handled. Nothing else has changed.

What changed in v1.7: you can now view and change your Basic Information in Settings. Section 6 says so, and how a change is saved; section 7 adds changing it in Settings to the times your Basic Information travels to Anapep’s server. Nothing else about what is stored, where, or how it is deleted has changed.

What changed in v1.6: Basic Information from onboarding — age, sex, height, weight, target weight, target body-fat percentage, and whether onboarding is complete — is now saved to your account on Anapep’s server and loaded when you sign in from another browser or device. Version 1.5 said none of your information was stored on an Anapep server and that none of it followed you between browsers; sections 6, 7, 13 and 16 now describe this exception, and that everything else still stays in your browser. Section 15 now says that both deletion controls clear that server copy first, and do not proceed if they cannot.

What changed in v1.5: this is a correction. Version 1.4 said Clerk was not in use and that no Anapep server held anything. In fact Clerk runs sign-in, and Anapep’s database, hosted by DigitalOcean, holds an account record linking your sign-in to your account; it holds no health or performance information. Sections 6, 7, 13 and 16 now say so. Section 15 now says that Delete Account signs you out, and what it does not yet remove — your account record, your Clerk sign-in account, and information in other browsers — and how to ask for the first two to be removed.

What changed in v1.4: this is a correction, and a significant one. Version 1.3 said the AI Coach ran entirely on your device, that no external AI provider received your information, and that this policy would be updated before any external AI service was switched on. By then the Coach was already sending your question and a structured summary of your information to Anthropic. Section 8 now describes that in full — what is sent, what is deliberately left out, and what Anapepis not in a position to promise about a provider it does not control. Section 7 is new, and separates where information is stored from when it leaves. Section 12 corrects the claim that every wearable metric was typed in by hand, when a historical Oura import has been available. Section 13 replaces a “complete list” of third parties that did not include Anthropic. Section 11 is new and describes the calculator. Section 15 now discloses that the AI Scan usage record survives health-data deletion, and that an AI Coach question waiting to be asked is now removed by both controls — it previously survived both, because the way it was stored did not record whose it was.

What changed in v1.3: section 3 disclosed that an imported CSV also leaves behind the biomarker wording and the unit the file showed.

What changed in v1.2: section 3 was corrected about lab results. Version 1.0 said no lab report could be uploaded as a file and that biomarker values were entered by hand. Importing a CSV has always been possible, so that was wrong when it was written.

What changed in v1.1: the deletion section was rewritten. Version 1.0 said there was no in-application way to delete your account or your logged health data. Both controls now exist.

The checkboxes on the sign-up form ask you to agree to this policy and to the Terms of Service. They are required to create an account, but Anapepdoes not currently keep a record of that agreement — no acceptance, timestamp or version is stored for either document. Only the medical disclaimer’s acceptance is recorded, in your browser.

19. Contact

Write to contact@anapep.com.