EgoCraftAI · Avalogica app policies

Avalogica Privacy Policy

This document applies to the Avalogica app and is separate from the policies governing this website.

Last updated: October 23, 2026

I. Introduction

EgoCraft, Inc. (“the Company”), the creator of Avalogica (“the App”), values your privacy and is committed to safeguarding your personal information. This Privacy Policy outlines how both the Company and the App collect, use, store, and protect the information you provide when using our services. It also describes your rights regarding this information and how you can exercise them.

EgoCraft is responsible for the personal information it processes for the purposes described here, including as a controller where applicable data protection law uses that term. Privacy rights and requirements depend on the law that applies to you and to the processing.

This policy explains our practices. Using Avalogica does not substitute for a separate choice where consent is required. The feature permissions, withdrawal controls, and other choices described below remain distinct from accepting the App’s Terms of Use.

II. Information We Collect

A. Account Information and Content You Provide

Avalogica is an integrated platform for self-directed personal development. Its features process thoughts, conversations, reflections, writing, and information about personality and behavioral patterns. Depending on the feature, this information is stored on your device, processed by an AI provider, or retained in Avalogica’s cloud services. Cloud processing and storage are already part of some features; they do not depend on the future Cloud Memory Sync feature described below.

1. Account Information

When you create or use an account, we process an account identifier and, when supplied through sign-in or registration, your email address and display name. Account records may also include language preferences, creation and sign-in dates, and subscription status. Sign-in methods include Apple, Google, and email; guest access uses an anonymous authentication identifier rather than requiring an email address. An anonymous sign-in identifier does not make content associated with that account anonymous.

We use this information to authenticate you, manage access and subscriptions, and send essential communications. Account information is managed through Google Firebase services, including Authentication and Firestore. Apple processes in-app payments; Avalogica may retain transaction identifiers and verified subscription information to confirm access, but does not receive your card details.

Google may also process a phone number within its sign-in service. Avalogica does not request access to your phone number through Google sign-in.

2. User Content and Feature Data

User Content includes text, files, questions, profile information, memories, audio you record through supported features, and AI-generated responses. It can include sensitive information if you choose to provide it. The information processed depends on the feature you use:

  • Just Talk: Recorded speech is uploaded through Avalogica’s backend for transcription by OpenAI. We process and retain session text, requested responses, and session information to support saving and recovery. Optional emotional feedback estimates patterns from the words in your transcript, rather than analyzing vocal characteristics. These estimates are stored with the session. Just Listen controls whether you receive replies; it does not make transcription an entirely on-device process. Saved conversations preserve text rather than a permanent recording of the original audio. Just Talk does not automatically add its emotional feedback to your personality profile.
  • Reflection: We process your starting material, answers, follow-up questions, generated reflections, and related session records. Voice submissions use Google cloud transcription. Reflection uses Google Gemini through Vertex AI for questions, journal synthesis, and associated analysis. Reflection can produce an approved journal entry and, through the profile participation controls, observations and supporting evidence that contribute to your profile. Sessions and associated results use Avalogica’s backend and cloud storage, as well as local app records.
  • Profiles: We process information you provide about a profile, Baseline assessment answers and results, and participating Reflection observations. Results can include personality patterns, emotional tone, reasoning and certainty observations, changes over time, and passages supporting those interpretations. Baseline assessment analysis and participating Reflection analysis use Google Gemini through Vertex AI. These are personal inferences associated with a profile, not anonymous usage statistics. They are interpretive aids that may be incomplete or inaccurate, rather than medical diagnoses or definitive statements about identity.
  • Profile conversations: Profile Insight (Discuss This Profile) and Relational Dynamics (Relationships) send a limited selection of profile context and recent conversation messages to Google Gemini through Vertex AI, using Avalogica’s backend. The app asks you to accept the Google-specific processing disclosure before using these conversations. Continuing an existing thread can send its recent messages, including earlier replies generated by a different provider, to Google; older saved replies are not regenerated merely because the provider changes. Automatic context excludes raw assessment answers, journal and reflection text, transcripts, audio, unrelated conversations, and Global Memory. Real-person Memory is excluded; for other real-person profiles, names, images, and relationship notes are also excluded. Discuss This Profile can include fictional-profile Memory only through its separate inclusion choice; Relationships excludes Memory. Information you type into a conversation yourself is still submitted. These conversations do not automatically change profile assessment results.
  • Memories and personality instructions: When you ask Avalogica to create or update a memory, selected conversation text, a selected user or AI message, or material you provide can be sent to OpenAI. Updating or merging a memory can also send the existing notes. AI assistance for creating or revising authored personality instructions likewise uses OpenAI. This processing can occur directly between the app and OpenAI, rather than through Avalogica’s backend. Avalogica disables optional response storage for these memory and personality-instruction requests. This does not eliminate separate provider retention or temporary caching; see Section IV. Memories are saved notes for continuity and personalization, separate from Baseline and Reflection assessment results. The guidance for real-person notes emphasizes supplied information and attributed self-descriptions rather than new psychological conclusions; authored fictional personalities are treated separately. Generated notes can nevertheless omit, misstate, or overinterpret material. You can review and edit saved notes; they are not verified facts merely because they have been saved.
  • Journal: We store written entries and the reflections you approve, with dates, source information, and profile associations. Journal combines local records with approved Reflection records available through the backend. Removing an approved reflection from the Journal view does not erase the underlying reflection or its profile evidence; see Section V.
  • Compose: Projects can contain your writing, imported files or text, copies of material selected from Just Talk or Journal, writing briefs, outlines, drafts, revisions, and source references. Projects and their content are stored through Avalogica’s backend, with a local app cache. For supported AI requests, you review the selected material and writing instructions before authorizing submission to OpenAI. Imported material is an independent project copy; deleting its original does not automatically delete the Compose copy. Exporting or publishing content sends it to the destination you choose, whose own practices apply.
  • Shared reflections: If you choose to offer a reflection to Shared, we process the submitted text, moderation results, publication status, and a private ownership reference. Approved contributions can be read by other users without displaying your account identity. The contribution can display the reflection-pattern label shown before submission and an optional country you select; we process that selected information as part of your submission. This is an optional publication action, not automatic sharing of your Journal or profile. Section IV explains its limits.

