Nest Egg

Information Security & Data Protection Policy

A statement of the organizational, technical, and contractual measures maintained by Artunisia LLC in connection with the Nest Egg application, including without limitation authentication, bank-account linking via third-party data aggregators, storage, transmission, retention, and deletion of user information.

1. Parties, scope, and interpretive conventions

This Information Security & Data Protection Policy (the “Policy”) is published by Artunisia LLC, a California limited liability company (“Artunisia,” “Operator,” “we,” “us,” or “our”), in respect of the consumer-facing software application commercially known as Nest Egg (the “Service,” “Application,” or “Nest Egg”), including any related websites, application programming interfaces, backend infrastructure, and documentation made available under the Nest Egg brand.

For the avoidance of doubt, references herein to Nest Egg, the Service, or the Application shall be construed as references to the same offering operated by Artunisia, and nothing in this Policy shall be read to imply that Nest Egg is a separate legal person, a bank, a credit union, a money services business, a broker-dealer, an investment adviser, a fiduciary, a payment processor, or a party authorized to initiate, approve, or complete the transfer of funds belonging to any user.

This Policy describes security and data-protection practices applicable to information processed in connection with the Service. It is intended to be read together with, and not in derogation of, the Nest Egg Privacy Policy and Terms of Use. In the event of any inconsistency between this Policy and those documents regarding privacy rights, consumer disclosures, or contractual terms of service, those documents control as to their respective subject matter; this Policy controls as to the description of security measures, bank-connection safeguards, and related operational controls.

Capitalized terms used but not defined herein shall have the meanings ascribed in the Privacy Policy or Terms of Use, as applicable. Headings are for convenience only and shall not affect interpretation. The words “include,” “includes,” and “including” shall be deemed to be followed by the phrase “without limitation.” Words importing the singular include the plural and vice versa. References to “you” or “user” mean any natural person who creates an account, attempts to create an account, links a financial institution account, or otherwise accesses or uses the Service.

2. Nature of the Service; expressly limited capabilities

Nest Egg is a personal finance companion application designed to help users visualize savings goals (“Nests”), optionally connect financial accounts for display of balances and related account information, and interact with in-application conversational features. The Service is offered solely as a software tool for informational and organizational purposes.

Nest Egg does not move money. Nest Egg does not initiate ACH transfers, wire transfers, card payments, securities trades, or any other disposition of funds. Nest Egg does not take custody of user funds, hold deposits, extend credit, guarantee balances, or act as an intermediary with authority to debit or credit any linked account. Any appearance of balances, goals, projections, allocations, or progress indicators within the Service is a representation of data made available to Nest Egg for display and calculation purposes only, and shall not be construed as evidence of Nest Egg’s ability to access, control, transfer, or encumber those funds.

Without limiting the foregoing, and for further clarity: (a) Nest Egg has no capability to withdraw, deposit, transfer, or otherwise move money from or to any linked financial account; (b) Nest Egg does not request, receive, or store banking credentials in a form that would enable Nest Egg personnel to log into a user’s financial institution as the user; (c) Nest Egg’s bank-connection features, where enabled, are facilitated through a third-party data aggregation provider as described herein and are configured for read-oriented retrieval of account and transaction information; and (d) any user action that involves the actual movement of money occurs solely between the user and the user’s financial institution or other third parties outside Nest Egg’s control.

The Service is not personalized investment, tax, legal, or financial advice. Security measures described herein are designed to protect information within Nest Egg’s systems and do not constitute a warranty that third-party institutions, networks, devices, or users will be free from compromise, error, or misuse.

3. Roles and responsibility for information security

Artunisia maintains organizational responsibility for information security relating to Nest Egg. Day-to-day stewardship of security practices, including evaluation of controls, response to suspected incidents, and coordination of notices where notice is required by applicable law or by this Policy, is vested in Artunisia’s designated information-security personnel acting on behalf of the Operator.

Security ownership, for purposes of this Policy, means that Artunisia—and not any individual named in marketing materials, application store listings, or public biographies—is the party accountable for the design and maintenance of the controls described herein. Inquiries regarding security, suspected unauthorized access, or data incidents should be directed to hello@mynestegg.org. Communications sent to that address are treated as notice to the Operator for purposes of security reporting.

Nothing in this Section creates a personal guarantee, personal fiduciary duty, or personal liability on the part of any natural person associated with Artunisia. Security commitments herein are commitments of the Operator in its corporate capacity.

4. Authentication, session controls, and access gating

