Privacy

Optional browser account helper

If you install and pair the Chrome Account Helper, it derives billing facts from visible provider pages you enable. Captures stay in that Chrome profile, are unavailable after seven days and are removed on the next local-state read. Your paired dashboard can preview them; only subscription fields you explicitly review and save enter your account storage. No provider passwords, cookies, card details, invoices or page copies are collected. Disable a provider or disconnect the helper to clear captures and permissions. Read the helper access, storage and installation details before enabling it.

Who is responsible

The data controller is Χρήστος Φραγκούλης (Christos Fragoulis), acting as a natural person, based in Corfu, Greece (49100). Privacy contact: cfragoulis@rawlogic.gr.

[REVIEW REQUIRED: a full postal contact address and applicable jurisdiction.] Corfu and its postcode alone are not a deliverable postal address.

For account deletion, access to your data or other privacy questions, see support and data requests. The confirmed controller and contact details do not mean this draft notice has completed legal review.

What the beta handles

• Account information managed through Supabase authentication, including your email address, account identifier and authentication/session data.
• Subscription details you enter or approve, such as service, amount, currency, billing cycle, recorded renewal date, category and status. Renulio does not connect to your bank.
• Review settings you supply: cancellation deadline or notice period, whether a deadline is user-confirmed or calculated, an optional provider URL, source, last-check time and per-subscription reminder preferences.
• Your recorded decisions, notes, planned amounts, follow-up dates and confirmed outcomes. History preserves snapshots of the service, price, currency, renewal date and deadline context as they were recorded.
• Selected structured rows from a CSV import. The file preview is read on your device; rows you select and confirm are sent to your account. Private request records also retain structured action/import payloads to prevent duplicate submissions.
• Practice subscriptions, decisions and imports held in page memory, which reset on reload or Reset demo. For signed-in accounts, saved or dismissed rule-based suggestion preferences are stored locally in that browser. Decision Inbox history is stored with your account, not just in the browser.
• Reminder preferences: your opt-in, timezone, selected intervals and processing/failure records. When sending is enabled and you opt in, Resend receives your email address and the prepared reminder containing the service name, recorded amount and relevant dates. Private notes are excluded. Automatic email reminders are available after you opt in from Account. Choose your timezone and reminder preferences there. Delivery can be delayed or fail; keep your own calendar alerts for important deadlines.
• Technical request and security information handled by the hosting and authentication services. Exact log and backup retention requires operator confirmation.

Why the information is used

Renulio uses account and subscription data to authenticate you and display, save, update and export your records. Review settings place renewals and follow-ups in your inbox. Decision and outcome history lets you see what you chose previously; request records prevent the same submission from creating duplicate actions. These records do not independently verify provider terms, usage or payment outcomes.

Optional Gmail processing runs at your request; the separately consented continuous pilot can search, save supported records and update them automatically. An optional Google Play connection can import and update supported subscriptions for eligible pilot accounts after you authorize it; its separate notice explains the data and controls. Reminder preferences control optional decision emails when the service is operational. You can opt out from Account; a message already handed to the email provider cannot be recalled.

[REVIEW REQUIRED: confirm the lawful basis for each purpose, any legitimate-interest assessment, and the conditions for withdrawing optional consent.] Optional Google access can be removed from your Google Account.

Services involved

• Supabase: authentication and account-linked database storage.
• Vercel: application hosting and request processing.
• Google: only if you choose an available Gmail scan or authorize an eligible Google Play connection. Read the detailed Gmail notice and the Google Play connection notice for their separate data handling and controls.
• Resend: delivers optional renewal reminders when you opt in. If custom SMTP is enabled, it also delivers account verification and password recovery messages; those are needed for account access regardless of reminder preferences.

No Stripe checkout or OpenAI API integration is present in this version. Gmail message bodies are not sent to an AI service. [REVIEW REQUIRED: confirm processor agreements, deployment regions, international transfers and any applicable safeguards.]

Browser storage and Gmail

Your chosen interface language is stored in the functional renulio-language cookie for up to one year. It contains only en or el, applies to this browser and is not used for advertising or tracking. You can change the language at any time or remove the cookie in your browser settings.

Authentication uses session cookies. The demo keeps its subscriptions, decisions and imports in page memory. Signed-in saved/dismissed suggestion preferences use local storage, separately for each account. Clearing that storage does not remove account-linked review settings or decision history. CSV previews are held in page memory; only selected structured rows are submitted for import.

Gmail OAuth state and temporary suggestions use short-lived cookies. The Gmail notice describes their exact lifetime and controls. Gmail message bodies are processed during a requested scan and discarded. For the existing one-time scan, Google tokens are not persisted. The separately consented continuous pilot retains encrypted server-side refresh access and minimal derived evidence, as explained in the Gmail notice. The application requests token revocation after processing, but cannot guarantee that Google confirms it; the flow provides a Google Account access-removal link when needed.

Retention and deletion

Saved subscription records remain in your ledger until you delete them. Decision and outcome history is append-only in the app: later choices add records rather than overwrite earlier ones. Deleting a subscription retains its private historical snapshots, including the recorded name, amounts and notes, until account deletion. Private action/import request records are also retained for duplicate prevention. None of these actions cancels a service with its provider.

To request account deletion or correction of historical personal data, email cfragoulis@rawlogic.gr, preferably from your account email. There is no self-service account deletion button. Requests require manual handling and account-ownership verification; sending a request does not itself delete data. The account-deletion procedure still needs operational verification before general release.

[REVIEW REQUIRED: set account, decision-history, action/import-request, request-log, reminder-delivery and backup retention periods; confirm the correction/deletion procedure and how deletion propagates to processors and backups.] Do not treat deleting browser storage as deleting server records.

Your access and choices

When signed in, open Account to download the available JSON export, including subscription records, review settings and decision/outcome history. You can correct or delete individual subscriptions in the ledger; their retained history is described above. For a wider access request, historical-data correction or help with export, email cfragoulis@rawlogic.gr and identify your account. Follow the data-request instructions for account deletion and other support.

Depending on applicable law, you may have rights to access, correct, erase, restrict or object to processing, receive portable data and complain to a supervisory authority. [REVIEW REQUIRED: confirm applicable rights, authority, identity-check process and response procedure.]