Direct Chat and other conversation features process the prompts, identity definitions, memories, attachments, and responses involved in the interaction. Information is sent to the provider used by the selected model or feature, including OpenAI when an OpenAI model is selected. This provider choice is separate from the Google-backed profile conversations described above. Using Avalogica does not mean every provider listed in this policy receives all of your content.

Permission for Other-Person Profiles

Before submitting identifiable information about another real person for a profile or analysis, you must have that person’s permission for the information and intended analysis, including any AI processing involved. You are responsible for obtaining that permission and for accurately confirming it when asked. A confirmation does not authorize uses beyond the permission actually given. Fictional or hypothetical profiles must not be used to disguise identifiable information about a real person.

AI Processing Choices

The app presents separate AI-processing disclosures and choices for supported activities and profile categories. You can review the listed permissions in Settings ▸ Privacy & AI and withdraw permission for future requests covered by those controls. These permissions belong to the account or Guest identity on this device and are not transferred to another account or synchronized through iCloud. Compose approvals, fictional-profile Memory inclusion, Journal approval, profile participation, and public sharing remain separate choices. Withdrawing a permission does not undo processing already performed, retract material already sent to a provider, or erase saved results. It is not a switch that disables every AI feature.

3. Local Storage, iCloud, and Cloud Services

The app maintains local records and caches. Its Core Data library is configured for Apple CloudKit synchronization, subject to iCloud availability and your Apple account settings. This is distinct from Avalogica’s Google-hosted feature data and from device backups. The device and iCloud library can contain material used with more than one Avalogica account; changing Avalogica accounts does not create a separate device library. Deleting the app is not a request to delete cloud records, iCloud copies, or information already exported elsewhere. The Keep and Erase choices for account deletion are explained in Section V.

Avalogica’s backend uses Google Cloud and Firebase services to store and process feature data described above. Temporary uploaded audio is used for transcription and recovery rather than as a permanent audio archive. AI-provider processing and retention are separate from the copies managed by Avalogica.

Future Cloud Memory Sync: The previously described optional Premium feature for synchronizing selected conversation histories and identity memories through Firebase Cloud Storage remains a separate proposed feature. Its optional status should not be understood to mean all existing cloud storage is optional. We will update its disclosures before making it available in production.

Subject to our Terms of Use, you may use, share, and dispose of your User Content at your discretion. You are responsible for ensuring that your use of it complies with applicable law.

4. Contact Information (Support Interactions)

If you email our support team, we receive your email address, any name associated with it, the message, and any attachments you provide so we can respond and resolve your request. Support email sent to service@egocraftai.com is received and stored through Google Workspace. We do not use generative AI tools to summarize support correspondence or draft replies. Access to the support mailbox within EgoCraft is currently limited to one authorized person. We retain support correspondence while handling an inquiry. We review resolved routine support messages every three months and delete those that have been resolved for at least 12 months and are no longer needed. Relevant records may be kept longer for an ongoing matter or dispute, a security investigation, or a legal obligation. Provider recovery and backup cycles remain separate. You can request deletion through our Contact page, subject to applicable legal limits and separate provider recovery or backup cycles. Please include only information needed for your inquiry. Account and feature records stored in Firestore are separate from this support correspondence.

B. Technical, Diagnostic, and Usage Information

We automatically collect certain technical data so Avalogica can run reliably, diagnose crashes, and understand feature uptake. We do not sell this data, nor do we use it for third-party advertising or cross-app tracking.

