The short version
You connect your own Bee account. Always Near sends the conversation text you approve, without topic filtering or identifier redaction, through a short-lived encrypted path for AI-assisted analysis. It keeps structured alerts and summaries, not a permanent transcript. The current trial does not retain conversation evidence excerpts. You choose the trusted contacts who receive information. AI can be wrong, so every output must be verified.
1. Your Bee, your account
The Bee wearer or controller creates the Always Near account. One active owner account connects to one Bee account. Family members, friends, and caregivers are invited as trusted contacts; they do not own the Bee connection and cannot expand sharing beyond what the owner authorizes.
2. Before information leaves the collector
No topic exclusions, credential-keyword blocking or identifier redaction is applied to conversation input. Previously saved private phrases are no longer used after you accept this policy. The companion shows the selected conversation parts locally and asks you to approve them before upload. Any sensitive values present in an approved part, including card numbers, PINs or passwords, will be sent to Always Near and Amazon Bedrock for analysis. Keep that review window private. Avoid uploading highly sensitive information or conversations you do not have permission to use.
3. Short-lived analysis
Once Bee processing is enabled, approved, unfiltered text will be encrypted in transit and enter an encrypted processing queue. Normal queue retention is no more than 15 minutes; failed processing can remain in a dead-letter queue for no more than one hour. Amazon Bedrock is the service for schema-constrained extraction and rendering, with request-body and model-invocation logging disabled before use. A processing message is deleted after successful analysis or expires under the short retention controls.
4. What we keep
- Short source-language and recipient-language summaries.
- Detected language, category, normalized time references, confidence, attention level, and model/prompt version.
- Non-text source references, delivery status, preferences, acknowledgements, feedback, and content-free security or deduplication metadata.
- No conversation evidence excerpt or speaker-name list is retained by the current trial.
Structured alerts, generated summaries, and content-free processing completion records are scheduled to expire 90 days after creation; new account requests do not return expired structured alerts. Database deletion may lag while time-to-live cleanup runs; point-in-time backups may retain prior copies for up to 35 days after deletion. Account preferences, consent records, and other security records follow the separate retention description in our Privacy Policy.
We do not intentionally write the full conversation or an unredacted excerpt to application databases, permanent object storage, logs, traces, analytics, or error reports.
5. AI use and training
AI helps identify possible signals, summarize them, and render them in each recipient’s language. Conversation text is treated as untrusted data, not as instructions to the AI. Outputs are constrained to defined fields and then checked by application rules. These output checks reject recognized sensitive values and copied source text; they do not redact the input sent to AI and are not a guarantee that every sensitive value is recognized.
Famplified does not use your conversation content to train a general-purpose AI model or sell it as training data. Amazon states that Bedrock customer inputs and outputs are not used to train its base models or shared with model providers. Provider safety, abuse, and retention controls can vary by model and configuration, so we select and configure services to minimize provider retention and will disclose a material change before using a materially different practice.
6. What AI cannot promise
AI may confuse speakers, mishear words, mistranslate, misunderstand context, overstate a concern, or miss one completely. Alerts are potential signals, not verified facts. Summaries are not a complete account of a day, and silence is not an “all clear.” Always Near does not make medical diagnoses or emergency determinations. Verify outputs with the person involved and appropriate professionals.
7. Sharing and control
You select trusted contacts, categories, cadence, language, and delivery channels. Each contact uses their own confirmed email and independently opts in; the wearer cannot do it for them. When available, email contains only a neutral notice and sign-in link, not conversation text, evidence or sensitive alert details. Linked views recheck identity and current wearer permission. Email delivery depends on service availability, current wearer permission and the recipient's saved opt-in.
Phone ownership uses a personally requested AWS Notify verification text when available. Always Near processes the entered code transiently, stores only keyed digests rather than plaintext codes, and checks ownership of the exact current number before a call. No CALL-E verification call or SMS updates are sent. Confirmation never opts you into notices. A separate neutral test call requires a confirmed number and its own request consent. Notice calls additionally require current wearer permission and personal category-specific opt-in.
Ten attempted CALL-E calls per owner account per UTC month are shared across contacts. Test/notice and failed or uncertain attempts count, including earlier reserved voice-confirmation attempts; SMS verification does not consume call attempts. CALL-E receives the phone, locale and fixed test/category-summary instructions, never a verification code, Bee text, private signal prose, names or evidence. Notices preserve uncertainty and encourage portal review or checking email if enabled, without claiming email was sent. Anyone answering could hear a category; neutral voicemail instructions are best effort. Always Near is not an emergency service. CALL-E may record/transcribe under its own retention practices; Always Near does not fetch those recordings, and its seven-day evidence limit does not apply to them.
Availability is shown in settings; current calling is limited to the designated owner trial, with automatic notices separately gated. Verification texts have a separate availability switch and request limit; they are not SMS alert notices. You can remove contacts, turn off sharing, disconnect Bee or request deletion. Withdrawal stops future processing after it takes effect, not an already submitted call or completed processing.
8. Lawful use around other people
Bee-derived content may include other speakers. Recording and monitoring laws vary by location and context. The account owner is responsible for providing notices and obtaining permissions required by law and for avoiding places or conversations where capture would be inappropriate or unlawful.
9. Questions
For data or AI questions, access requests, or deletion requests, contact Famplified LLC at info@email.famplified.com.