docs(key-database): clarify which databases travel with profiles

- add "Which Databases Travel" section to key-database docs
- explain automatic vs manual mode and folder location deciding travel
- describe inactive databases and how profiles behave on other machines
- add caution that export UI text is easy to miss and advise checks
- add "What Goes In, and What Does Not" section to profiles doc
- clarify profile files include settings and keys inside the profile
- note logs, modules, and keys kept outside the profile are omitted
- advise using a KeyPackage to move keys that don't travel with profile

2 files changed, 65 insertions, 0 deletions

diff --git a/src/content/docs/advanced/key-database.mdx b/src/content/docs/advanced/key-database.mdx
index 3cd661c..fe39492 100644
--- a/src/content/docs/advanced/key-database.mdx
+++ b/src/content/docs/advanced/key-database.mdx
@@ -90,6 +90,10 @@ If you make a [profile](/advanced/profiles/) that holds its own keys, its key
 database travels with it. That is what lets you save a whole setup to one file
 and open it on another computer.
 
+**Automatic** mode puts the database inside the profile, so it travels.
+**Manual** mode usually points somewhere else, and then it does not. See
+[Which Databases Travel](#which-databases-travel) below.
+
 :::
 
 ## Switch Between Databases
@@ -195,6 +199,39 @@ Back up each database based on its engine:
 
 Store backups in a safe, encrypted place.
 
+## Which Databases Travel
+
+If you save a [profile](/advanced/profiles/) to a `.gfp` file to move it to
+another computer, some key databases come along and some do not.
+
+What decides it is **where the folder is**, not which mode you chose:
+
+- A database in a folder **inside the profile** travels. Its keys are packed
+  into the file. **Automatic** mode always puts it there.
+- A database in a folder **anywhere else** does not travel. **Manual** mode
+  normally points somewhere else, such as your system GnuPG home directory.
+
+A database that does not travel is still listed in the file by name, but its
+keys stay on the old computer.
+
+When you open the profile on the other computer, GpgFrontend tells you which
+databases were left behind. Each one shows as **Inactive** in the Key Databases
+settings until you edit it and point it at a folder on the new computer.
+
+:::caution[Nothing warns you loudly at export time]
+
+The export window mentions this in small grey text under **What goes in**. It
+is easy to miss.
+
+If you want your keys to travel with the profile, check that the database is in
+**Automatic** mode, or that the folder you picked in **Manual** mode sits
+inside the profile.
+
+If it does not, and you still want those keys on the other computer, move them
+across separately with a [KeyPackage](/advanced/key-package/).
+
+:::
+
 ## Tips
 
 - **Name databases by purpose**: `Personal`, `Work`, `Project Alpha`,
diff --git a/src/content/docs/advanced/profiles.mdx b/src/content/docs/advanced/profiles.mdx
index 2d7cbef..cd77bf1 100644
--- a/src/content/docs/advanced/profiles.mdx
+++ b/src/content/docs/advanced/profiles.mdx
@@ -145,6 +145,34 @@ somewhere safe.
 
 </Aside>
 
+### What Goes In, and What Does Not
+
+The file carries your settings, your saved state, your key groups and
+categories, and any keys kept **inside** the profile.
+
+It does not carry logs, modules, or **keys kept outside the profile**. That
+last one is the surprising one.
+
+Keys live outside the profile when your key database points at a folder
+elsewhere, such as your system GnuPG home directory. That happens when you
+chose **Manual** mode for the database, or when you told the profile to use the
+keys you already had.
+
+Such a database is still named in the file, but it arrives empty on the other
+computer, and shows as **Inactive** until you point it at a folder there.
+
+<Aside type="tip" title="Check before you rely on it">
+
+The export window lists what is going in, including a line for **Keys stored
+inside this profile**. If that line says nothing is there, your keys are not
+travelling.
+
+To send those keys too, use a [KeyPackage](/advanced/key-package/) alongside
+the profile file. See also
+[Which Databases Travel](/advanced/key-database/#which-databases-travel).
+
+</Aside>
+
 ## Open a Profile File on Another Computer
 
 You have two ways to do this, and they behave differently.