update what data is returned for customization

Author: ethanpalm

protected-pages/sending-data.mdx

@@ -10,9 +10,6 @@ When implementing protected pages, your system returns user data in a specific f
 
 ```tsx
 type User = {
-  expiresAt?: number;
-  groups?: string[];
-  content?: Record<string, any>;
   apiPlaygroundInputs?: {
     header?: Record<string, any>;
     query?: Record<string, any>;
@@ -22,38 +19,6 @@ type User = {
 };
 ```
 
-<ParamField
-  path="expiresAt"
-  type="number"
->
-  Session expiration time in **seconds since epoch**. If the user loads a page after this time, their stored data is automatically deleted and they must reauthenticate.
-  <Warning><b>For JWT handshakes:</b> This differs from the JWT's `exp` claim, which determines when a JWT is considered invalid. Set the JWT `exp` claim to a short duration (10 seconds or less) for security. Use `expiresAt` for the actual session length (hours to weeks).</Warning>
-</ParamField>
-<ParamField
-  path="groups"
-  type="string[]"
->
-  A list of groups that the user belongs to. Pages with a matching `groups` field in their metadata will be visible to this user.
-
-  **Example**: User with `groups: ["admin", "engineering"]` can access pages tagged with either the `admin` or `engineering` groups.
-</ParamField>
-<ParamField
-  path="content"
-  type="object"
->
-  Custom data accessible in your `MDX` content via the `user` variable. Use this for dynamic personalization throughout your documentation.
-
-  **Example**:
-  ```json
-  { "firstName": "Ronan", "company": "Acme Corp", "plan": "Enterprise" }
-  ```
-
-  **Usage in `MDX`**:
-  ```mdx
-  Welcome back, {user.firstName}! Your {user.plan} plan includes...
-  ```
-  With the example `user` data, this would render as: Welcome back, Ronan! Your Enterprise plan includes...
-</ParamField>
 <ParamField
   path="apiPlaygroundInputs"
   type="object"