Security

1. Encryption

1.1 Encryption in Transit

Connections between your browser or mobile device and Amoviti are protected using Transport Layer Security (TLS).

Information submitted to Amoviti is transmitted over encrypted connections rather than in plaintext. TLS is designed to protect information against interception or unauthorized disclosure while it travels between your device and Amoviti.

1.2 Encryption at Rest

Information stored by Amoviti is hosted in the United States and encrypted at rest using AES-256 encryption provided through our cloud infrastructure.

Encryption at rest is designed to protect stored information against unauthorized access to the underlying storage media or backups. It does not, by itself, prevent access to information through authorized application or administrative systems.

1.3 Vault Documents

Documents stored in the Amoviti Vault receive the same baseline protections as other stored information, including:

• TLS encryption while transmitted;
• AES-256 encryption at rest;
• server-side access controls;
• household-level data isolation; and
• access controls governing people to whom you intentionally provide information.

Amoviti can access documents stored in the Vault through its application and administrative systems. This capability supports features such as document search, reminders, expiration alerts, document processing, automatic organization, the Family Assistant, and other functionality provided by the Service.

Amoviti does not provide end-to-end encryption or client-side encryption that prevents the Service from accessing Vault document contents. The Service is not a zero-knowledge storage system, and users should not interpret its encryption measures as meaning that Amoviti is technically unable to read stored documents.

1.4 What Encryption Protects — and What It Does Not

Encryption in transit and encryption at rest address different security risks.

TLS protects information against interception while it is transmitted between your device and Amoviti. AES-256 encryption at rest is designed to protect stored information if the underlying storage media or backups are obtained by an unauthorized party. These measures provide important layers of protection, but neither prevents Amoviti from accessing document contents through authorized application functionality or administrative systems.

Neither measure, by itself, prevents access by an individual who obtains sufficiently privileged access to systems capable of accessing document contents. Encryption in transit and at rest therefore should not be understood as a barrier between you and Amoviti or as a guarantee against all forms of unauthorized access.

This limitation follows from the Service's architecture. Features such as document search, expiration and renewal reminders, automatic organization, document processing, and the Family Assistant require the Service to process relevant document contents in readable form. Amoviti does not offer a zero-knowledge mode in which document contents are inaccessible to the Service.

If you store highly sensitive records, such as passports, wills, financial statements, insurance records, or legal documents, you should understand that Amoviti is technically able to access those documents through its systems, subject to applicable access controls and operational procedures.

1.5 How Amoviti Limits Its Own Access

Because the Service's architecture permits access to stored document contents, Amoviti uses technical and organizational controls intended to restrict, monitor, and govern that access. These controls are intended to reduce unnecessary or inappropriate access without representing that Amoviti's technical ability to access documents has been eliminated.

Least-privilege access. Access to production systems capable of reaching stored document contents is restricted to authorized personnel and limited to the permissions reasonably required for their assigned responsibilities.

Automated routine processing. Routine Service operations are performed through automated processes. Personnel access to document contents is not intended to be part of ordinary Service operations.

Administrative access logging. Administrative access to systems capable of reaching stored document contents is subject to applicable logging, retention, and review controls. The scope and retention of such records are governed by Amoviti's implemented security and audit procedures.

Controlled exceptional access. Access for exceptional purposes, such as investigating a suspected security incident, responding to a support request initiated by a user, or complying with valid legal process, is governed by applicable authorization requirements and documented procedures, rather than unrestricted or ad hoc access.

Restrictions on use and sale. Amoviti does not sell users' documents or their contents. Any additional representation concerning the use of document contents to train general-purpose AI models is subject to the applicable contractual commitments, subprocessor terms, and documented AI-processing policies.

These safeguards, together with encryption and server-side access controls, are intended to reduce the risk associated with Amoviti's ability to access stored information. They do not eliminate that ability or guarantee that unauthorized access, misuse, or disclosure can never occur.

The appropriate expectation is that Amoviti can access document contents as necessary to provide the Service and that such access is subject to applicable authorization, security, monitoring, and governance controls rather than being technically impossible.

2. Account Authentication

2.1 Passwordless Authentication

Amoviti does not use traditional account passwords.

You may authenticate using:

• a six-digit verification code delivered to your registered email address; or
• Google single sign-on.