Current Practices (Version 1.0)

  1. Device and Technical Data: (1) Device model, OS version, language, screen size (2) Identifier for Vendor (IDFV) (3) Basic performance metrics (load time, latency)
  1. Diagnostics and Crash Reports: Crash logs, stack traces, device information, and installation identifiers via Apple or Firebase Crashlytics. Technical identifiers can distinguish installations even when your name or email is not included.
  1. Usage Analytics: Firebase Analytics collects app usage events. Explicit Daily events can include content, edition, module, and source identifiers, actions, and outcomes. When you tap an external source link in Daily, an event can identify the selected source, including its destination URL. This records the source-link tap; it does not establish that the page finished loading or monitor subsequent browsing in Safari. Analytics can also include technical or installation identifiers; aggregated reports do not make every underlying event anonymous. These events are separate from the private writings, conversations, memories, and profile analysis described above.
  1. Network & Log Data: Backend and cloud infrastructure may process request times, IP addresses, browser or app information, and response status for service operation, abuse prevention, and troubleshooting. Log fields and retention depend on the service and its configuration; they do not all follow one 30-day period. These technical records are separate from saved content and profile analysis.
  1. Cookies & Web Tracking: Avalogica is a native iOS app; it does not set web cookies. If you visit our website, separate web cookies may apply (see site policy).
  1. Advertising Identifiers & Profiling: We do not integrate the Apple Advertising ID (IDFA), show third-party ads, or use profile inferences for third-party advertising. The personal analysis provided by Profiles and Reflection is described separately in Section II.A.

Future Practices (Expanded Analytics, opt-in)

  1. Device and Technical Data: Same data set; no change expected.
  1. Diagnostics and Crash Reports: Same; we may capture additional non-personal app-state to speed bug fixes.
  1. Usage Analytics: Any future Expanded Analytics feature would be separate from the current Share usage analytics control. We would describe the additional collection and request permission before enabling that future feature; it would be off by default.
  1. Network & Log Data: No change planned.
  1. Cookies & Web Tracking: No change.
  1. Advertising Identifiers & Profiling: Same (unless we introduce an ad-supported tier, in which case this policy will be updated and users will be asked for tracking permission).

How we use this technical and usage data:

  1. To diagnose crashes and ensure service uptime.
  1. To understand feature use and prioritize performance and usability improvements.
  1. To protect against fraud and abusive usage patterns.

Controlling analytics collection:

Open Settings ▸ Privacy & AI and use Share usage analytics to control new Firebase Analytics collection on this device. The current setting is enabled by default and is available in Guest Mode as well as with an account. It is saved on this device and is not synchronized through iCloud. Turning it off stops new collection; it does not delete events already sent. Crash reporting through Apple or Firebase Crashlytics remains separate from this setting.

We will update this section if our analytics scope expands or if we introduce advertising technologies.

C. Secure Payment Handling

Avalogica relies on Apple’s payment system for processing all in-app purchases, including subscription plans and other premium features. This ensures that your payment information is handled with the highest level of security and privacy.

  1. Billing and Processing: Apple is responsible for managing billing, processing, and charging for all transactions within Avalogica. Your payment details (such as credit or debit card information) are not accessible by Avalogica or EgoCraft, Inc. This means we never store or process sensitive payment information directly.
  1. Purchase Policies: By using Avalogica, you agree to follow the purchase rules and policies set by Apple, which can be accessed through your respective app store. These rules include refunds, subscription management, and other billing-related inquiries.
  1. Transaction Safety: All payments are processed securely through Apple’s ecosystem, ensuring your payment data is protected from unauthorized access or misuse. You can manage your payment options directly through your Apple account.

D. Account and Service Communications

We use contact information you provide to respond to support requests and for necessary account, security, or policy communications. Email-and-password sign-in supports password-reset emails through Firebase Authentication. Apple handles purchase receipts and billing communications for in-app subscriptions; these are separate from messages sent by EgoCraft.

EgoCraft is not currently sending promotional emails for Avalogica or using app activity or subscription history to personalize promotional emails. If we begin an optional marketing-email program, we will describe it, obtain any required permission separately, and provide a way to unsubscribe before sending those messages. The Website’s separate Legacy waitlist signup and requested updates are covered by the Website Privacy Policy.

III. How We Use Your Information

We use your data to operate Avalogica, support self-directed personal development, keep the service secure, improve performance, and stay in touch with you. The integrated features have the processing and storage practices described in Section II; proposed Cloud Memory Sync and Expanded Analytics remain separate future features.