Access to authenticated areas of the Service, and access to bank-connection flows where bank linking is offered, is conditioned upon successful completion of Nest Egg’s sign-in process. The sign-in process ordinarily requires (i) presentation of an email address and password (or such other credential method as Artunisia may enable from time to time, including Sign in with Apple where available), and (ii) verification by means of a one-time code or equivalent challenge delivered to the user’s email address or other verified channel, prior to unlocking the remainder of the Application and prior to initiation of a bank-connection session.

Stated differently: Nest Egg is designed so that merely possessing a password, standing alone, is not treated as sufficient to open the full Application or to commence linking of financial accounts. An additional verification step is required so that access depends on control of both the password credential and the verified communication channel associated with the account. This layered approach is intended to reduce the risk that a compromised password alone would suffice for account takeover or for initiation of bank linking.

Where a user enables biometric unlock features offered by the device operating system (including Face ID or equivalent), such biometrics may be used locally on the device to unlock credentials stored in the device’s secure storage (for example, Keychain or Keystore mechanisms). Biometric templates remain on the device under the control of the operating system vendor’s security architecture. Nest Egg does not receive, store, or process facial maps, fingerprint templates, or other biometric source data. Biometric unlock is a convenience for local credential retrieval and is not a substitute for the email-based verification factor that gates Application access and bank-connection initiation as described above.

Artunisia requires multi-factor or second-factor authentication for administrative and vendor consoles used in the operation of Nest Egg that materially affect production systems—including, as applicable, hosting, authentication, bank-aggregation, and source-code repository platforms—so that privileged operational access is not dependent on a single password alone. Users remain responsible for safeguarding their own passwords, email inboxes, and devices.

5. Transmission security

Nest Egg transmits information between the user’s device and Nest Egg’s backend systems using encrypted transport protocols customary for modern web and mobile applications, including HTTPS / TLS for network traffic between the client and Nest Egg services. The purpose of such encryption in transit is to reduce the risk that data traversing public networks could be inspected or altered by unauthorized intermediaries.

Encryption in transit means that communications are protected while moving between endpoints under Nest Egg’s control or under the control of Nest Egg’s processors acting on Nest Egg’s behalf. Encryption in transit does not, and cannot, secure data once it resides on a user’s unlocked device screen, in a user’s email inbox, on a compromised endpoint, or within systems operated solely by the user’s financial institution or other independent third parties.

Users should connect to Nest Egg over networks they trust, keep devices updated, and avoid sharing verification codes. Nest Egg’s use of HTTPS is one element of a broader set of controls and is not offered as a stand-alone warranty of absolute confidentiality under all conditions.

6. Storage, hosting, and encryption at rest

Nest Egg application data is hosted with infrastructure providers that provide disk-level or storage-volume encryption for data at rest as part of their platform offerings. In practical terms, the database and related storage media used to persist Nest Egg records are encrypted by the hosting environment such that physical media, if removed without authorization, would not yield plaintext application data without the corresponding cryptographic keys managed within that environment’s security model.

Encryption at rest, as used in this Policy, refers to protection of stored bytes on disk or equivalent persistent media. It is complementary to, and distinct from, encryption in transit. Together, encryption in transit and encryption at rest are intended to address different threat scenarios: interception during communication, and unauthorized access to underlying storage media, respectively.

Nest Egg further applies application-level protections to certain sensitive secrets associated with bank linking, as described in Section 7. Hosting-provider encryption and Nest Egg’s additional handling of tokens are cumulative measures; neither displaces the other.

7. Bank connections, Plaid, tokens, and the limits of what Nest Egg receives

Where bank linking is enabled for a user, Nest Egg uses Plaid (or such successor or alternative aggregation provider as Artunisia may engage) to facilitate connection between the user and the user’s financial institution. Plaid’s services are subject to Plaid’s own terms and privacy policy. Nest Egg does not operate the financial institution’s login screens, does not receive the user’s bank password through Nest Egg’s own forms for the purpose of logging into the bank as the user, and does not store bank passwords in Nest Egg’s application database.

Restated for clarity: when you link an account, you authenticate with your institution through the aggregation provider’s flow. Nest Egg’s systems are configured to receive account-related information such as balances, account identifiers necessary for display, and transaction data used to power Nest Egg features— not your bank password. Nest Egg still only receives transactions and balances (and related fields needed to render those features), even in circumstances where a financial institution’s interface might display or request account and routing numbers in other contexts. Possession or display of routing and account numbers in banking interfaces does not expand Nest Egg’s role into money movement.