Because Amoviti does not maintain an account password, there is no Amoviti account password for an attacker to steal from an Amoviti password database. This does not eliminate the risks associated with compromised email accounts, compromised identity-provider accounts, stolen sessions, or other authentication attacks.

On supported mobile devices, you may additionally enable biometric authentication, such as Face ID or fingerprint authentication. Biometric verification is performed by the device operating system. Amoviti does not receive or store your biometric information.

2.2 Verification Codes

Authentication codes are subject to security controls designed to reduce unauthorized use, including:

• expiration after ten minutes;
• a maximum number of verification attempts;
• rate limiting;
• a cooldown period between code requests;
• daily request limits; and
• server-side invalidation and destruction after a code is used, expires, or becomes exhausted.

2.3 Protecting Your Email Account

Your registered email account is an important security boundary for your Amoviti account.

Anyone who can access that email account may potentially request or receive an Amoviti sign-in code. You should therefore protect your email account with a strong, unique password and, where available, multi-factor authentication.

2.4 Loss of Email Access

Your registered sign-in email is currently the primary means of accessing your Amoviti account.

Amoviti does not maintain a traditional password-reset mechanism, and support personnel cannot bypass authentication to sign you into an account through an alternative method.

If you lose access to your registered email address, you should first recover that email account through your email provider.

Additional account-recovery mechanisms may be introduced in the future. Amoviti will update this page before materially changing the authentication or recovery methods available to users.

3. Additional Verification for Sensitive Actions

Certain higher-risk actions require additional verification even when you are already signed in.

Examples include:

• exporting account information;
• deleting your account;
• changing certain emergency or post-death release settings; and
• making changes that materially expand the information that may be released to another person.

Depending on the action and device, Amoviti may require a fresh email verification code and/or supported mobile biometric verification.

The server validates the required authentication before the requested action is performed. Client-side application controls alone cannot bypass the server-side authorization requirement.

4. Household-Level Access Controls

Amoviti uses server-side access controls to isolate household information.

A household has a single account owner. Other individuals do not receive general household membership or unrestricted access to household information.

Access by another person occurs only through mechanisms intentionally configured by the account owner, including:

• documents intentionally shared with that person;
• emergency workflows activated according to their configured conditions; or
• post-death instructions and release mechanisms configured by the account owner.

Database security rules enforce household-level access restrictions on the server. A request for information belonging to another household is intended to be rejected by the underlying access-control layer rather than merely hidden by the user interface.

Household-level isolation governs access between users and households. It does not mean that Amoviti itself is technically unable to access document contents through its authorized systems.

No access-control system eliminates every security risk. Amoviti therefore uses additional authentication, monitoring, auditing, and operational safeguards described on this page and in our Privacy Policy.

5. Audit Logging

Amoviti maintains an audit trail for significant actions performed through the Service.

Depending on the action, the audit trail may record:

• who performed the action;
• what type of action was performed;
• the affected record or resource;
• when the action occurred; and
• relevant security or access information.

For shared or released documents, document access and download activity may also be recorded.

The audit trail is designed to record activity without recording the substantive contents of your documents. Administrative access to systems capable of reaching stored document contents is governed by the applicable logging and audit controls described in Section 1.5.

Audit records are retained according to the retention periods described in the Privacy Policy and applicable security and audit procedures.

6. AI and Automated Document Processing

Amoviti uses automated processing to help identify and organize documents and to provide certain AI-assisted features.

6.1 Document Identification

Where automatic identification performed on your device cannot identify a document, Amoviti may process the document within its cloud environment to determine its type.

The initial identification process does not consume an AI credit.

Additional document analysis and certain Family Assistant functionality may consume AI credits according to the applicable plan.

6.2 Processing Environment

AI-related processing for Amoviti occurs through enterprise services within Amoviti's cloud environment in the United States.

Amoviti does not intentionally send documents to public or consumer AI services for this processing.

Where third-party AI infrastructure is used as part of the Service, the applicable contractual and data-processing terms govern the provider's handling of information. Amoviti's statements concerning the use of customer documents to train or improve AI models are governed by its applicable contractual commitments and documented AI-processing policies.

6.3 Health Documents

Health-related documents may be identified by document type, but Amoviti does not perform substantive content extraction from health documents through its document-processing workflow.

The handling of health information is further described in the Health Data Notice.

6.4 AI Accuracy

