ASTRO HAVIANT · ANDROID
Privacy policy — Astro Haviant Android
2026-10-08 · 2026-10-08.1 · Build 32 (1.0.0-rc-play3)
Controller and scope
Astro Haviant for Android (previously called Astro Haviant Client) belongs to the Arukadia project, operated by Catanzaro Francesco. Privacy contact: account@arukadia.com. This page explains app-specific processing and supplements the Arukadia privacy notice for accounts, security, recipients and rights. The app contains no advertising, advertising SDK, Firebase or external analytics service.
Data on your device
Your profile, birth information, manually added people, journal, preferences, appointments and intentionally imported materials are stored in the app’s private area. Astrology calculations run locally. The journal is not synchronized or included in telemetry. The app does not read your contacts or request GPS location: birth locations and coordinates are entered or selected by you.
Notifications and widgets use local data. Camera access is only for QR decoding; camera images are not uploaded. Android’s document picker grants access to individual selected files, not general storage.
Optional account and synchronization
Local features and remote projection work without an account. Arukadia account registration uses email, display name, password and language under the account privacy notice. Synchronization requires your explicit choice. It can store profiles, birth data, people, appointments and consultation preparation on Aruba. The journal is excluded. Synced records are encrypted on the server and protected by account authentication; this is not end-to-end encryption.
In Build 32, “Add a file” saves PDFs, PNGs and JPEGs on the device and does not automatically upload them to Aruba. The service also supports private online material storage only when an upload is explicitly requested; enabling document synchronization does not import every file on the device. Limits are 2 MiB per file, 10 MiB total and 100 materials, plus 200 synced records including up to 50 people and one main profile. Audio and video are not recorded automatically. Recording an intention to share preparation does not itself send it: synchronized notes are not automatically made available to a practitioner.
Temporary remote projection
The Windows program sends only the shared client view over HTTPS. That view may contain names or birth information. Aruba stores one current frame and temporary session metadata, not a projection archive. Your device receives the view and click indicators. A session link or code works without login.
Online closure deletes the session. If the Windows publisher stops activity, access expires after approximately five minutes; cleanup runs on a subsequent request or the existing scheduled job. Active sessions keep renewing. Intentionally saved materials are separate from temporary projection.
Optional Arukadia telemetry
Telemetry remains off until enabled. It counts app openings, feature use, consultations/projections, notifications, widgets, generic errors and app version. It uses a random app-instance value, stored server-side as a keyed digest without linking it to an account record. It does not use an advertising ID or device fingerprint.
Metrics exclude names, emails, locations, astrology content, journal entries, questions, images, session credentials and detailed error messages. First open means first use with telemetry consent, not a Play download. Batched reports cover a 90-day window. Older rows are excluded from reports and removed by bounded daily maintenance triggered by API traffic. If traffic stops, physical deletion resumes on the next request; any backlog is cleared progressively.
Turning telemetry off immediately stops local collection and requests deletion of uploaded metrics. An offline deletion must be retried when connectivity returns; its private technical capability is retained until deletion is confirmed.
Retention, sharing and deletion
Local data remain until you erase them or remove app data. Uninstalling does not automatically delete an Arukadia account or synchronized records. Synced data remain until you delete them or account closure is processed. Erasing online app data does not close the shared Arukadia account and can preserve a local copy. Export and Android sharing require your action; the selected destination has its own terms.
Aruba hosts the service and database. Technical security logs and backups are covered by the Arukadia notice; deleting a live database row does not promise instant removal of backup copies. To request account closure and associated data deletion, use the Account deletion page or contact privacy support.
Community, invitations and benefits
When you activate your community profile, we associate a random invitation code, the first app activation and a random installation identifier with your verified account. The installation identifier is stored on the server as a keyed hash. These records support direct invitations, evident duplicate checks and Premium periods under the active campaign. No hardware identifiers, chart data or journal content are used for this feature.
The ledger records the source, date and expiry of benefits, valid invitation counts and invitation attribution. Community is separate from optional sync and usage statistics. These data remain linked to the account until account deletion; contact privacy support to manage them. The professional invitation link includes only a campaign source, without your personal code.
Purposes, legal bases, recipients and security
Accounts, synchronization and remote consultations provide the functions you choose to request (GDPR Article 6(1)(b)). Synchronization requires a separate explicit activation and is not needed for local calculations. Optional telemetry relies on consent (Article 6(1)(a)), which can be withdrawn in settings without losing local features. Community and invitation benefits provide the requested function (Article 6(1)(b)); proportionate fraud, duplicate and security controls rely on legitimate interests (Article 6(1)(f)). These data are not used for advertising or commercial profiling.
The controller and authorized persons access data necessary to operate the service. Aruba S.p.A. provides hosting, MySQL and email under the service agreements; authorized subprocessors and the recipient’s email provider may process data. The practitioner you choose sends the shared consultation view and manages their own data under their responsibilities: account synchronization does not automatically expose your archive to them. Android export or sharing sends a file only to your selected destination, under that destination’s terms. We do not sell data.
Application connections use HTTPS with certificate verification; Build 32 disallows cleartext HTTP. Passwords are securely hashed; online documents and materials are encrypted with a server-held key, with account isolation and security controls. This is not end-to-end encryption. Local data are in the app’s private area; automatic Android backup is disabled. We do not promise full local archive encryption or absolute security. The account WebView uses Arukadia’s technical session cookie and rejects third-party cookies.
No advertising SDK, Firebase, external analytics or AI service receives these data. Calculations, journal and personal numbers remain local; number preferences, salt and cache are not synchronized. The birth-time guide does not automatically upload certificates or official documents. Build 32 enables no purchases, advertising or commercial usage counters; existing referral campaigns are separate from these future features.
No application copies to non-EEA providers are configured. Provider infrastructure processing and any international transfers follow applicable agreements; user-chosen email providers or sharing destinations may operate outside the EEA. Contact the controller for information about applicable safeguards.
Account deletion and your rights
To request deletion of your account and associated data, open Profile → Settings → Account deletion in the app, or the public Astro Haviant / Arukadia account deletion page. No login or app reinstallation is required. Write to account@arukadia.com from the account email where possible; do not send passwords, codes or licence keys. Support may perform proportionate identity verification.
The request covers the shared Arukadia account, sessions and linked Android profiles, people, consultation preparation, online materials, community, referrals and benefits. Support processes deletion rather than merely suspending the account. Licences or records from other services require an individual review of strictly necessary retention for applicable obligations, security or legal claims; reasons and the relevant duration will be explained. A licence does not justify retaining the entire Android archive. Logs and backups follow the Arukadia notice’s criteria: simultaneous removal from every backup is not promised, and approved deletions must be reapplied after restoration.
Telemetry is independent from your account and cannot be located using email alone: you can disable and erase it in its dedicated setting before uninstalling. Offline deletion is retried when connectivity is available; otherwise the stated 90-day retention and bounded cleanup policy applies. Erasing online data or uninstalling does not automatically close your account; account deletion does not remove device copies or files already exported to others. Erase those through the app, Android settings or the recipient.
Where applicable you can request access, rectification, erasure, restriction and portability, and object to legitimate-interest processing. You can withdraw telemetry consent without affecting earlier processing. Requests are answered under GDPR Article 12, normally within one month; any justified extension is communicated within that time. You can complain to the Italian data protection authority or the competent authority. See also the Arukadia rights and contact notice. This version describes Build 32; new processing in future updates requires a notice update before activation.