Privacy Policy

1. Data Controller

The data controller responsible for personal data collected via Ricly is:

Ricly — a commercial name (nom commercial) of Samir Benabdelmoumen, auto-entrepreneur (entreprise individuelle) registered in France (SIRET 889 343 687 00022).
Email: hello@usericly.com (prefix subject with [Privacy] for privacy-related requests).

Given the scale of our operations (under 250 employees, no large-scale special-category processing), we are not required to appoint a formal Data Protection Officer (DPO) under GDPR Article 37. Privacy-related requests are handled directly by the data controller.

2. Data We Collect

We collect only the data needed to provide the Service. Categories:

2.1 Account data

• Email address — provided by you at sign-up (Firebase Authentication).
• Optional name — if provided in settings.
• Authentication token — managed by Firebase, never stored by us in plain text.
• Billing email — captured separately by Stripe at checkout if it differs from your sign-up email (Stripe Link users typically have this scenario). Stored as billing_email ; never used for transactional emails which always go to your sign-up email.

2.2 Subscription & billing data

• Subscription status — Free / Pro / Founding Monthly / Founding Lifetime / Family.
• Stripe customer ID — opaque identifier for billing reconciliation.
• Payment method — handled entirely by Stripe ; we never see or store card details.
• Invoice history — accessible to you via the Stripe Customer Portal.

2.3 Usage & analytics data

• Module opens — which Ricly modules you launch, linked to your account to measure feature usage and unique reach. Governed by the “Help improve Ricly” switch in Settings (on by default) — turning it off stops all product-usage analytics.
• Your “Help improve Ricly” choice — whether the switch is on or off, and the date we learned it, linked to your account. When the switch is off, the analytics above stop, and the app sends this choice instead.
• Upload counts & bytes — number of files uploaded via Upload & Share and total storage used. Not the file content.
• Last seen timestamp — to identify dormant accounts for re-engagement emails (opt-out available).
• App version & macOS version — to diagnose crashes and ensure compatibility.
• Anonymized error reports — when the app crashes, we may receive a stack trace via Apple MetricKit ; no personal data is included.

2.3 bis Download count and setup steps

• Download count — when you click Download on usericly.com, we count the click with the date, your country (derived from your IP address by Cloudflare), whether you use a Mac, and where the click came from (see Section 5). To count each person once a day, we keep a code computed from your IP address and browser with a secret key, which changes every day; your IP address itself is not stored.
• Setup steps — the app reports a few setup steps (first launch, Finder extension turned on, first successful try, sign-up screen shown, account created) with a random installation ID created on your Mac, and your country. They follow the “Help improve Ricly” switch: turning it off stops them.
• Which channels work — we estimate, by country and by hour, how many downloads are followed by a first launch of the app within 48 hours. This uses no IP address and no device identifier: only the country and the time of the download and of the first launch.

2.4 Files (Upload & Share only)

• Files you upload via the Upload & Share feature are stored encrypted at rest on Cloudflare R2.
• File metadata stored: file name, size, MIME type, upload timestamp, expiry date, download count.
• File content is NEVER analyzed, indexed, or shared with any third party (other than the link recipients you choose).
• Files expire and are permanently deleted per your plan: 3 days (Free), 30 days (Pro and Founding).

2.4 bis People who receive a shared link

• If someone shares a file with you through Upload & Share, you can download it in your browser, without an account.
• Each time the download page is shown, and if you click “Get Ricly for Mac” on it, our server records which version of the page was shown, the shared link, the time, whether your device is a Mac (read from your browser’s user agent), and a pseudonymous code. The code is calculated from your IP address, your browser’s user agent and the date, with a secret key. It changes every day, and we do not store your IP address with these records. We use it to count visits without counting a page reload twice.
• Downloads are counted as a number per link. The person who shared the file sees that number and gets one email the first time the file is downloaded. They never see who you are.
• The download page sets no cookie.
• After 90 days, we erase the pseudonymous code from these records. Only anonymous counts remain.

2.4 ter People who report a shared link, or send a counter-notice