Access credentials issued by the aggregation provider (commonly referred to as access tokens or similar credentials) that allow Nest Egg’s backend to retrieve linked-account data are treated as sensitive secrets. Such tokens are encrypted prior to storage in Nest Egg’s systems, using keys and procedures designed so that the mobile Application itself cannot read those stored tokens in plaintext from Nest Egg’s servers as an ordinary client. The Application requests data through Nest Egg’s authorized backend pathways; it does not hold a user-readable copy of production access tokens for linked institutions.

Nest Egg does not retain the full raw bank payload in an unrestricted archival form for general reuse. Nest Egg retains the fields and derived records it needs to operate the features shown to the user—balances, transactions, institution metadata, and similar display-oriented data—rather than indefinitely warehousing complete unmodified aggregator responses beyond operational need.

Bank-related webhook notifications and callbacks are validated. Nest Egg rejects bank webhooks unless the signature, authenticity check, or equivalent verification mechanism configured for that integration succeeds. Unsigned, improperly signed, or otherwise unverifiable webhook traffic is not treated as authoritative instruction to alter account state.

Again, and without limitation of Sections 2 and 7: Nest Egg does not move money; Nest Egg’s bank connection is for informational retrieval and display; Nest Egg does not see your bank password; Nest Egg cannot initiate transfers from linked accounts; and Nest Egg’s receipt of balances and transactions is not authority to dispose of funds.

8. Minimization, purpose limitation, and “need to know”

Artunisia designs Nest Egg’s data handling so that information collected in connection with bank linking and account use is oriented toward providing the Service: showing progress toward Nests, surfacing balances and activity the user has chosen to connect, supporting authentication, and maintaining application state. Nest Egg does not sell personal information. Nest Egg does not use linked bank data to serve third-party advertising.

Operational access to production systems and production data is limited to personnel and automated systems that require such access to build, operate, support, or secure the Service. “Need to know” in this context means access is not granted merely by virtue of association with Artunisia, and production credentials are subject to the second-factor requirements described in Section 4.

To the extent Nest Egg uses subprocessors (hosting, authentication, analytics if any, model providers for conversational features, or aggregation providers), those parties process information as described in the Privacy Policy and under contractual or platform terms applicable to those services. This Policy’s description of Nest Egg’s controls does not replace those parties’ own security programs, but Nest Egg selects and configures such services with security and privacy considerations in mind.

9. Retention, deletion, and residual copies

Account information, Nest configurations, chat or companion interaction records, and bank-derived display data associated with an active account are retained while the account remains open and as needed to provide the Service. Retention while the account exists is the default posture: Nest Egg keeps what it needs to show you your nests, history, and linked balances, and does not maintain a separate public archive of deleted accounts for general browsing or marketing reuse.

When a user deletes an account through Nest Egg’s deletion flows (or when Artunisia deletes an account in accordance with the Terms of Use), Nest Egg undertakes to remove the login credentials and associated application records from active systems, and to request that the aggregation provider remove or revoke the corresponding bank connection so that Nest Egg’s ongoing ability to retrieve that institution’s data ceases. Deletion is intended to end Nest Egg’s active use of that account’s data for Service provision.

Notwithstanding the foregoing, transient residual copies may persist for a limited period in backups, logs, or disaster-recovery snapshots maintained for continuity and integrity of the Service. Such residual copies are not used as a living customer database, are subject to the same infrastructure protections as other stored data, and are overwritten or aged out according to backup rotation practices. There is no separate long-term archive maintained for the purpose of preserving deleted accounts beyond ordinary backup windows.

In short: while your account exists, your data stays so the app can work; when you delete, Nest Egg removes active records and asks the bank-link provider to disconnect; backups may briefly linger and then fall away; Nest Egg does not keep a shadow folder of deleted users for later exploitation.

10. Vulnerability management, dependencies, and platform currency

Artunisia reviews dependency and vulnerability alerts affecting Nest Egg’s software supply chain on a recurring basis. Critical or high-severity issues are prioritized for remediation. Nest Egg aims to address critical and high alerts within a short operational window measured in days, or to document a reasoned exception where immediate patching is impractical due to compatibility, vendor lag, or risk of regression.

Nest Egg is maintained on supported runtime and mobile platform versions appropriate to a contemporary iOS application and its backend. Staying current is itself a security control: unsupported platforms accumulate unpatched weaknesses. Backend hosting is provided by Nest Egg’s cloud database and application platform providers, which operate the underlying server fleet under their respective shared-responsibility models.

Users are encouraged to install Application updates when offered through the App Store or other official distribution channels. Security fixes delivered in updates are effective only when installed.

11. Monitoring, integrity of integrations, and rejection of untrusted signals