A. Service Delivery and App Functionality

  1. Account Management: Authenticate you, associate records with the appropriate account and profile, and verify subscription access.
  2. AI Processing: Transcribe submitted audio; generate requested responses, reflective questions, writing assistance, profile interpretations, and memory or personality-instruction updates; and moderate content offered to Shared.
  3. Continuity and Storage: Save sessions, memories, approved reflections, profile observations and evidence, and Compose projects so you can revisit and develop your material. Records transferred between features may have independent lifecycles.
  4. Personal Development: Present patterns and changes in your contributions over time, with supporting context that helps you assess the interpretation. Profile analysis serves the personal-development features, not advertising targeting.
  5. Your Choices: Apply feature-specific choices, such as requesting a reply in Just Talk, enabling emotional feedback, allowing Reflection contributions to a profile, approving a journal entry, authorizing a Compose AI request, or offering a reflection to Shared. Turning off future processing does not necessarily erase existing results; deletion is addressed separately in Section V.

B. Personalization and User Experience

Memory in later conversations: Saved personality notes can be included as context when you converse with that personality. When Global Memory is active, its user information and preferences can be included automatically in supported later conversations, without selecting each note again. That context is transmitted to the provider handling the conversation, which may differ from OpenAI, the provider that created or updated the memory. Memory can therefore influence later responses. This is use of saved context, not training a model on your notes. The narrower exclusions for Profile Insight and Relationships described above still apply.

  1. Customization of Features Current: On-device settings (theme, font size, model favorites) personalize your app experience. Future: These preferences will sync across devices if Cloud Sync is enabled.
  1. Usage and Suggestions: Technical usage information can help us understand feature use and improve how features are presented. It is separate from private profile analysis and is not used for third-party advertising. Any future Expanded Analytics collection remains subject to the separate choice described in Section II.B.
  1. Performance Optimization: Technical usage and diagnostic information help us investigate reliability and performance. This information can include technical or installation identifiers.

C. Analytics and Performance Monitoring

  1. Usage Metrics: Firebase Analytics collects usage information as described in Section II.B. Share usage analytics in Settings ▸ Privacy & AI controls new collection on this device; it does not erase earlier events or control crash reporting.
  1. Crash Reporting Current and Future: Apple or Firebase Crashlytics collects crash logs and associated technical or installation identifiers as described in Section II.B.
  1. Testing and Optimization: Technical usage and diagnostic information can help us assess performance and usability. This does not authorize use of private user content for product-improvement research or evaluation datasets.

Private Content Is Not Used for Product Improvement

EgoCraft does not use your private writings, recordings, transcripts, memories, or profile inferences for general product-improvement research, evaluation datasets, prompt development, or model training. Processing your selected material to provide a feature you request, including personal analysis, memory updates, and writing assistance, is distinct from reusing it to improve the product. The technical usage analytics and diagnostics described elsewhere in this policy are separate from your private content.

D. Security and Fraud Prevention

We use account authentication and relevant technical records to help detect and prevent abuse and investigate security issues. Log information and retention vary as described in Section II.B. Material submitted to Shared undergoes the moderation described in Section IV; this does not mean private content is routinely read by company personnel.

E. Legal Compliance

We may process or disclose any of the information above to comply with applicable laws, court orders, or to defend our legal rights—both now and after Cloud Sync launches.

F. Communication and Notifications

We use relevant contact information for account assistance, support replies, and necessary service notices as described in Section II.D. Apple’s billing messages remain separate. Any future optional marketing communications would require the notice, permission where required, and unsubscribe choices described there.

We may invite optional feedback or survey participation. Choosing not to participate does not authorize unrelated use of your private content or affect your access to core features.

We will update this section—and the App Store privacy label—before releasing any feature that changes how your information is collected or used.

IV. Data Sharing and Disclosure

Avalogica may share your information with third parties in specific ways, all in accordance with this Privacy Policy. We work with a variety of third-party service providers to ensure that we can deliver the features and services available in Avalogica. We take care to only engage with providers that follow stringent security and privacy practices, but we cannot guarantee the security of information shared with third parties beyond our control.

A. Third-Party Service Providers

We share data with the providers needed for the feature you use, including AI processing, hosting, authentication, synchronization, payments, and diagnostics. The following list identifies current providers used by Avalogica; it does not mean that each provider receives every category of data. Legacy AI integrations that are not currently offered are excluded.

ProviderService DescriptionPrivacy and API Data References
Apple Inc.Sign in with Apple, in-app payments, iCloud/CloudKit synchronization and device backup services, and platform diagnosticsPrivacy Policy
AnthropicSelected chat responsesPrivacy Policy, Commercial Terms
Google, L.L.C.Gemini through Vertex AI for Baseline and Reflection analysis, Reflection generation, Profile Insight, and Relationships; Reflection speech transcription; other selected Google AI services; cloud hosting, authentication, and data management (Firebase)Google Privacy Policy Firebase Privacy and Security Google Cloud AI Data Governance
Mistral AISelected chat responsesPrivacy Policy, Commercial Terms and API Data Handling
OpenAI, L.L.C.Selected chat responses; Just Talk transcription, responses, emotional feedback, and generated speech; memory and authored personality-instruction processing; Compose assistance; moderation of Shared submissionsPrivacy Policy API Data Controls

