Personal memory and privacy controls¶
Personal memory lets HiveAI retain a small preference you deliberately choose to save, such as how you like an explanation presented. It can reduce repeated instructions in later conversations. It belongs to your account within the current organization; it is separate from shared organizational knowledge, conversation history and scheduled work.
Availability: Personal-memory storage and owner controls are implemented in the backend, and the checked-in configuration enables them. The intended review-and-save journey is visible in 06 Final Screens. The inspected frontend still blocks HiveAI entry and has no connected HiveAI application. Management screens and deployed delivery remain unverified. This is a draft guide to implemented behavior and the designed experience.
What personal memory can do¶
You can explicitly confirm a preference for future use. The backend also supports reading your saved preferences, correcting one, pausing or resuming it, deleting it and exporting your currently readable preferences with their provenance. The task guide distinguishes the inspected save steps from controls whose full screen journey still needs delivery.
A saved preference is supporting context. It does not change permissions, authorize an action, establish a business rule or guarantee that every future answer will follow it. Saving “I prefer weekly summaries on Friday afternoons” does not create a schedule, send a notification or arrange an automatic summary. Those require their own supported operation and confirmation.
Who owns the information¶
Owner controls use the signed-in person's identity and current organization. They do not provide a way to select another employee's memory. Being an organization head does not turn the owner export into an export of everyone's preferences.
Personal memory is not the place for passwords, access tokens, medical information, sensitive personnel judgments or instructions to bypass controls. The service rejects certain unsafe statements, but that validation cannot guarantee that every inappropriate statement is detected. Keep preferences concise and limited to information suitable for the task.
Some internal memory records can carry classified source provenance. Their later use requires current authority to the original source; a saved record is not a permanent permission grant. The ordinary save interface does not establish a user flow for creating such classified records.
Lifecycle and practical limits¶
| State or action | Meaning |
|---|---|
| Reviewing a proposed preference | Nothing has been saved yet |
| Saved and active | Eligible for bounded selection in later supported conversations |
| Paused | Retained for the owner, excluded from later memory selection |
| Corrected | Wording changes; a paused preference stays paused |
| Resumed | A paused preference becomes eligible again |
| Deleted | Readable statement is cleared and excluded from normal memory lists, exports and prompt selection |
| Exported | A snapshot of the owner's currently readable saved items and associated provenance |
The current configuration allows up to 50 non-deleted preferences, including paused ones. Each statement is between 3 and 1,024 characters after trimming. Prompt preparation considers a smaller recent set, currently up to eight items within a 2,048-character total budget that also includes the explanatory wrapper. These are service settings and limits, not a promise to use every eligible preference.
Deletion does not promise that all related records disappear. Statement hashes, identifiers and selected audit or provenance evidence can remain. Earlier conversations, previously delivered answers and exported copies have their own lifecycle. See conversation and speech data for those boundaries.
For managers, executives and administrators¶
Evaluate personal memory as a convenience for an individual, not as an employee profile, organizational policy repository or management reporting source. A preference about writing style cannot authorize sending a message or making a decision.
Review whether people understand what is about to be saved, can recognize the actual saved outcome, and can distinguish pausing from deleting. Recovery should also cover changed access, a stale edit, a rejected statement, a full allowance and a save whose result is uncertain.
Access and configuration still apply to memory controls. If the feature or current access becomes unavailable, the ordinary controls may also be unavailable. Support needs a governed recovery process; this guide does not promise an always-accessible bypass.
Saving a preference through a conversation can involve normal conversation work and usage. A direct memory record does not by itself prove that the surrounding interaction is free. Use the conversation cost guidance and the actual workspace's terms; no price or savings claim is made here.
Start with a task¶
Read save and manage a personal preference for the intended save sequence, the behavior of each control, export limits and recovery. Initial user and business walkthroughs remain pending with the designated reviewer.