Protect information in alert previews
Review what an alert can reveal and reduce exposure on your phone, inbox and shared devices.
Written By Landon
Last updated 1 day ago
Treat Claim Raven SMS and email previews as potentially sensitive. Current narrow notification templates can include Claim Raven account context, a filename, submission GUID, claim ID, condition or research topic, deadline title, date, or status detail depending on the event. The checked templates do not intentionally place a Social Security number or full medical record in a message, but a filename, condition title, or user-entered label can still reveal personal information.
Use a private phone and inbox, limit previews, and never forward an alert or verification code to ordinary support.
Assume a preview can reveal claim activity
A short message can still show that you use Claim Raven, that a document or deadline exists, or that a claim-related event occurred. Anyone who can see your lock screen, shared inbox, notification history, forwarded mail, or synced device may see that context.
What current narrow templates may include
- Claim Raven branding and account or product context.
- A document filename or user-entered label, which can reveal a condition, provider, person, or record type if the name is descriptive.
- A submission GUID or other product tracking reference.
- A claim ID when the producer supplies one to the email template.
- A BVA analysis notification can name the analyzed condition or research topic in its SMS, email subject and body, or in-app message.
- A document status, reminder type, deadline title, date, or other event detail.
- A link or instruction to sign in and review more information.
What this inventory does not guarantee
- It does not prove that every current or future template contains only the listed fields.
- It does not make a sensitive filename safe simply because the product did not add it.
- It does not prove a provider, carrier, mailbox, forwarding rule, lock screen, wearable, or synced device keeps the preview private.
- It does not prove that deleting a message removes it from provider logs, backups, notification history, forwarded copies, or another device.
- It does not turn an alert into an official VA record or prove that VA received, accepted, or acted on anything.
- It does not mean ordinary Claim Raven support should receive the alert, claim facts, contact details, or an unredacted screenshot.
Reduce exposure before enabling alerts
Use private contact methods
Use a phone number and inbox you control. Avoid a work, shared-family, public, supporter-controlled, or forwarding mailbox unless you understand who can access it.
Use neutral filenames
Do not place an SSN, VA file number, full name, condition, diagnosis, provider, or traumatic event in a filename. Preserve the original record separately and use a neutral working-copy name when appropriate.
Limit previews and synced devices
Review lock-screen previews, notification history, watches, tablets, browser notifications, shared computers, mailbox forwarding, and account recovery access.
Keep account security current
Protect the phone, email account, and Claim Raven account with unique credentials and available multifactor protection. Never approve an unexpected sign-in or share a code.
Keep support requests minimal
Describe the page, approximate time, channel, and non-sensitive error text. Redact contact information and identifiers; do not attach the alert, notice, medical record, decision letter, or unredacted screenshot.
Use official records for action
Open VA.gov and the complete VA notice. An alert preview is not a safe substitute for the official details, instructions, or date.
Never send a verification code
Claim Raven support does not need your password, multifactor code, SMS verification code, Social Security number, VA file number, claim ID, medical record, decision letter, or full alert message to troubleshoot an ordinary settings problem.
If this does not work
A lock screen or shared inbox displayed claim context.
- Change preview settings and review every synced device or mailbox rule.
- Remove access from people or devices that should not see future messages.
- Review the affected account's recent sign-ins and security settings.
Treat the message as exposed to anyone who could view that surface; do not assume deleting one copy removes every copy or notification record.
A filename in the alert reveals a condition or person.
- Preserve the original record separately.
- Use a neutral working-copy filename for future organization when appropriate.
- Do not resend or forward the alert while asking for help.
Changing a future filename cannot retract an already delivered preview. Reduce future exposure and share only non-sensitive troubleshooting details.
You sent an alert or code to someone by mistake.
- Change any exposed password and secure the affected email, phone, and Claim Raven accounts.
- Review recent sign-ins and revoke sessions or access you do not recognize.
- Do not send more information to explain the mistake.
Use the current security and support channels for the affected account; an ordinary content reply cannot determine the scope of an exposure.
For a Claim Raven settings problem, share the page name, approximate time, channel, and non-sensitive error text only. Do not include the phone number, email address, message body, filename, tracking reference, password, code, VA identifier, notice, medical record, decision letter, or unredacted screenshot.
Review notification privacy before enabling a channel
Use a phone and inbox you control, reduce previews, and treat every alert as potentially sensitive.
Related articles
Was this helpful?
More in Notifications & alerts
Set up claim alert preferencesTroubleshoot missing SMS alertsCheck whether your number can receive SMSStill need help? Ask the team