A provider’s general privacy policy may cover its website and account information separately from its processing of API inputs on a customer’s behalf. Applicable API agreements and data commitments also matter; a link to an opt-out or retention option does not mean that the option has been enabled for Avalogica.

AI-provider retention: Sending content for processing is distinct from saving it in Avalogica. For example, disabling response storage in an OpenAI request does not guarantee zero provider retention. Depending on the API and configuration, separate abuse-monitoring records or temporary processing caches can remain. OpenAI’s API documentation states that API data is not used for model training by default unless sharing is enabled. Google Cloud’s documentation likewise separates restrictions on model training from retention for purposes such as abuse monitoring and temporary caching. Its applicable terms, service, and configuration determine that handling. Other providers have their own terms and settings. We do not make a blanket promise that all providers immediately discard all submitted content.

B. Other Data Sharing

Current Practices (Version 1.0)

Avalogica does not show third-party ads and does not share any data with advertising networks. In addition to the feature processing described above, we use trusted service providers such as Firebase for analytics and diagnostics. These services may process technical or installation identifiers; their data should not be assumed to be irreversibly anonymous.

Future Practices (possible ad-supported tier)

If we ever introduce an ad-supported version, we will give you clear notice in advance, request your consent where required (including Apple’s “Ask App Not to Track” prompt), and update this policy to explain exactly what data—if any—would be shared with advertising partners. Even in that scenario, we will never rent or sell your personal information.

In all cases, Avalogica does not rent, sell, or otherwise disclose your personal data to third parties for their independent marketing purposes.

Optional publication through Shared: An approved Shared reflection is visible to other users without displaying your account name or profile. Avalogica retains a private connection to the submitting account to manage ownership, withdrawal, and moderation. Text can still identify you or someone else through its contents, so the absence of an author name is not a guarantee of anonymity. Submitted text is processed for moderation, including through OpenAI. A contribution is available for up to 90 days unless removed earlier. You can withdraw it, but other readers may already have copied or captured it. Withdrawal does not delete your original journal entry.

Human Access to Content: Access by personnel acting for EgoCraft to private user content is limited to what is necessary to respond to support you request, handle security matters, or meet legal obligations. Authorized personnel determine internally whether access is necessary for one of these purposes; access must remain limited to that purpose and the relevant information. This does not authorize routine reading of private journals or conversations. Material you offer to Shared and related reports may be reviewed by authorized reviewers for moderation and safety. The AI-provider processing described above remains separate from these limits on company personnel.

C. Legal and Compliance Disclosures

We may disclose your personal information if required to do so by law or if necessary to: 1. Comply with a legal obligation or court order. 2. Protect our rights or the rights of others. 3. Investigate fraud, security breaches, or potential violations of our Terms of Use. 4. Respond to government requests.

D. Mergers or Acquisitions

If Avalogica (or EgoCraft, Inc.) is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. In such an event, we will notify you before your personal information is transferred and becomes subject to a different privacy policy.

For more information about the services provided by third-party vendors, or to review their privacy options, please refer to their individual privacy policies through the links provided above.

V. Data Retention

We keep your information only for as long as it is needed to operate Avalogica, comply with the law, and protect our legitimate interests. Retention depends on the kind of record and the feature that created it. A local copy, an Avalogica cloud record, an AI-provider processing record, and an exported or published copy can have different lifecycles.

A. Account Information

We retain account information, including your account identifier, email address where supplied, and subscription status, while maintaining your account. We keep it until you request deletion or the account is otherwise closed under our Terms of Use, subject to the deletion processes and legally required retention described below.