• If you report a shared link with our report form (or by email), we keep what you send: the link, the reason you chose, your explanation, any evidence link, and your name and email address (both optional only for a report of child sexual abuse). For a copyright report, we also keep the work concerned, whether you own it or act for the owner, the owner’s name, your postal address, country and phone number, your statements and your typed signature.
• We use this to review the report, contact you, and keep a record of what we did. For a copyright report, the person who shared the link receives the copyright owner’s name, your name, your description of the work and your explanation, never your email address, postal address or phone number. For any other report, we never tell them who reported it.
• If you send a counter-notice, we keep your name, email address, postal address, country, phone number, explanation, statements and signature, and we forward them to the person who reported the link, as copyright law requires.
• The form sets no cookie and stores no IP address. To limit abuse, our server counts recent submissions per IP address in memory only, for a few minutes.

2.5 Network & device data

• IP address — used for abuse prevention, rate limiting, and approximate country detection. Provided by Cloudflare network edge.
• Country code (ISO-2) — derived from your IP. Used for locale-appropriate pricing display (EUR vs USD) and analytics.
• Device identifier — a unique ID per Mac, used to enforce the number of Macs allowed on your plan and to check that requests come from your Mac, and the name of your Mac as set in System Settings, shown back to you in Settings so you can tell your Macs apart.

2.6 AI input data (cloud AI modules only, on demand)

• When you use a cloud AI module, the input file (image, audio, document) is sent to the relevant AI provider for processing. No plan on sale today includes a cloud AI module.
• We do NOT retain a copy of the AI input data beyond the processing window. The AI provider’s retention policy applies separately (see Section 6.4).

2.7 Reviews (only if you choose to write one)

• Writing a review is entirely optional. Only Ricly account holders can write one: either after rating Ricly 9 or 10 in our satisfaction survey, or on our review page, where you give the email address of your Ricly account and then confirm your review with a link we send to that address.
• Confirmation — until you click the confirmation link, your review is kept aside and nobody at Ricly reads it. An unconfirmed review is deleted after 7 days, photo included. If the email address you give does not belong to a Ricly account, your review is discarded straight away: we keep nothing and send nothing. To prevent abuse, we keep a scrambled (hashed) form of the email address for 24 hours.
• What we collect — your first and last name and how you want it shown (full name, or first name and last initial), your job title, your rating (1 to 5), your review text, and, only if you add them, a photo and a link to a public LinkedIn, Instagram or X profile. The review is linked to your account and email address ; your email address is never published.
• Photos — before storing a photo, we remove the location, camera and other data embedded in the file. Photos are stored privately and have no public address.
• Consent — we record the exact consent text you agreed to and the time you agreed.
• Early testers — if you tried Ricly before its public launch, we may note it next to your review.
• Publication — nothing is published automatically: we read every review first. With your consent, an approved review may appear on usericly.com and on Ricly’s social accounts, with your name as you chose, your job title, your rating, your photo and, if you added one, the link to your profile, marked “Verified Ricly user”. Our website is in English: if you wrote in another language, we show our English translation, labeled as translated. Your email address is never shown.

2.8 Satisfaction survey

• If you answer our satisfaction survey, we store your score (0 to 10), linked to your account.
• If your score is 0 to 8, we ask one optional question about what would make Ricly better for you. Your answer is linked to your account, read only by the Ricly team, and never published. We may reply to it by email.

2.9 “Send it to my Mac” (only if you ask for the download link by email)

• What we keep — your email address, the page you asked from (so our check-in can mention that tool), your country and time zone (to email you around 10 am your time), whether you used the download link, and which of our emails you received. We never attach the site you came from or any campaign tag to this record.
• Emails — the download link right away, then one short check-in the next day. Nothing more, unless you tap “Yes, send me the deal” on the confirmation screen.
• The founder deal (only if you tap yes) — one email with a personal offer, one last email on the day it ends, and after that only big Ricly news, rarely. We record when you agreed and which version of this policy you saw.
• Deletion — without that consent, we delete your address right after the check-in is sent (at the latest 48 hours after it was due). With it, we keep your address until you unsubscribe, or for 3 years after our last email to you. If you create a Ricly account or buy Ricly with this address, we remove it from this list: your account then follows the rest of this policy.
• Unsubscribe — one click in any of these emails stops everything and deletes your address on the spot. We keep only a hash of it (not the address itself), so we never email you again.
• Earlier requests — requests made with the earlier version of this form get the download link and a single reminder, as promised at the time.

