> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getbased.health/llms.txt
> Use this file to discover all available pages before exploring further.

# Share a profile with a password-protected link

> Create a temporary locked link for one getbased profile, send the password separately, and stop sharing when you are done.

Profile sharing lets you send one getbased profile to another person without exporting a file manually. It is designed for temporary handoff: you create a link, send the password separately, and the recipient loads the profile into their own browser.

<Warning>
  Only create a share link when you are comfortable uploading a locked copy of that profile. Anyone who has both the link and the password can open it.
</Warning>

## What gets shared

A profile share contains the selected profile's health record:

* Lab entries, custom markers, and per-profile marker category placements
* Context cards, health goals, notes, and supplements
* Biometrics, menstrual cycle data, genetics, and Light/Sun data when present
* Profile details such as name, sex, date of birth, location, height, and tags

It does not share your whole getbased database, other profiles, live wearable connection credentials, or Meals & Nutrition records and thumbnails. Use a single-profile JSON export or end-to-end-encrypted Sync when you intentionally need to move reviewed meals. Recipients import the shared profile as a separate copy in their own browser.

Marker placements affect only presentation. The shared copy keeps the same underlying marker identities, values, history, notes, ranges, and import provenance while displaying markers in the categories selected by the sender.

## Create a share link

<Steps>
  <Step title="Open Share Profile">
    On desktop, click the share button in the top bar. On mobile, open the profile menu and choose **Share Profile**. You can also open **Settings -> Data -> Share Profile**.
  </Step>

  <Step title="Choose the password and expiry">
    Use the generated high-entropy password or enter one with at least 12 characters. Choose how long the link should stay available: 7, 14, or 30 days.
  </Step>

  <Step title="Confirm upload">
    Read the confirmation text and check the consent box. getbased creates a locked copy of the selected profile.
  </Step>

  <Step title="Send the link and password separately">
    Copy the link and password from the result screen. Send them through different channels, for example email for the link and a secure message for the password.
  </Step>
</Steps>

<Note>
  The password is the only way to unlock the shared profile. It is not added to the link and is not stored by getbased.
</Note>

## Open a shared profile

<Steps>
  <Step title="Open the link">
    The link opens getbased and shows **Load Shared Profile**.
  </Step>

  <Step title="Enter the password">
    Paste the password that the sender gave you.
  </Step>

  <Step title="Load the profile">
    Click **Load Profile**. getbased unlocks the profile in your browser and imports it as a new profile.
  </Step>
</Steps>

If the password is wrong, the profile cannot be unlocked. If the link has expired or the sender stopped sharing it, it can no longer be loaded.

## Stop sharing a link

Open **Share Profile** again. Links created on the current browser are listed under active links. Click **Stop sharing** to remove the locked copy so the link can no longer load the profile.

Active links are tracked locally on the browser that created them. If you created a link on another device or cleared your browser data, it may not appear in this list.

<Warning>
  Stopping a link prevents future loads from that link. It does not remove copies that someone already imported into their own browser.
</Warning>

## Privacy model

* The selected profile is compressed and encrypted in your browser with AES-256-GCM before upload. The key is derived from the password with PBKDF2-SHA256 using 600,000 iterations.
* The password is never sent with the link and is never stored by getbased.
* The link only finds the locked copy; the password unlocks it.
* If the password is lost, getbased cannot recover the shared copy.
* If someone has both the link and password, they can import the shared profile until it expires or you stop sharing it.

On the official app, the browser sends the encrypted envelope directly to getbased's dedicated share service. The static application host does not receive the profile. The service stores the opaque envelope, expiry and deletion state, and a keyed identifier used for abuse controls; like any network service, it can observe connection metadata. It does not receive the password or profile plaintext.

The share database is intentionally not retained in backups. A service outage or data loss can therefore make an active link unavailable before its expiry. This does not affect the source profile in the sender's browser, and you can create a new link when the service is available.

<Note>
  A shared copy is a time-limited handoff, not a durable backup. Keep a regular export or folder backup for recovery.
</Note>

For your regular backup and migration options, see [Export and import](/guides/export-import), [Backup](/guides/backup), and [Sync across devices](/guides/cross-device-sync).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.