B. User Content and Feature Records

  • Saved content and analysis: We retain saved transcripts, approved journals, current profile results and their supporting evidence, and Compose projects until you delete them or request their deletion, subject to account closure and the legal-retention provisions below. These records can exist in Avalogica’s cloud services as well as in the app. Unfinished sessions and temporary processing records have shorter retention periods. Completing a session, closing a screen, or turning off further analysis does not itself erase previously saved content or results.
  • Saved memories: Memory notes remain in the app’s local library until changed or cleared and can be subject to the CloudKit synchronization described above. Editing or clearing notes does not retroactively change earlier conversation messages, independent copies, or material already processed by an AI provider. Profile removal and account deletion are distinct actions; clearing a profile’s local notes does not erase its separate backend analysis records.
  • Temporary audio: Just Talk and voice Reflection use temporary recordings for transcription and recovery. Just Talk attempts to delete backend audio after successful transcription. Their backend audio storage is configured to make recordings eligible for deletion one day after creation; physical deletion is asynchronous and is not guaranteed at an exact 24-hour instant. Failed or interrupted processing does not extend this storage rule. Device-side recovery copies, saved session text, and emotional-feedback results have separate lifecycles from the backend recording.
  • Unfinished Reflection records: Routine cleanup targets operational sessions older than 30 days and inactive continuity records older than 90 days, while preserving approved journals and their governed profile evidence. Routine session cleanup for Reflection and Just Talk is not yet fully active; cleanup targets should not be understood as guarantees that every unfinished record has already been removed. Account deletion, backend audio-storage deletion, and Shared expiry are separate processes.
  • Journal removal: “Remove from Journal” removes an approved reflection from the Journal presentation. The underlying approved record, Reflection analysis, and profile evidence remain. To request erasure beyond that view, use the deletion request process below.
  • Compose copies and suggestions: Imported source material remains an independent copy inside its project. Temporary AI operations, consent records, and unadopted suggestions are scheduled to expire seven days after creation; physical cleanup may follow asynchronously. Adopted material, project history, and minimal records preventing duplicate requests follow the project’s separate lifecycle. Cancelling a request does not undo processing that has already occurred at the provider.
  • Shared: Public contributions expire after 90 days or can be withdrawn earlier. A pending moderation copy becomes eligible for cleanup 30 days after submission. If a submission is rejected, its rejected sharing copy becomes eligible for deletion 14 days after the first rejection; retries do not restart that period. Managed cleanup is asynchronous, subject to legally required retention and the backup/deletion distinctions below. These periods concern the sharing copy, not your original Journal entry. Withdrawal ends public display and removes any retained candidate text, but does not by itself erase all separate ownership/status records or the original Journal. Copies made by readers are outside Avalogica’s control.
  • Device and iCloud copies: Device records, CloudKit synchronization, and personal backups must be considered separately. Uninstalling Avalogica does not erase server records or necessarily erase Apple-hosted copies. Apple settings govern your iCloud and device backups.

For the proposed Cloud Memory Sync feature, the existing plan remains to keep selected chats and memories until you delete them or disable that feature, and to provide a 30-day export or removal period after cancellation of the Premium tier that enables it. This proposed arrangement does not describe retention for the existing backend features above.

C. Account Deletion and Your Library

You can request account deletion through the app’s Delete Account controls or ask for help through Contact. In-app deletion requires identity confirmation and a final confirmation after preparation. Preparing a library briefly pauses online changes; preparation alone does not submit the final deletion request.

  • Keep my library (the default): Before final submission, the app saves and checks a separate readable archive of the account’s online material on this device. On-device writing and memories remain available in Guest Mode. Retained library and export lets you read the archive or save another copy. The retained library is a separate copy, not a continuing connection to the deleted online account.
  • Also erase my library: This separately chosen action erases the shared library on this device, including material used with other Avalogica accounts, and requests deletion of the synchronized library through iCloud. Synced deletion can affect other devices using that Apple account. Propagation depends on connectivity and iCloud availability; a pending iCloud erasure can require retrying. Exported copies and Apple-managed backups remain separate.

After the deletion request is accepted, the app signs out of the account and enters Guest Mode. Online cleanup continues automatically, including removal of the account’s Shared material, with a final check eligible after 24 hours. This is not a guarantee that every record is deleted at exactly 24 hours. You can use Check deletion status to follow the request. We will remove associated account and feature records from Avalogica’s active backend storage within 30 days unless a longer retention period is required by law. Residual backups, minimal deletion records that prevent removed material from being restored, and provider authentication, diagnostics, and AI-processing records follow their separate lifecycles described below. These distinctions do not waive applicable privacy rights.

Deleting an Avalogica account does not cancel an Apple subscription. Manage cancellation separately through Apple’s subscription settings.

D. Legal Retention Certain records (for example, payment receipts) may be kept for the period mandated by tax or accounting regulations, even after you delete your account. These records are stored securely and are not used for any other purpose.

E. Deletion Processes and Separate Provider Records

We use service deletion and cleanup processes for cloud records. Removing an active record is distinct from expiry of backup copies and from retaining minimal deletion records that prevent removed material from being restored. Deletion of Avalogica records also does not retract processing already performed by an AI provider or remove copies you or other readers exported. Applicable provider retention and legally required retention remain separate.

For example, Firebase’s published retention information states that Authentication removes associated authentication information from its live and backup systems within 180 days after the customer initiates user deletion. Firebase Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal from live and backup systems. These are provider service periods, not a promise of immediate physical erasure when the app enters Guest Mode. AI-provider records follow the separate handling described in Section IV.

We coordinate applicable privacy requests with providers processing information on our behalf and explain relevant retention limits. Provider documentation does not replace our responsibility to handle your request under applicable law.

VI. Analytics and Advertising Tracking

Avalogica uses third-party services to understand how the app is used and to keep it running smoothly. Today, we do not show third-party ads or engage in cross-app tracking. If that ever changes, we will ask for your explicit consent first.

