What is an outside service, and what does it learn about me?
Checked against GilbApp d529620.
An outside service is run by someone else and used by an app for you; it learns who you are but cannot open your vaults.
Deeper
Also asked:
What is an outside service, and is it safe to connect one? A service run by someone else that an app may use for you; you do not connect it yourself. What keeps it safe: it learns your WebID, not your e-mail, and its short key cannot open your vaults and lasts at most 5 minutes.
An outside service is a service run by someone else, not a vault and not an app, that an app you signed in to may use for you, for example one that removes a photo's background. The app asks GilbPlatform for a short key for that one service, and sends it to the service with its request.
From that key the service learns your WebID, the web address GilbPlatform knows you by, the same address Copy my WebID copies. It also learns which app sent you and which of its actions the app was granted: the ones the app asked for, or every action of the service if the app asked for none. It does not learn your e-mail address. Knowing your WebID does not let anyone in.
The key does not open your vaults: your vaults refuse it, because it is made for that one service only. So the service gets nothing from your vaults by itself; it sees only what the app sends it, such as the photo to work on. The key lasts at most 5 minutes; after that the app must ask for a new one.
GilbPlatform makes such a key only for a service the platform owner, the one who runs GilbPlatform, has registered, only for an app that service allows, and only from a sign-in you made in that app with an e-mail code, once you have a vault. A sign-in to GilbApp in the browser cannot be used for it, and GilbApp itself uses no outside service. GilbPlatform does not ask you each time an app uses a service, and GilbApp has no screen that lists them. When the app ends your sign-in, it gets no new key; one already given keeps working at that service for at most 5 minutes: the answer on signing out says more.
An outside service cannot act for you in your vaults, such as reading or writing a record: that is not built. Only the platform owner registers a service; there is no screen for it, so the maker of a service asks the platform owner.
Source: GilbPlatform 498d29a0 (https://id.gilb.com/version read 2026-11-11, dirty false; contains 5be516b4), code read at 498d29a0: src/auth/outside-service-exchange.ts:1-23 (one request shape for every registered service; `sub` is the person's WebID, never the email; "The platform's own verifier refuses these tokens: every trusted-issuer entry pins its own audience, and this token's audience is the service address"), :162-191 (c2: only a person's DPoP-bound sign-in token that carries azp, i.e. names an app), :220-234 (sign-out gate: after the sign-in ended), :236-250 (c4: only an active registration), :259-290 (c5: only an app the service allows), :300-365 (c7: WebID only; The email stays in the source token; it is not copied forward; this person has no WebID yet: create a vault first), :367-382 (mint: sub = WebID, aud = the service's address, client = the app, scope = the granted actions; :297-298 and :400-417 grantedActions: scope left out or empty = every action; at most 300 s; no person-consent step anywhere in c1-c7); src/auth/outside-service-registry.ts:1-10 (Only the owner's CLI (`scripts/outside-service.ts`) writes one; no HTTP route), :35-48 (address, actions, allowed apps, contact); scripts/outside-service.ts:1-15 (register | update | suspend | resume | withdraw | list | show; refuses unless on the identity store). GilbApp ebd9415e (https://gilb.com/app/version.json): no call to /base/oauth/token or /base/service/ in src; no outside-service screen. REAL on production 2026-11-10: service token 300 s, `sub` the person's vault address ending /vault, never an email; `aud` the service address, `azp` the app. READ (handoff 2.2): a browser-session token names no app and is refused (403 unauthorized_client). Not built (handoff 3): an outside service acting for the person in their vault (C8 ActForUser); a screen to register or manage services. GilbVeda: t:OutsideServiceRegistration (Suggested: "a service run by someone else (not a vault, not an app) that a signed-in person's app may call with a short-lived credential the platform makes for that service alone"), t:OutsideServiceAction (THE PLATFORM NEVER INTERPRETS THESE NAMES AND THEY GRANT NOTHING IN ANY VAULT); public read 2026-11-11; no type for the service itself (t:OutsideService 404): listed to mint. Confidentiality protocol: no customer, test account or service id named. Row: none yet (proposed Capability.Security.OutsideServiceLearnsWebIdOnly).