AI-generated classifications, extracted values, summaries, responses, and other outputs may contain errors.

AI may:

• misclassify a document;
• fail to identify information;
• extract an incorrect value;
• misunderstand context; or
• provide an incomplete or inaccurate response.

You should verify important information against the original document and should not rely solely on AI-generated information when making legal, financial, medical, insurance, tax, or other consequential decisions.

7. Data Location

Amoviti currently stores household information in the United States.

This includes, as applicable:

• documents;
• contacts;
• household records;
• emergency workflows;
• configuration information; and
• information used to provide the Service.

AI processing performed by Amoviti also occurs in the United States.

Certain service providers, such as payment processors, email providers, and infrastructure providers, may process limited information on their own systems. The Privacy Policy identifies the principal service providers and describes the categories of information they may receive.

8. Access Within Amoviti

Access to production information within Amoviti is restricted to individuals who have a legitimate operational need, subject to applicable authorization and access-control procedures.

Depending on the circumstances, authorized personnel may require access to production information to:

• operate and maintain the Service;
• troubleshoot technical problems;
• respond to support requests;
• investigate security incidents;
• investigate suspected abuse or misuse;
• maintain system security;
• comply with legal obligations; or
• perform other legitimate operational functions.

Access is intended to be granted individually and according to least-privilege principles rather than provided indiscriminately.

Administrative access to systems capable of reaching stored document contents is subject to applicable access-control, logging, retention, and review procedures. Exceptional access is governed by applicable authorization requirements and documented procedures.

Routine processing is automated, and personnel access to document contents is not intended to be part of ordinary Service operations.

These safeguards are intended to reduce unnecessary or inappropriate access. They do not mean that Amoviti is technically unable to access stored documents, and they cannot guarantee that authorized access will never be misused.

9. Third-Party Service Providers

Amoviti relies on carefully selected third-party providers for portions of its infrastructure and Service, including providers supporting:

• cloud hosting and storage;
• document processing and AI;
• network protection;
• email delivery;
• payment processing; and
• mobile application distribution.

Amoviti evaluates providers based on factors including security, reliability, and their ability to support applicable data-protection requirements.

Where appropriate, Amoviti enters into contractual data-processing terms with providers that process information on its behalf.

Third-party providers operate their own systems and security controls. Amoviti cannot guarantee the security of systems that it does not directly control.

The Privacy Policy identifies the principal providers used by Amoviti and describes their respective roles.

10. Security Practices We Ask of You

Security is shared between Amoviti and its users.

You should:

• protect the email account associated with Amoviti;
• use a strong, unique password for your email account;
• enable multi-factor authentication on your email account where available;
• keep your computer and mobile devices updated;
• protect your devices with a passcode or biometric authentication;
• never share an Amoviti sign-in verification code;
• understand that Amoviti will not ask you to provide your verification code;
• avoid forwarding document-sharing links or access codes intended for another person;
• periodically review documents and information you have shared;
• periodically review your emergency workflows and designated recipients; and
• promptly report suspected unauthorized access.

If you believe your account may have been compromised, use the Sign out everywhere functionality available in Settings → Privacy, where available, and contact Amoviti at security@amoviti.com.

11. Security Incidents

Amoviti maintains processes intended to detect, investigate, contain, remediate, and learn from security incidents.

If Amoviti determines that personal information has been lost, exposed, accessed, or acquired in circumstances requiring notification under applicable law, Amoviti will provide notifications to affected individuals and/or regulators as legally required.

Where appropriate, notifications may describe:

• what occurred;
• the categories of information involved;
• actions taken by Amoviti;
• steps individuals can take to protect themselves; and
• additional information that becomes available during the investigation.

Security investigations can develop over time. Initial information may therefore be incomplete, and Amoviti may provide supplemental information as the investigation progresses.

The Privacy Policy contains additional information regarding Amoviti's handling of security incidents and privacy obligations.

12. Security Testing and Continuous Improvement

Security is an ongoing process.

Amoviti works to improve security through activities that may include:

• reviewing application and database access controls;
• reviewing application code;
• maintaining dependencies and infrastructure;
• monitoring systems;
• applying rate limits and abuse protections;
• investigating security events;
• correcting identified vulnerabilities; and
• evaluating changes to infrastructure and security controls.