A. Analytics (current version) We collect the technical usage information described in Section II.B to understand feature use and investigate reliability and performance. Reports may be aggregated, but underlying analytics and diagnostics can include technical or installation identifiers; aggregation does not make every underlying record anonymous. The Share usage analytics control and its limits are described in Section II.B.

B. Advertising (future, opt-in) If we introduce an ad-supported tier, we will: 1. Present Apple’s “Allow Tracking?” prompt before sharing the device’s advertising identifier (IDFA). 2. Update this policy to describe exactly what data is shared with ad partners. 3. Give you a setting inside Avalogica to switch off personalized ads at any time. Note that even with ads disabled, you may still see generic (non-targeted) ads.

C. How to limit or disable tracking 1. App Tracking Transparency (ATT) – On iOS you can disable cross-app tracking for Avalogica (or all apps) under Settings ▸ Privacy & Security ▸ Tracking. 2. Usage analytics – Inside Avalogica, open Settings ▸ Privacy & AI and turn off Share usage analytics to stop new Firebase Analytics collection on this device. This does not delete earlier events or turn off separate crash reporting. 3. Location services – Avalogica does not request location access. If we add location-based features later, you can revoke access in Settings ▸ Privacy & Security ▸ Location Services.

Opting out of analytics or ad tracking will not break core functionality, though some personalized suggestions or advertising (if added) may become less relevant.

VII. User Rights

You can contact EgoCraft about access to, correction of, or deletion of your personal information. Depending on your location and applicable law, you may also have rights to portability, restriction of processing, objection, withdrawal of consent, or complaint to a regulator. Legal rights can have conditions and exceptions; they are not determined solely by where a server physically stores the information.

A. Data Access and Portability

You can request a copy of personal information we hold about you, including relevant account details, content, and associated profile inferences. We will provide access and a portable copy as required by applicable law. Access may require safeguards for another person’s information or other lawful limits; we will explain any applicable limits rather than treating cloud storage as outside the request.

B. Change or Correct Data

You can request correction of personal information that is inaccurate or outdated. Where available, you may be able to make these updates directly within your account settings. If you are unable to change certain data, you can submit a request to us through our Contact page for manual assistance.

C. Data Retention and Deletion

You can request deletion of your personal information, including account information, saved content, and associated profile inferences, subject to applicable legal conditions and exceptions. A screen-level action can have a narrower effect than full erasure: removing an approved reflection from Journal does not erase its source analysis, and removing an original entry does not automatically erase an independent Compose copy. Likewise, local removal or uninstalling the app is not a request to erase Avalogica’s server records. Synchronized Apple records and backups must also be considered separately rather than assuming that every local deletion erases every iCloud copy.

To request account deletion, use the app’s Delete Account controls or contact us through our Contact page. Choose separately whether to keep or erase the device/iCloud library as described in Section V. We may retain information where required for legal or regulatory reasons, such as tax records or resolving disputes, and will inform you if this applies. Section V explains the different storage and deletion lifecycles.

D. Restriction of Processing

Under certain circumstances, you have the right to restrict the ways in which your personal information is processed. This can include limiting the use of your data for specific purposes, such as marketing or analytics.

E. Right to Know About Data Sharing

You have the right to know if and how your data is shared with third parties. Detailed information regarding third-party sharing can be found in the Data Sharing and Disclosure section of this Privacy Policy. If you have any further questions or concerns about how your data is shared, you can contact us at any time.

F. Object to Processing

You may object to the processing of your personal information in specific circumstances, especially when the processing is related to direct marketing or advertising. In such cases, you can opt out of receiving marketing communications or object to automated profiling.

G. California Consumer Privacy Act (CCPA)

California residents may have the following rights under the California Consumer Privacy Act, as amended, where it applies:

  • Know and access: Request the categories and specific pieces of personal information collected, their sources, purposes, and categories of recipients.
  • Delete and correct: Request deletion or correction, subject to applicable exceptions.
  • Sale or advertising sharing: Opt out of sale or sharing for cross-context behavioral advertising. Avalogica does not sell personal information or share it for that advertising purpose.
  • Sensitive information: Limit uses and disclosures of sensitive personal information where the law provides that right. The personal analysis you request through Profiles and Reflection is described in Section II.
  • Non-discrimination: We will not discriminate against you for exercising applicable privacy rights.

Relevant information can include account identifiers, app activity, content you submit, and the profile inferences and supporting evidence described in Section II. Contact us using the process below; we do not require a special subject line or a separate account to submit a privacy request.

HOW TO EXERCISE YOUR RIGHTS

Email service@egocraftai.com or use our Contact page. Describe your request and provide enough context to locate the relevant information. A request may concern information about you submitted by another user, as well as information you supplied yourself. Please avoid unnecessary sensitive material or identification documents.