2.9 What we do NOT collect

• The content of files processed locally (conversions, compression, OCR, etc.). These run 100% on your Mac.
• Your browsing history, location history, or any third-party app data.
• Sensitive personal data under GDPR Art. 9 (health, beliefs, biometrics) — we do not request or process this.
• Card payment details (handled by Stripe ; we are out of PCI scope).

3. Why We Process Your Data (Purposes)

• Service delivery. Authenticate you, enforce subscription tier, route uploads.
• Billing. Process payments, send invoices, manage subscriptions.
• Customer support. Respond to your emails and bug reports.
• Product improvement. Aggregate anonymized usage stats to decide which modules to improve.
• Security & fraud prevention. Rate-limit abusive IPs, detect anomalies, prevent fraudulent chargebacks.
• Reviews. With your consent, show what users say about Ricly on our website and social accounts.
• Reports and legal notices. Review reports about shared links, act on them, and keep a record (Section 2.4 ter).
• Communication. Send transactional emails (welcome, payment receipts, dunning) and, if you opted in, occasional product updates and marketing.
• Legal compliance. Retain billing records as required by French fiscal law.

4. Legal Basis for Processing (GDPR Art. 6)

• Contract performance (Art. 6.1.b) — account, billing, support, file delivery, Upload & Share, AI features.
• Legal obligation (Art. 6.1.c) — accounting/fiscal retention, response to legal authorities, handling reports and counter-notices about content we host (EU Digital Services Act, copyright law).
• Legitimate interest (Art. 6.1.f) — abuse prevention, security, anonymous analytics, short-term IP retention, satisfaction survey answers.
• Consent (Art. 6.1.a) — marketing emails, optional analytics, reviews you send us for publication. Withdrawable at any time via Settings → Email notifications or by emailing us.

5. Cookies & Tracking

The Ricly macOS application does NOT use cookies. It sends a per-device identifier and your Mac’s name to our server, to apply your plan’s device limit and to list your Macs in Settings, and a random installation ID for the setup steps described in Section 2.3 bis.

The website usericly.com uses only strictly necessary cookies (session, language preference, dismissed banners). We do not currently use third-party analytics cookies, advertising cookies, or social media trackers on the website. If we add any in the future, we will display a GDPR-compliant consent banner before any non-essential cookie is set. We do use one cookieless analytics service, described below.

Since 21 September 2026, usericly.com uses Umami for anonymous website analytics, on servers located in the European Union. Umami sets no cookies and writes nothing to your browser storage: visits are counted using an anonymized server-side hash that rotates, so you are not recognized from one visit to the next, nor across other websites. It records the page you opened, the site you came from, campaign parameters present in the address (utm_*), your country, browser and device type, and a few anonymous clicks on this site: opening or sending the “Send it to my Mac” form, and clicking Download. It records nothing you type, and builds no profile. This is why you see no consent banner here: there is no non-essential cookie to consent to.

When you arrive from another website, the page keeps that site’s name and any campaign tags (utm_*) in your browser’s session storage — deleted when you close the tab — and adds them to the anonymous download count. Never the full address, never anything personal.

6. Third-Party Subprocessors

We use the following services to operate Ricly. Each is a data subprocessor under GDPR Art. 28 and processes data only under our written instructions (Data Processing Agreement, DPA, signed where applicable).

6.1 Authentication & database

