AC Utveckling · Amoré

Amoré — Tarot for Love · Current development builds

Privacy Policy

Effective date:

This policy explains how the current development builds of Amoré — Tarot for Love (Android package com.actuveckling.amore) handle information. It applies to the Android app, the web version, and support correspondence about the app, and describes the implemented features as of the effective date.

Privacy at a glance: Card selection and your reading journal use local app logic and storage. You do not need an account. The current app has no advertising, analytics service, in-app purchases, or journal cloud sync. The web version loads external fonts and uses a hosting provider, which receive technical request information.

1. Who we are

Amoré — Tarot for Love is operated by AC Utveckling (AC mobiltillbehör HB), based in Sweden.

For privacy questions, contact claeseriksson@acutveckling.com.

2. Information stored on your device

When you draw another card, Amoré stores a journal entry in your browser's or Android WebView's local storage under amore:journal. Each entry contains:

The journal retains up to 50 entries to show recent readings and reading counts. Older entries are replaced as you make new draws. The app has no feature that uploads or synchronizes this journal with an account or server.

The daily card uses the device's calendar date. Other draws are selected locally, and card artwork and meanings are included in the app. The app does not ask you to type your personal question, name, birth date, email address, or relationship details.

The current app does not save separate user settings or profiles. It respects the reduced-motion preference supplied by your device or browser. Browsers and Android WebView may also keep ordinary resource caches used to display the app.

3. Network requests and external providers

The web version's hosting provider serves pages and resources to your browser. This involves technical request data such as your IP address, requested page, and browser information. Hosting systems may retain technical request and error logs to operate and diagnose the service. Journal entries are stored on your device and are not included in an app upload.

The web implementation loads Libre Baskerville and IBM Plex Sans through Google Fonts at fonts.googleapis.com and fonts.gstatic.com. Loading these resources sends Google technical request information, including your IP address and browser request details. See Google's privacy policy for its handling of this information.

The Android build uses bundled web assets and includes Android's internet permission. Its card-selection and journal functions do not require a server. External resource requests can still involve the providers described above.

The current app has no login, advertising SDK, analytics service, payment or subscription integration, or developer-operated cloud synchronization. It does not request Android permissions for location, camera, microphone, or contacts.

4. Error reporting and security

Development-preview code checks for error-reporting hooks supplied by the Lovable editor. When those hooks are present, it can pass an error message, stack trace, and route information to the preview's reporting system. The standalone Android build does not configure that editor-preview service. The web server also logs technical errors to diagnose page-loading failures.

Journal storage is protected by the browser's site-storage controls or Android's app storage controls. The app does not add a separate password or encryption system for the journal. Access also depends on your device and user-account security.

Automatic Android app-data backup is disabled in the current manifest. The app provides no cloud backup of your journal. Copies made through external tools or device transfers are managed separately by those tools or providers.

5. Retention and deletion

The journal remains locally until entries are replaced by the 50-entry limit or you remove the app's storage. There is no separate in-app journal deletion control in the current build.

In the web version, clear site data for the Amoré website in your browser's privacy or site settings to delete the journal. Removing browsing history alone may leave site storage intact.

On Android, use Android Settings → Apps → Amoré → Storage → Clear storage, or uninstall the app, to remove its local journal and app data. Clearing cache alone does not erase the journal.

Clear or delete any copies you made through external tools separately. Provider-side technical records are retained under the relevant provider's policies and operational requirements; deleting local app storage does not delete those records.

6. Contact correspondence

If you contact us by email, we receive your email address and the message or attachments you choose to send. We use them to answer your request and resolve support issues, based on our legitimate interest in providing support. Email providers process correspondence to deliver and store it.

We retain correspondence only as long as needed to handle the request, relevant follow-up, or legal obligations. Please avoid sending information that is unnecessary for your support request. You can contact us to ask about or request deletion of your correspondence.

7. Your rights

Where applicable under GDPR, you may request access, correction, deletion, restriction, or data portability, and object to processing of your personal information. Contact claeseriksson@acutveckling.com to exercise your rights. We cannot remotely access or delete a journal stored only on your device; you can remove it using the steps above.

Read more about your data protection rights. You may also lodge a complaint with Integritetsskyddsmyndigheten (IMY), the Swedish Authority for Privacy Protection.

8. Policy changes

We will update this page and its effective date if the app's features or data practices change, including before adding features that collect or transmit journal information. This policy describes the current development builds; future releases may have an updated policy.