Where needed and permitted, we may request proportionate information to verify your identity or an authorized agent’s authority before disclosing or changing records. We use verification information for that purpose and to document our handling of the request.

We handle requests about information processed for EgoCraft even when it is stored with a service provider, and work with providers processing it on our behalf. Independent services you choose, such as destinations for exported copies, may have their own request processes. We will explain relevant boundaries rather than requiring you to contact every cloud provider yourself.

We will respond without undue delay and within applicable legal deadlines. Our usual aim is within 30 days, but a shorter applicable deadline takes precedence, including a calendar-month deadline where required. We will explain any permitted extension, applicable retention limit, or reason we cannot fulfill a request, together with available review or complaint options.

You can withdraw the feature permissions described in Section II.A through Settings ▸ Privacy & AI. Withdrawal affects future covered processing and does not undo earlier lawful processing or erase saved results; deletion is a separate request. Where applicable law provides a right to appeal our decision, contact us to request review.

FILING A COMPLAINT

Where applicable law provides a right to complain, you may contact the relevant data-protection authority or regulator. You may also contact us for help, but you do not have to contact us first before exercising that complaint right.

VIII. Security

Avalogica uses authentication, protected app storage, and the cloud-service protections described below to help safeguard personal information. These measures reduce risk but do not guarantee that information is completely secure.

A. Encryption and Service Protections

  1. In transit: Avalogica uses HTTPS for backend and AI-provider requests to help protect submitted material while it travels over the internet.
  2. At rest: Account and feature records in Google Firestore and Cloud Storage use the providers’ managed encryption at rest. Local records are stored within the app’s protected storage. Apple-hosted synchronization and backups are governed by the applicable Apple service protections. A local record can also have a cloud copy.
  3. Provider processing: Cloud AI features require selected content to be available to the processing service. Encryption in transit and at rest does not mean the content is end-to-end encrypted against the provider processing it.
  4. Authentication and selected context: Account sign-in uses Firebase Authentication and the applicable sign-in provider. Features select content and context for their operation as described in Section II; this can include personal material and analysis, not only account information and diagnostics.

B. Company Access to Content

Access by personnel acting for EgoCraft to private content is limited to what is necessary for support you request, security matters, or legal obligations, as described in Section IV. Access must remain limited to that purpose and the relevant information. This does not authorize routine reading of private journals, conversations, or memories. Authorized reviewers may handle material offered to Shared and related reports for moderation and safety. Support-mail handling is described separately in Section II.A.4.

C. Security Limitations and Incidents

No method of internet transmission or electronic storage is completely secure. If we become aware of a security incident affecting personal information, we will investigate and take appropriate steps to address it. We will provide notices required by applicable data-protection law.

D. Your Role in Security

Protect your device and sign-in credentials. Use strong passwords where passwords apply, and the additional account protections available from your sign-in and iCloud providers. Be cautious about phishing and avoid sending unnecessary sensitive material through general support email. Contact us through Contact if you have a security concern.

IX. Minimum Age Requirement

Avalogica is available only to people aged 18 or older. If you are under 18, you may not access or use Avalogica, even with permission from a parent or guardian. Any additional requirements imposed by applicable law also apply.

We do not knowingly permit use of Avalogica by people under 18. If we learn that an account belongs to someone under 18, we will restrict access and take appropriate steps to remove their personal information, subject to legal obligations. Please contact us through our Contact page if you believe someone is using Avalogica contrary to this age requirement.

X. International Data

Avalogica operates globally, and as such, the personal information we collect may be transferred to, stored, and processed in countries outside of your jurisdiction, including the United States, where our cloud service providers are located. These countries may have different data protection laws than the laws of your country.

A. Data Transfers: The services described in this policy can involve international storage and processing. Using the App is not blanket consent to international transfers where a separate lawful transfer mechanism or explicit consent is required.

B. Data Protection Safeguards: Where applicable law requires safeguards for a transfer, we will use an appropriate lawful transfer mechanism. This may include standard contractual clauses or another applicable mechanism. You can contact us for information about safeguards relevant to your information.

XI. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, services, or legal requirements. If we make any significant changes, we will notify you by posting an updated version of the policy on our app and website, and we may also notify you via email or through in-app notifications.

A. Policy Updates: We will post revisions and update the date. For material changes, we will provide appropriate notice and any choices required by law before the changed processing begins.

B. User Consent: If a change requires new consent, we will request it separately. Continuing to use the App does not substitute for that consent. The Terms of Use and feature-specific permissions remain distinct.

XII. Contact Information

If you have any questions, concerns, or requests regarding this Privacy Policy or the handling of your personal information, please do not hesitate to contact us. You can reach us through the Contact page on our website, where we provide an email link for submitting inquiries. We aim to respond to ordinary inquiries within 30 days; privacy requests follow the applicable deadlines described in Section VII. Your privacy is important to us, and we are committed to resolving any concerns or issues you may have.

Back to top