Nest Egg’s systems are configured to treat certain inbound signals—including bank webhooks—as untrusted until verified. Verification may include cryptographic signatures, shared secrets, or other authenticity checks. This practice exists so that forged or replayed messages cannot casually rewrite balances, unlink status, or other account state.

Nest Egg may log security-relevant events (for example, authentication failures, webhook rejection, or administrative access) for troubleshooting and incident review. Logs are used for operation and security of the Service and are retained only as long as reasonably needed for those purposes, consistent with the Privacy Policy.

12. Incident response and user notice

If Artunisia becomes aware of a security incident affecting Nest Egg that results in unauthorized access to, acquisition of, or loss of personal information in a manner requiring notice under applicable law, Artunisia will provide notice as required by such law, and will otherwise communicate with affected users in a manner appropriate to the circumstances, using contact information associated with the account (such as email) or in-Application messaging where available.

Users who suspect unauthorized access to a Nest Egg account should promptly notify hello@mynestegg.org, change passwords on Nest Egg and related email accounts, and review linked-institution connections. Prompt reporting assists Artunisia in investigating and containing potential misuse.

No security program eliminates all risk. This Policy describes measures Artunisia undertakes; it does not guarantee that incidents will never occur, that third parties will never be breached, or that every attempt at unauthorized access will be detected in real time.

13. Insurance and risk transfer

Artunisia evaluates cyber liability and related insurance coverages appropriate to an early-stage software business handling authentication data and bank-derived account information. Insurance, where obtained, is a risk-transfer mechanism for Artunisia and is not a product feature sold to users, not a guarantee of reimbursement to any particular user, and not a substitute for the technical and organizational controls described in this Policy.

Availability, limits, exclusions, and status of any insurance policy are matters between Artunisia and its insurers. Nothing in this Policy shall be construed as a representation that a particular claim by a user would be covered, paid, or prioritized under any insurance contract.

14. Third-party services; shared responsibility

Nest Egg depends on third-party platforms for hosting, authentication, device operating systems, application distribution, email delivery, optional model-powered conversational features, and bank data aggregation. Those parties maintain their own security and privacy programs. Nest Egg’s obligations under this Policy concern Nest Egg’s configuration and use of those services and Nest Egg’s own application logic.

Apple, Google (if applicable), Plaid, cloud hosts, and other vendors are independent controllers or processors as to their own systems. A security event at a third party is not automatically a Nest Egg event, though Nest Egg will take reasonable steps within its control if such an event affects Nest Egg users.

Links from Nest Egg to third-party policies (including Plaid’s) are provided for convenience. Nest Egg is not responsible for the content of third-party sites except to the extent required by law.

15. User responsibilities

Security is shared. Users agree to: choose strong unique passwords; protect email accounts used for Nest Egg verification; not share one-time codes; keep devices and the Nest Egg Application updated; use official distribution channels only; and promptly report suspected compromise. Nest Egg cannot secure an account whose credentials and inbox are willfully or negligently shared with others.

Users remain solely responsible for decisions made with information displayed in Nest Egg, including savings goals and interpretations of balances. Display of a balance does not create a Nest Egg obligation to preserve, insure, or transfer that balance.

16. Changes to this Policy

Artunisia may update this Policy from time to time to reflect changes in the Service, infrastructure, vendors, law, or security practices. The version published at mynestegg.org/security is the current Policy. Material changes may be communicated by updating that page and, where appropriate, by email or in-Application notice. Continued use of the Service after an update constitutes acknowledgment of the revised Policy to the extent permitted by law.

Periodic internal review of this Policy and related controls is conducted by Artunisia’s designated security personnel as part of ordinary operations. Review cadence may vary with the Operator’s risk assessment and is not conditioned on publication of individual review dates on this page.

17. Governing interpretation; no waiver of limitations

This Policy is a description of practices and intentions. It does not expand Nest Egg’s role into that of a bank or money transmitter; does not create rights beyond those provided by law, the Privacy Policy, and the Terms of Use; and does not waive disclaimers, liability limitations, or arbitration or venue provisions set forth in the Terms of Use, except where such waiver would be unenforceable.

If any provision of this Policy is held unenforceable, the remainder shall continue in effect. Failure to enforce any provision is not a waiver of future enforcement.

18. Restatement of core assurances (bank linking)

Because bank linking is a sensitive step, the following assurances are restated expressly:

These bullet points summarize—not replace—the fuller explanations in Sections 2 through 12. In any conflict between a short summary and a detailed section, the detailed section governs.

Questions regarding this Policy: hello@mynestegg.org · Artunisia LLC · Nest Egg · Privacy · Terms