• Firebase Authentication (Google LLC, USA) — manages user sign-up, email verification, and login sessions. Data: email, password hash (we never see plain text), authentication metadata. Under EU Standard Contractual Clauses (SCC) for international transfers.
• Firebase Firestore (Google LLC, USA) — stores your account state (plan, settings, Founding Member status). Under EU SCC.
• Cloudflare D1 + Workers (Cloudflare, Inc., USA) — application backend database and edge compute. Hosted in the EU (Frankfurt and Paris regions) where possible. Under EU SCC.

6.2 Payments

• Stripe Payments Europe Ltd (Ireland) — handles all payment processing, tax collection (Stripe Tax), and billing portal. We never receive card data. Stripe’s privacy policy: stripe.com/privacy.

6.3 File storage & CDN

• Cloudflare R2 (Cloudflare, Inc., USA) — Upload & Share file storage, and photos attached to reviews (private). Files encrypted at rest. Under EU SCC.

6.4 AI providers (cloud AI modules only, on demand)

None of these is used today: Ricly’s AI tools (Remove Background, Upscale Image, Extract Text) run on your Mac. These providers would only apply to cloud AI features, which are not available today; we’ll update this list before any of them ships.

• fal.ai (USA) — AI image upscaling and generation. Under EU SCC.
• PhotoRoom (France) — background removal AI. EU-based.
• PiAPI (Singapore) — selected generative AI features. Under EU SCC.

AI providers are invoked ONLY when you actively use an AI-powered module. Each request sends the necessary input (e.g., the image to upscale) and receives the AI output. We do not pre-emptively send your data to AI providers.

6.5 Email delivery

• Resend (Resend, Inc., USA) — sends transactional and lifecycle emails (welcome, dunning, receipts, opt-in updates) and internal notifications to our team, such as a new review to read. Stores email addresses and send logs. Under EU SCC. Links in our emails carry a short code naming the email, never you. When you click one, our server adds one to a daily count for that email and sends you on to the page; it keeps no IP address and no email address, so a click is never linked to a person. We do not track whether you open an email.

6.6 Auto-updates

• Sparkle Updater (open source, served from our own infrastructure) — checks for app updates by fetching an XML feed from releases.usericly.com (hosted on Cloudflare R2). No personal data is sent ; only the request itself (which includes your IP via standard HTTP). User-Agent includes app version for compatibility checks.

6.7 Website analytics

• Umami (Umami Software, Inc., EU hosting region) — anonymous website analytics for usericly.com. No cookies, no browser storage, no cross-site tracking, no profiling. Data: page visited, referring site, campaign parameters (utm_*), country, browser and device type, and a few anonymous clicks (opening or sending the “Send it to my Mac” form, clicking Download). Used only to know which launch channel brought visitors, and where they stop.

6.8 No advertising, no data sales

We do NOT use advertising platforms, marketing analytics platforms (e.g., Mixpanel, Amplitude, Segment), or social media trackers. We do NOT sell, rent, or share your personal data with any third party for marketing purposes.

7. International Data Transfers

Several of our subprocessors are based outside the European Economic Area (EEA), notably in the United States. For each such transfer, we rely on:

• EU Standard Contractual Clauses (SCC, Commission Decision 2021/914) — signed with each US subprocessor.
• Where applicable, EU-US Data Privacy Framework (DPF) certification of the subprocessor.
• Supplementary technical measures: encryption in transit (TLS 1.3), encryption at rest, access controls.

You may request a copy of the SCCs in force with any subprocessor by emailing hello@usericly.com.

8. Data Retention

We keep your data only as long as necessary for the purpose for which it was collected:

