Contents
Effective 13 November 2026. Operator: Always Late Technologies. Contact: privacy@alwayslatetechnologies.com. The product is Show My Revenue.
What we process
We operate revenue listings, a leaderboard, badges and revenue milestones. We process the connection and account data needed to provide the service you request, and limited security data to protect it. Public listing data can identify a person, including a sole trader. We do not sell personal data, profile customers, run advertising analytics or send marketing messages.
| Data | Use and visibility | Retention and deletion |
|---|---|---|
| Mollie token encrypted with an authentication tag and key version | Private server-only access for daily refreshes. Encryption keys stay outside the database. Only the refresh job decrypts saved merchant tokens; no screen or endpoint returns one. | Until replacement, disconnect, listing deletion, or the first refresh that detects expiry/revocation or unsafe permissions. That event deletes the active ciphertext and stops refreshes. Revoking a token in Mollie is not detected instantly. |
| Listing name, description, optional logo, founder’s X handle and website, Mollie profile ID, stable URL, creation time, connection status and aggregate EUR figures | Published listing, leaderboard and badge, including the selected profile’s scope, comparison windows and last complete refresh. Logos are resized PNGs stored with the listing. No customer or payment-level records are stored. | Until verified listing deletion. Owners can remove their optional logo, handle and website at any time. Disconnect or rejected credentials retain the last complete figures with a visible warning. Successful imports replace aggregate totals. |
| Revenue milestone amounts and the date each was first recorded | Public listing and its milestone share pages/images. A later refund does not remove a reached milestone. | Until listing deletion. No milestone emails, notifications or additional tracking. |
| Raw provider responses and reduced payment/refund/chargeback records | Transient server-memory processing only. Customer fields returned by Mollie are discarded at the adapter boundary. | Never written to durable storage, logs, telemetry or job payloads. Discard after processing or a failed request. |
| Unfinished aggregates and encrypted pagination cursor | Private first-import progress. The cursor can contain transaction identifiers solely to continue pagination; no individual transaction record is saved. The token is not stored with unfinished progress. | Delete on completion, cancellation, replacement, disconnect, listing deletion or emergency purge. Unfinished progress expires 24 hours after its original start; retries do not extend it. Expired rows are physically removed on the next public-listing, import or daily-refresh cleanup operation. Account-only operations do not trigger that cleanup. Closing the page pauses it; a valid token for the same profile is required to resume. |
| Optional sign-in email, Google identity/profile metadata, Supabase user ID, session records and listing ownership link | Private authentication and account management. Sign-in alone cannot claim a listing. We request Google sign-in identity access, not access to your Gmail or files. Your sign-in email is not added to the public listing. | Account and ownership metadata remain until account deletion. Deleting an account clears its convenience ownership link; it does not delete a public listing automatically. Request either or both by email. Session cookies are HttpOnly and last up to 30 days, renewed during continued use; sign-out ends that local session. Email codes expire after one hour and are single-use. |
| Keyed network identifiers and rate counters | Private abuse prevention; no plain IP history is kept by application code. | Counters expire after 15 minutes and are physically cleaned by the next connection/import cleanup operation, including daily refresh. Hosting providers separately process technical request metadata. |
| Hosting request/security logs | Paths, status, time and provider technical metadata. Application code does not log tokens, authentication codes, request bodies or payment/customer records. | Vercel’s current Pro runtime-log retention is one day. Supabase Free API/database log retention is one day; this project has database copies of authentication audit logs disabled. Supabase still processes authentication/security events in its provider logs. An account deletion request includes review of relevant provider-controlled records. No external log drain or application analytics is configured. |
| Sign-in emails and delivery metadata | Resend delivers Supabase email codes from our company sending subdomain. It processes the recipient, code email and delivery status. Open/click tracking is off. | Resend retains email data for 30 days under its current plan. A sign-in code expires after one hour even while its delivered email remains. No marketing mail is sent. |
| Internal deletion markers | Connection IDs for recovery safety, with no customer/payment records. | Expire 30 days after deletion; physically removed by the next connection/import cleanup operation, including daily refresh. On restoring a database, purge restored credentials/progress before refreshing or accepting connections again. |
| Deletion-request correspondence and verification notes | Private operator inbox on Migadu. Ask only for proportionate proof, not credentials or transaction data. | Delete 30 days after the request closes, unless a legal duty or active dispute requires a longer period, which we explain. |
Tokens and publication
Submit a Mollie token only through the HTTPS form. It travels in a POST body, never a URL, query string, browser storage, analytics event or error report. It stays masked in the open form while permissions/profile selection and import requests run, then clears on completion, cancellation or error. We accept only payments.read, refunds.read and profiles.read and reject extra permissions. No partial figures are published. Submitting a listing makes its aggregate totals public.
Delete a listing without a token
Email privacy@alwayslatetechnologies.com with its listing URL and your relationship to the business. A valid token is not required to request deletion. Do not email a token, password, sign-in code, customer records, bank details or identity-document copy.
Thomas verifies control proportionately. An email address or knowledge of public figures alone is insufficient. A signed-in Mollie dashboard showing the matching profile ID can establish control; sign in yourself and hide credentials/customer data. Screenshots alone are insufficient. If you cannot access the dashboard, explain this so alternative evidence can be agreed. We do not retain dashboard recordings.
We respond within one calendar month, explaining any lawful extension or refusal. Verified listing deletion removes its active token, progress, aggregate totals, milestones and URL aliases and stops refreshes. You separately revoke the token in Mollie. Public copies, screenshots and search caches may remain outside our control. Listings and share images are publicly accessible without signing in.
Providers, transfers and backups
We use Vercel for hosting; Supabase for the Frankfurt database and authentication; Mollie as the source of figures; Google for optional sign-in; Resend for sign-in email delivery (Ireland sending region); and Migadu for privacy correspondence. These providers receive only data necessary for their roles; Mollie must receive the token to answer read requests. The database schema holding ciphertext/progress is excluded from Supabase’s public API, uses row-level security, and has no client grants.
The database and application runtime are configured for Frankfurt. Build systems, support, email and provider infrastructure may process data elsewhere; we do not claim all processing stays in the EU. Provider safeguards and international-transfer terms apply. No application-managed backup exports are created, and this Free Supabase project currently exposes no retained backups. This does not promise that infrastructure providers have no disaster-recovery copies. Provider-controlled copies follow their contractual retention; active deletion does not promise immediate deletion from every underlying recovery system.
Your rights
Where applicable, request access, correction, deletion, restriction, portability or objection at the contact address above. Service processing is necessary to provide the service you request; proportionate abuse prevention relies on legitimate interests. You may complain to your data-protection authority. We do not make automated decisions with legal or similarly significant effects. Any legal retention exception is explained with its purpose and period.
Changes
Material changes to collection, visibility or retention will be explained before they take effect. Checkout, marketing, marketplace transactions and additional payment providers are not part of this service.