For security reasons, Amoviti does not publicly disclose every internal control, configuration, threshold, detection mechanism, or security procedure.

The absence of a particular control from this page should not be interpreted as confirmation that the control does or does not exist.

13. Vulnerability Reporting

If you believe you have discovered a security vulnerability affecting Amoviti, please report it to:

security@amoviti.com

Please provide sufficient information to reproduce and investigate the issue and allow Amoviti a reasonable opportunity to address the vulnerability before publicly disclosing it.

Amoviti does not currently operate a paid bug-bounty program.

Amoviti does not intend to pursue legal action against security researchers who act in good faith and who:

• avoid accessing or modifying information that does not belong to them;
• avoid unnecessary privacy violations;
• avoid service disruption;
• do not conduct social engineering against Amoviti personnel or users;
• do not intentionally harm the Service or its users; and
• promptly report discovered vulnerabilities through the appropriate channel.

This vulnerability-reporting approach does not authorize conduct that violates applicable law or the Terms of Service.

14. Security Limitations

Security controls reduce risk but cannot eliminate it.

No online service, network, computer, mobile device, authentication method, or storage system can be guaranteed to be completely secure.

Accordingly, Amoviti does not represent or warrant that:

• unauthorized access will never occur;
• information will never be lost or disclosed;
• the Service will never experience an outage;
• every security vulnerability will be discovered before exploitation; or
• every security incident can be prevented.

In particular, TLS encryption in transit and AES-256 encryption at rest do not provide end-to-end encryption or prevent Amoviti from accessing stored document contents through its authorized application and administrative systems. The Service does not operate on a zero-knowledge basis.

Amoviti uses access controls and organizational safeguards intended to constrain its own access, but these safeguards do not eliminate the underlying technical capability or guarantee that access will never be misused.

This Security page describes Amoviti's security practices and does not create a warranty or modify the disclaimers, limitations of liability, or other provisions contained in the Terms of Service.

15. Frequently Asked Questions

Does Amoviti sell my information?

No.

Amoviti is a subscription-based service. Amoviti does not sell personal information and does not share personal information for cross-context behavioral advertising.

Amoviti is not a data broker.

Can Amoviti read my documents?

Yes.

Amoviti can access documents stored in your Vault through its application and administrative systems. This capability supports features such as search, reminders, expiration alerts, document processing, automatic organization, the Family Assistant, and other functionality provided by the Service.

Amoviti uses TLS to protect information in transit and AES-256 encryption to protect stored information at rest. These protections do not prevent Amoviti from accessing document contents through its authorized systems.

The Service does not provide end-to-end or zero-knowledge encryption. Access is subject to applicable household access controls and internal access restrictions, logging, and governance procedures described on this page and in the Privacy Policy.

Can another person see what I store?

Access by another person is governed by the sharing and emergency mechanisms you configure in Amoviti.

A household has one owner. Other people do not receive unrestricted access to the household.

A person may receive information when you:

• share a document with them;
• configure an emergency workflow that releases information to them; or
• configure post-death instructions that authorize release of information to them.

Can I export my information?

Yes.

Amoviti provides an export function through Settings → Privacy.

The export may include your records in machine-readable formats together with original document files.

Exporting your information requires additional verification, such as a fresh email verification code, as applicable to the device and authentication method.

What happens when I delete my account?

Account deletion begins a 90-day grace period during which signing back in can restore the account.

After the grace period, applicable household records, documents, contacts, assets, and workflows are permanently deleted according to the deletion process described in the Privacy Policy.

Certain information, including applicable audit, backup, and billing records, may be retained for longer periods where required for security, legal, accounting, or other legitimate purposes.

Deleting an individual item is handled separately and may remove that item immediately.

How do I report a security problem?

Email security@amoviti.com with enough information for Amoviti to understand and reproduce the issue.

Please provide Amoviti a reasonable opportunity to investigate and remediate the issue before publicly disclosing it.

16. Changes to This Security Page

Amoviti may update this Security page as its safeguards, infrastructure, providers, authentication mechanisms, or security practices change.

The Last Updated date at the beginning of this page identifies the current version.

For security reasons, Amoviti may omit or generalize details where publishing specific information could materially increase security risk.

Where applicable law requires notice of a material change, Amoviti will provide the required notice.

Nothing in this page limits or replaces the Privacy Policy, Health Data Notice, or Terms of Service.