• Account data — for the duration of your account. If you delete your account, we remove personal data within 30 days, except as required by legal retention obligations below.
• Subscription & billing records — 10 years from the end of the fiscal year, as required by French fiscal law (Code de commerce, Art. L. 123-22).
• Upload & Share files — links stop working when they expire (3 days on Free, 30 days on Pro and Founding), and the files are deleted automatically within about two hours. Revoking a link in the app stops access right away; the file is kept for 48 hours so you can undo, then deleted.
• Links we turn off — if we turn off a shared link after a report (see our DMCA Policy), its files are kept without access for 30 days, even if the link expires in the meantime, so that a valid counter-notice can restore it. Then they are deleted.
• Reports and counter-notices — kept 3 years after they are closed, to handle disputes and repeat infringement. A report with no action is closed after 90 days.
• Visits to shared download pages — the pseudonymous code described in 2.4 bis is erased after 90 days; the anonymous counts remain.
• IP address logs — 12 months for security/abuse forensics, then deleted or anonymized.
• Email opt-out records — retained indefinitely to honor your unsubscribe preference even after account deletion.
• Backups — operational backups of databases are kept up to 30 days, after which they are cycled out.
• AI input data — not retained by us. Subprocessor retention varies (see their respective policies).
• Reviews — kept until you ask us to remove them or delete your account. If you withdraw your consent, or if we decide not to publish a review, its photo is deleted immediately and the rest within 30 days. An unused review link expires after 30 days at most. Unconfirmed reviews are deleted after 7 days, photo included; reviews sent with an address that has no Ricly account are not kept at all.
• Satisfaction survey answers — kept for as long as your account exists, and deleted with it.
• “Send it to my Mac” addresses — deleted right after the next-day check-in, unless you agreed to the founder deal and rare news; then kept until you unsubscribe, or 3 years after our last email (see 2.9).

9. Your Rights (GDPR & Equivalent)

You have the following rights regarding your personal data:

• Right of access (Art. 15) — obtain a copy of the personal data we hold about you.
• Right to rectification (Art. 16) — request correction of inaccurate or incomplete data.
• Right to erasure / “right to be forgotten” (Art. 17) — request deletion of your data.
• Right to restrict processing (Art. 18) — request that we limit how we use your data.
• Right to data portability (Art. 20) — receive your data in a machine-readable format and transmit it to another controller.
• Right to object (Art. 21) — object to processing based on legitimate interest, including direct marketing.
• Right to withdraw consent — for any processing based on consent (marketing emails, reviews, etc.), you can withdraw your consent at any time via Settings → Email notifications or by emailing us.
• Right not to be subject to automated decision-making — we do not perform automated decision-making with legal effects on you.

To exercise any of these rights, email hello@usericly.com with subject [Privacy Request]. We respond within 30 days (extendable by 2 months for complex requests, with notice).

10. Security Measures

We implement appropriate technical and organizational measures to protect your data:

• TLS 1.3 encryption for all data in transit between you and our servers.
• Encryption at rest for files in Cloudflare R2 and database records in Cloudflare D1.
• Firebase Authentication best practices: password hashing, rate-limited sign-in, OAuth flows.
• Principle of least privilege: only the founder has direct access to production databases ; subprocessor employees access is restricted per their own security programs.
• Regular security review of code changes (manual code review for every commit touching auth, billing, or data storage).
• Webhook signature verification for all Stripe events.
• Rate limiting on API endpoints to prevent enumeration and abuse.

In the event of a personal data breach likely to result in high risk to your rights and freedoms, we will notify affected users without undue delay (within 72 hours where feasible) per GDPR Art. 33-34.

11. Children

Ricly is not intended for users under 16. We do not knowingly collect personal data from children under 16 (or the applicable minimum age in your country). If you believe a child under 16 has created an account, email us and we will delete the account and associated data.

12. Complaints to a Supervisory Authority

If you believe our processing of your data violates GDPR or your national data protection law, you have the right to lodge a complaint with a supervisory authority. In France, the competent authority is:

CNIL — Commission Nationale de l’Informatique et des Libertés
3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France
cnil.fr/en/plaintes

If you reside in another EU/EEA country, you may contact the supervisory authority of your country of residence.

13. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be notified to active users by email at least 30 days before they take effect. The current version is always available at usericly.com/legal/privacy. The “Last updated” date at the top of this policy reflects the most recent revision.

14. Contact

For any question, complaint, or request related to this Privacy Policy:

Email: hello@usericly.com (prefix subject with [Privacy] or [GDPR] for prioritized handling).
A postal address can be provided on request by writing to the address above.