Your information & your choices

Privacy Policy

Everlumen LLC · Effective October 23, 2026

Everlumen LLC operates Residency.Casa, a service for organizing residency and travel records. This policy covers its mobile apps, website and account services. For privacy questions or requests, email support@residency.casa.

Information we handle Recipients Retention & deletion Your choices

Information we handle and why

Account and profile: Email address, account identifiers, sign-in credentials or provider information, name, account role, home jurisdiction, residence dates, additional residences, preferences and organization/advisor relationships. We use these to operate your account, sign you in, configure records and manage access.
Location and travel: Precise coordinates, capture times, accuracy, location labels, manual history, notes, day-count settings and change history. These support your timeline, gap/conflict review, summaries, reminders and exports. When you enable automatic tracking, collection can occur periodically while the app is closed or not in use, subject to device permissions and availability.
Documents and photos: Files you choose to upload, including boarding passes, receipts or identity documents, and their descriptive information. Photo check-ins can include photo location/time metadata, a separate GPS reading and device model. These help organize and assess supporting evidence.
Device and technical signals: Where supported and available, motion-event counts, step-count changes and a hashed Wi-Fi access-point identifier support location-evidence assessment. The hash is not treated as anonymous. Device/app details, network addresses, request times and operational errors may be processed to deliver, secure and troubleshoot the service. Device authentication uses the operating system; Residency.Casa does not receive fingerprint or face templates.
Purchases and support: We process purchase history, subscription status, product and transaction identifiers, purchase and expiry times, renewal/cancellation/refund events, account and customer references, access-grant records and inquiries you send us. We use these to verify purchases, manage access, prevent purchase misuse, understand subscription activity and provide support. Where purchases are enabled, Android subscriptions use Google Play and iOS subscriptions use Apple's App Store, with RevenueCat supporting validation and subscription management. New purchases are unavailable in this web release. The store handles payment-card details; Residency.Casa does not receive your full card number. Do not send payment-card details to support.

We do not sell personal data, use advertising trackers, or share personal data for targeted advertising.

Hosting and operations: our Supabase-based backend runs on Hetzner infrastructure. Providers supporting hosting, email, security and recovery process information needed for those services. Authorized staff may access information needed to operate the service or resolve an issue.
Google sign-in: if selected, Google processes the sign-in request and shares information needed to authenticate you.
Optional AI extraction: AI scanning is unavailable in this web release; attaching proof without AI remains available. This web release does not send your files for AI extraction. Earlier supported releases may have sent images you selected for extraction through our server to Google's Gemini API. Those images can contain passenger names, itineraries and booking references. Google's applicable Gemini API terms describe provider processing. Disabling the feature does not erase information already held by a provider.
Purchase providers: Google Play or Apple processes purchases made through its store. RevenueCat receives store purchase records (such as receipts or purchase tokens), subscription events and your signed-in Residency.Casa account identifier. This information is linked to your account and is not anonymous. RevenueCat also processes technical information such as device/operating-system details, locale, currency and recent app-use time to support its services. We use its validation, customer-history and subscription reporting features for access management, support and purchase analytics. Apple or Google can send subscription events to RevenueCat, which shares purchase status and account references with our backend. Our billing integration does not send GPS readings or uploaded documents to RevenueCat. See Apple's privacy information and RevenueCat's data-handling information. Stripe may retain customer or purchase information from earlier supported testing. The website does not start new checkout sessions. Disabling a purchase feature does not erase information already held by a provider.
Maps and device services: employer maps request OpenStreetMap tiles, exposing network/request information and the requested map area to the tile service. Device location and address-lookup services may process coordinates to provide readings and labels.
Advisors, employers and chosen recipients: account relationships and sharing can make relevant records available to an advisor or organization. Employer features can expose employee location and business-travel information to the linked employer. Revoking app access does not recall previously downloaded or exported copies.
Legal obligations: information may be disclosed as necessary to comply with law or lawful requests or to protect rights and service security.

Providers may process information outside your country. Their terms and safeguards apply to their processing. The processing described in this notice supports service delivery, recordkeeping, access management, security and support.

Storage and security

The service uses HTTPS and account access controls. Optional document encryption requires setup and retaining your recovery phrase. It applies to eligible new uploads after setup; it does not automatically encrypt every existing file, GPS record or account field. Sharing or AI extraction can expose selected content to the recipient. No system guarantees absolute security or recovery.

Your device can hold sign-in state, preferences, queued GPS readings, encryption keys and downloaded/exported files. Browser storage supports the web session and app preferences. Protect your recovery phrase and retain independent copies of important records; device backup or transfer alone may not preserve encrypted-document access.

Retention and deletion

We retain account and evidence records while your account is active to provide its history and services. Routine corrections may preserve original observations and change history. Revising or hiding an item differs from requesting erasure.

You can request account deletion from Account → Delete Account in the current Android app, or use the email route in our deletion instructions. You can also request removal of specific information by email while keeping your account. Older app versions may direct you to support. A saved request reference confirms receipt, not that every copy has already been erased. The process includes associated account, location, document and sharing data. Eligible primary account and stored-file removal is processed automatically; support handles cases needing review and remaining provider, backup and device steps. Support provides the expected timing for your case, explains retention exceptions, and notifies you of the result. If that timing changes, support provides an updated status.

Backup copies and records held by service providers require separate handling. We have not yet verified a maximum retention period covering every backup or a uniform provider-deletion completion time. We do not describe deletion from the live account as proof that those copies are gone. Contact support for the status and applicable timeframes for your request.

The email deletion route is available from any platform, including iOS, whether or not an in-app request control is available in your version.

Limited transaction, security or request-handling records may remain where needed for a legal obligation, fraud prevention or proof that a request was fulfilled. Any exception must be limited to necessary data and duration, with restricted access; we explain applicable retention unless legally prohibited. Backup handling does not determine independently required app-store transaction records or copies held by recipients outside our control.

Your choices

Use manual history without automatic tracking. Stop tracking or change device permissions; this does not itself erase past records.
Choose which files to upload. This web release offers proof upload without AI; exclude unrelated sensitive information.
Review advisor access and organization relationships. Ask support for help ending access or understanding what was shared.
Use exports or contact support for access, correction, a copy or deletion. Depending on your location, you may also have rights to object, restrict processing or complain to a privacy authority.

We may verify ownership using only reasonably necessary information. Never email a password, recovery phrase, full identity document or travel archive to prove ownership.

Changes and contact

We update the policy date when it changes and give additional notice where required. Residency.Casa is intended only for adults aged 18 and over. Contact support@residency.casa about privacy concerns or information submitted by someone under 18.