Controller and contact
The controller of your personal data within the meaning of Article 4(7) of Regulation (EU) 2016/679 (“GDPR”) is:
For anything related to personal data, including exercising your rights, write to privacy@rentyourtime.app. The controller has not appointed a data protection officer. Given the current scale and nature of the processing, the controller considers that none of the conditions in Article 37(1) GDPR that would make an appointment mandatory are met.
What this policy covers
This policy covers processing in connection with:
- the rentyourtime.app website (information pages, demo, account, dashboard);
- the RentYourTime API (api.atlashc.pl) used by the website and the RentYourTime apps;
- your RentYourTime account, including sign-in with Google, Apple, Facebook and Discord;
- the Pro subscription, the Founder Program and voluntary support payments, processed by Stripe;
- the waitlist, RentYourTime for Teams pilot requests and beta sign-ups through our Discord bot;
- our newsletter (news and product updates by email), if you subscribe to it;
- your correspondence with us.
The RentYourTime mobile apps use the same account and API, and this policy applies to them to that extent, including the optional usage analytics described in section 7. Information about data processed only on your device or by an app store will be provided with the app in the store.
Where the data comes from
- You — what you enter in forms or upload (e.g. email, username, shipping details, a profile photo).
- Google, Apple, Meta (Facebook) or Discord — when you choose to sign in with them or connect them, including the address of your profile picture that Google, Meta and Discord return (see section 5).
- Stripe — customer, subscription and payment identifiers and their statuses (section 6).
- Discord — your Discord user ID and username when you join the beta through our bot.
- Your browser — technical data sent automatically when you use the website (e.g. IP address, browser type).
- Your browser or app, if you consent to analytics — how you use the website or app (section 7).
What we process, why, and on what legal basis
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Account: email address, password (we store only its scrypt hash), optional username, account ID, the IDs that Google, Apple, Facebook and Discord assign to you if you sign in with them or connect them (section 5), email verification status, role, creation, update and last sign-in dates | Creating and running your account, signing in, providing the service | Art. 6(1)(b) — performance of a contract |
| Sessions: session tokens (we store only their SHA-256 hashes) and issue dates; in the mobile apps also platform, device, IP address and user agent at sign-in | Keeping you signed in, session management, abuse detection | Art. 6(1)(b) and (f) — legitimate interest in account security |
| Email verification and password reset: email address, one-time tokens (hashed) valid for 24 hours (verification) or 60 minutes (reset) | Confirming your address, recovering access | Art. 6(1)(b) |
| Account settings: time zone, locale, currency, daily allowance and virtual rent rate; usage data sent by the app (daily time totals, virtual rent, goal met) and virtual receipts | Running app and dashboard features (meters, history) | Art. 6(1)(b) |
| Demo: simulation parameters (time, allowance, rate, support percentage); if you are signed in, the link between the generated demo receipt and your account | Generating a demo receipt and its number | Art. 6(1)(b); for visitors who are not signed in, the receipt is not linked to any identifier |
| Subscription and payments: Stripe customer ID, subscription, checkout session and transaction IDs, plan, status, billing period dates, auto-renewal flag, applied discount, Stripe invoice data (number, amounts, currency, status, links) | Concluding and performing the contract, payments, refunds and complaints | Art. 6(1)(b); Art. 6(1)(c) — tax and accounting obligations; Art. 6(1)(f) — establishing, exercising and defending legal claims |
| Founder Program: tier, Founder number, amount, payment status, Pro period, Discord role status; for Founder Black — full name, shipping address, country, T-shirt size, tracking number | Performing the contract, granting benefits, shipping the Founder Black kit | Art. 6(1)(b); Art. 6(1)(c) and (f) (as above) |
| Founder profile: display name and your choices: listing in the Founders directory, in the credits, and being contacted about promotional material or a case study | Featuring you only in the ways you agreed to | Art. 6(1)(a) — consent, which you can change in the dashboard at any time |
| Profile photo (optional): a picture you upload yourself. We convert it to a small square image and remove camera and location metadata; we do not keep the original file. We also store your choice whether the photo may be shown on the public Founder Credits Wall. This is separate from the profile picture address received from Google, Facebook or Discord (next row), and it always takes priority over it | Showing the photo in your own account and dashboard; showing it on the public Founder Credits Wall only if you allow it, which also requires that you are included in Founder Credits | Art. 6(1)(a) — consent: you choose to add the photo and can remove it at any time, and the public display has its own setting, which you can change in your account and dashboard at any time |
| Profile picture from Google, Facebook or Discord (automatic, when you sign in with them): the web address (URL) of the profile picture that Google, Meta or Discord returns at sign-in — not the image file, which we do not copy or store. We keep the address only if it is an https address on the provider’s own image servers (Google: googleusercontent.com; Meta: fbcdn.net and fbsbx.com; Discord: cdn.discordapp.com) and replace it with the newer one each time you sign in with that provider; if Facebook reports that your account has only its default silhouette, or your Discord account has no avatar of its own, we delete the stored address. Apple provides no profile picture, so we store none. The address stays stored while you use a photo you uploaded yourself, so that the provider’s picture can be shown again if you remove your own | Showing a profile picture in your account and dashboard when you have not uploaded your own; showing it on the public Founder Credits Wall only if you allow it (the same setting as for your own photo, which also requires that you are included in Founder Credits) | Art. 6(1)(b) — performance of a contract (part of the sign-in you chose) for your own account and dashboard; Art. 6(1)(a) — consent for the public Founder Credits Wall, which you can change in your account and dashboard at any time |
| Voluntary support payments: chosen percentage, amount, currency, status, Stripe IDs, dates | Accepting and recording the payment, handling refunds | Art. 6(1)(b); Art. 6(1)(c) and (f) |
| Waitlist and Teams pilot: email address, sign-up source, status, confirmation, dates, SHA-256 hash of the IP address, user agent, administrator notes | Adding you to the list at your request, confirming your address (link valid for 24 hours), contacting you about early access or the pilot (the launch announcement is sent through Mailchimp, see “Newsletter and launch announcement” below), applying the discount offered to list members, protecting the form against abuse, notifying the administrator of a new sign-up | Art. 6(1)(b) — steps taken at your request; Art. 6(1)(f) — abuse prevention and internal organisation |
| Newsletter (only if you subscribe): email address; when you gave and confirmed your consent; where you signed up (e.g. waitlist or account); whether you are on the waitlist, have an account, are a Founder or a paying Pro subscriber; the language set in your account; your subscription status (subscribed, unsubscribed, bounced); in Mailchimp also whether our emails were delivered and, if enabled for a campaign, opened and which links were clicked | Sending occasional news and product updates, choosing which of them are relevant to you (e.g. Founders or language), campaign statistics, keeping a record of your consent and of your unsubscribe so that you are never emailed after opting out | Art. 6(1)(a) — consent (together with Article 398 of the Polish Electronic Communications Law); the unsubscribe record kept afterwards — Art. 6(1)(f) (making sure you are not emailed again) |
| Review request in the dashboard: when the request to review RentYourTime on Trustpilot was shown to you, whether you dismissed it and whether you opened Trustpilot from it; to decide whether to show it we use your account age and the number of days with usage data or receipts (see “Reviews on Trustpilot” below) | Asking people who have really used RentYourTime for a public review, the same way for everyone, and not asking again too often or after you opened Trustpilot | Art. 6(1)(f) — legitimate interest in honest public feedback on the service |
| Beta (Discord): email address, Discord user ID and username, sign-up date | Registering you for beta testing and contacting you about it | Art. 6(1)(b) |
| Security: SHA-256 hashes of IP addresses used for rate limiting; a security event log (e.g. app sign-in, password change, account deletion; for administrator actions also the administrator’s IP address and user agent) | Preventing abuse and unauthorised access, accountability | Art. 6(1)(f) |
| Request data: IP address, date and time, requested page, request headers — processed by the website hosting provider; application error messages | Delivering the website, keeping it available and secure, diagnosing errors | Art. 6(1)(f) |
| Analytics (consent only): cookie identifiers, pages viewed, referral source (including UTM parameters), approximate location, device and browser type, events (section 7); with PostHog also your account ID once you sign in (never your email address), product events on the website, in the apps and from our server (including the plan, amount and currency of a purchase), error reports and recordings of visits to the information pages | Statistics on the information pages and on marketing channel performance; understanding how the website and apps are used in order to improve them; finding and fixing errors | Art. 6(1)(a) — consent (together with Article 399 of the Polish Electronic Communications Law) |
| Correspondence: message content, email address, data you include | Replying, handling requests, complaints and data protection requests | Art. 6(1)(b) or (f); for GDPR requests — Art. 6(1)(c) with Articles 12–22 GDPR |
We do not collect special categories of data (Article 9 GDPR), we do not sell personal data and we do not use it for behavioural advertising on the website. We send the newsletter only to people who asked for it (below); account, security and purchase emails are not marketing and do not depend on that consent.
Newsletter and launch announcement (Mailchimp)
- Joining the waitlist before launch means one thing: we email you when the app launches. You receive news and product updates only if you also tick the optional box under the waitlist form, sign up for updates after launch, or switch on “News and product updates by email” in your account settings. Your consent counts once you confirm it with the link we email you (or, in the account, once your email address is verified). Creating an account, signing in or buying never subscribes you.
- We send these emails with Mailchimp (The Rocket Science Group LLC d/b/a Mailchimp, an Intuit company, USA). Mailchimp receives only the data listed in the “Newsletter” row above — never your password, payment or card details, usage data, IP address or session identifiers. Account, security and purchase emails are still sent by Amazon SES.
- You can unsubscribe at any time with the link in every newsletter email or the switch in your account settings. An unsubscribe made in Mailchimp is copied to your account, and we never subscribe you again on our own; if you subscribe again later, Mailchimp asks you to confirm by email.
- Deleting your account, or asking us to delete your waitlist entry, unsubscribes you. Mailchimp then keeps only your address marked as unsubscribed, so that it is never emailed again by mistake; you can ask us to delete it from Mailchimp completely.
Reviews on Trustpilot
Public reviews of RentYourTime are collected and published by Trustpilot (Trustpilot A/S, Pilestræde 58, 1112 Copenhagen K, Denmark), an independent review platform. We use it in the ways below, which differ in what, if anything, Trustpilot receives from us:
- Links (in use). The website and the dashboard link to our profile on trustpilot.com and to its review form. Our pages load nothing from Trustpilot and we pass no data about you or your account to Trustpilot; nothing happens unless you click a link. The link opens Trustpilot in a new tab without telling it which of our pages you came from. From then on you are on Trustpilot’s website, and Trustpilot processes your data there (for example your IP address and browser details, and your review and Trustpilot account if you write one) as a separate controller under its own privacy policy. Writing a review is voluntary and it is public; we cannot edit or remove reviews on Trustpilot.
- Review request in the dashboard (in use). Once your account is at least 14 days old and you have completed at least 3 days in the app (a daily receipt) or used it on at least 7 different days, the dashboard may show a small request, which you can dismiss, to review us on Trustpilot. The rule is the same for everyone, whatever your plan and whatever you might write. We record only when it was shown, whether you dismissed it and whether you opened Trustpilot from it — not whether you wrote a review, which we cannot know — so that we ask at most three times and stop once you open Trustpilot or dismiss the request twice. This happens entirely on our side: nothing is sent to Trustpilot. With analytics consent, PostHog also records that the request was shown or dismissed, or that a Trustpilot link was clicked (never anything you write).
- Trustpilot review widget (not used). The website does not show Trustpilot’s widget (“TrustBox”) at present. If we add it, it will load from Trustpilot’s servers only after you consent in the cookie banner, which will then name Trustpilot, and we will update this policy first.
- Review invitations by email (not active). We do not send review invitations at present, and Trustpilot receives no data from us for them. We may later use Trustpilot’s Automatic Feedback Service. Our server would then send Trustpilot, once per person, your email address, your RentYourTime account ID (as a reference number) and the language of the review page — never your name, password, payment details or usage data — and Trustpilot, acting as our processor, would send you one neutral invitation to review RentYourTime on our behalf; if you open it or its link, Trustpilot also receives technical data such as your IP address. We would invite only account holders who meet the same usage rule as the dashboard request, whose email address is verified, who have switched on “News and product updates by email” and who have not opened Trustpilot from the dashboard request or dismissed it recently. The legal basis would be your consent (Art. 6(1)(a) GDPR, together with Article 398 of the Polish Electronic Communications Law); before we switch invitations on, the description of that setting will say that it includes review requests. Switching the setting off stops any invitation not yet passed to Trustpilot, and you can ask us to have invitation data that Trustpilot already holds deleted.
Sign-in with Google, Apple, Facebook and Discord
External sign-in is optional — you can also create an account with an email and password. After you sign in with a provider, our server verifies the token (for Discord: the one-time code) it received and issues its own RentYourTime session token. The legal basis is Article 6(1)(b) GDPR. Sign-in providers are separate controllers of the data they process and apply their own privacy policies.
| Apple | Facebook (Meta) | Discord | ||
|---|---|---|---|---|
| What we receive | A Google Identity Services ID token containing, among others, your Google account ID, email address, whether it is verified, name and profile picture | A Sign in with Apple identity token (including your Apple ID, email address — possibly an Apple relay address — and whether it is verified); your name only on the first authorisation, if you share it | A Facebook Login access token with the public_profile and email permissions; with it we fetch from the Meta Graph API only: your app-scoped user ID, name, email address (if you share it) and the address of your profile picture (and whether it is only Facebook’s default silhouette) | After you approve RentYourTime on Discord with the identify and emailpermissions, Discord returns a one-time code. Our server exchanges it for an access token and uses that token once to read from the Discord API only: your Discord user ID, username and display name, email address and whether Discord has verified it, and your avatar |
| How we verify | Token signature and audience (Google public keys); a verified email address is required | Signature (Apple public keys), issuer and audience; a verified email address is required | Token validity, expiry and that it was issued for our app (Meta Graph API debug_token), matching user ID | Our server exchanges the code with Discord itself, using our app’s secret and a one-time proof (PKCE) that never leaves our server; the sign-in must come back to the browser that started it, within 10 minutes, and can be completed only once |
| What we store | Your Google account ID (the sub value of the ID token), email address; name as the account name — only when a new account is created; the address of your Google profile picture, replaced at each Google sign-in (not the image) | Your Apple ID for our app (the sub value of the identity token), email address; name as the account name if the account has none | Your Facebook user ID for our app, email address, name as the account name (if the account has none). If Facebook does not provide an email, the account gets a technical placeholder address (fb_…@facebook.rentyourtime.app) marked as unverified. We also store the address of your Facebook profile picture, replaced at each Facebook sign-in (not the image) | Your Discord user ID; when an account is created through Discord, the email address if Discord has verified it (otherwise a technical placeholder address discord_…@discord.rentyourtime.app marked as unverified) and your display name or username as the account name; the address of your Discord avatar, replaced at each Discord sign-in (not the image) |
| What we do not store | The ID token (it is not saved in our database, our code does not put it in localStorage, sessionStorage or cookies, and does not write it to logs), the profile picture file itself (only its address, see above) | The identity token (handled in the same way). Apple provides no profile picture, so none is stored | The access token (it is not saved in our database, our code does not put it in localStorage, sessionStorage or cookies, and does not write it to logs), the profile picture file itself (only its address, see above), friends list or any other Facebook data | The one-time code and Discord’s access and refresh tokens (not saved in our database, not put in localStorage, sessionStorage or cookies, not written to logs; we revoke Discord’s access right after the sign-in), the avatar file itself (only its address, see above), your servers, friends, messages or any other Discord data |
| Why we store the provider ID | To recognise you when you sign in with that provider, to make sure that one provider account belongs to only one RentYourTime account, and to show you which providers are connected to your account | |||
| Account linking | We look for an account by the stored Google or Apple ID first. If none is stored, we look for an account with the same email address; if one exists, you are signed in to it, the address is marked as verified and the ID is added to it (an ID is never moved from one account to another) | We look for an account by Facebook ID first, then by email address; in the latter case the Facebook ID is added to the existing account | We look for an account by Discord ID only. If no account has it and the email address Discord verified already belongs to an account, sign-in is refused and nothing is merged: sign in with your usual method and connect Discord in “Connected accounts”. Otherwise a new account is created | |
| Connecting a provider to your account | In the account page (“Connected accounts”) you can connect Google, Apple, Facebook or Discord to the account you are signed in to, also when the provider’s email address is different. We verify the provider’s token (for Discord: the one-time code) in the same way as at sign-in and then store the provider ID on your account; being signed in is enough, we do not ask for your password. A provider account that is already connected to another RentYourTime account cannot be connected again, and we never merge accounts. You can disconnect a provider in the same place after confirming your RentYourTime password (we check it ourselves; it is never sent to the provider): we then delete its ID and the address of its profile picture from your account (your account, its data and your current sign-in stay). An account without a password has to set one first (“Forgot password”). If your Google, Apple or Facebook account uses the same email address as your RentYourTime account, signing in with it connects it again (see above). You can also ask us by email (see Data deletion) | |||
| Provider script | Loaded from accounts.google.com when the sign-in form is shown | Loaded from appleid.cdn-apple.com when the sign-in form is shown | Loaded from connect.facebook.net only after you click “Continue with Facebook” | None: Discord’s own page opens in a pop-up window only after you click “Continue with Discord” or “Connect Discord”, and returns to a page of ours that hands the one-time code only to the page that opened it and removes it from the address bar |
Loading a provider’s script or sign-in page means your browser sends that provider technical data (e.g. your IP address). Provider scripts may store their own cookies needed for sign-in in your browser, under the providers’ policies. We keep the data stored on our side until your account is deleted. Disconnecting RentYourTime in your Google, Apple, Facebook or Discord settings does not delete your RentYourTime account — see Data deletion.
Which profile picture is shown
The picture that represents you in RentYourTime is chosen in this order: (1) the photo you upload yourself, which we store and serve ourselves (section 4); (2) the address of your Google profile picture; (3) the address of your Facebook profile picture; (4) the address of your Discord avatar; (5) the address of an Apple profile picture — Apple does not provide one, so this step does not currently apply; (6) if none is available, your initials, drawn by the website or app from your account name (or the beginning of your email address) without any picture. Your own photo is stored and handled independently of the provider’s picture and always takes priority. If you remove it, the provider’s picture may be shown again.
We do not copy a provider’s picture into our storage. Your browser or app loads it directly from the provider’s image servers (Google, Meta or Discord), so that provider receives the technical data your device sends with any such request, for example your IP address and the information in the HTTP request (such as browser type); on the website we ask the browser not to send the address of the page it is on. The same happens for visitors to the public Founder Credits Wall when a Founder who allowed it is shown with such a picture. The provider processes that data under its own privacy policy. If the picture cannot be loaded — for example because the provider’s link has expired, which happens with some Facebook picture links — it is not shown and your initials appear instead, until your next sign-in with that provider refreshes the address.
We validate every provider picture address before storing it: only https addresses on the provider’s own image servers listed in section 4 are accepted and anything else is discarded; we take such an address only from the provider’s verified reply, never as a value you send us. You can remove your own photo in the dashboard or on the account page; the provider’s address is deleted when you delete your account, or on request (section 11).
Google User Data and Google Sign-In Disclosure
RentYourTime provides Sign in with Google (Google Identity Services) as an optional, secure, and passwordless authentication method on our website and mobile applications. In full accordance with the Google API Services User Data Policy and Google OAuth verification standards, this disclosure describes our data practices regarding Google user data:
- Google User Data Collected: When you choose to authenticate using Google, RentYourTime requests only the standard, non-sensitive OpenID Connect identity scopes (
openid,email, andprofile). Google provides a cryptographically signed identity token (ID token) containing:- Your unique Google account identifier (the
subclaim); - Your verified email address (the
emailclaim andemail_verifiedflag); - Your full or display name (the
nameclaim), used to initialize your account display name; - The web address of your Google profile picture (the
pictureclaim ongoogleusercontent.com), stored only as an address to display your avatar.
- Your unique Google account identifier (the
- No Sensitive Scopes and No Password Access: RentYourTime does not request, access, read, or process any sensitive or restricted Google API scopes (such as Google Drive, Gmail, Google Calendar, or Google Contacts). Furthermore, RentYourTime never receives, sees, or stores your Google account password.
- How Google User Data Is Used (Specific Purposes): Data received from Google is utilized strictly and exclusively for:
- User authentication, session establishment, and secure identity verification across devices;
- Creating and administering your RentYourTime user account, and preventing duplicate accounts;
- Displaying your basic profile information (name and avatar photo) within your private account settings and dashboard.
- Data Storage and Security Measures: Your Google account ID (
google_sub), email address, display name, and profile picture URL are stored securely in our PostgreSQL database hosted in the European Union. The temporary Google ID token is validated against Google’s public JWKS certificates and immediately discarded; it is never persisted in permanent storage, written to application logs, or stored in browser cookies. - Data Retention and Account Deletion: Google user data is retained only for the duration of your active RentYourTime account. You retain full control over your data:
- Account deletion: You can delete your RentYourTime account and all associated data at any time via Account Settings, through our Data deletion instructions, or by emailing privacy@rentyourtime.app. Upon deletion, all Google-provided user data is permanently and irrevocably erased from our systems.
- Revoking Google permissions: You can revoke RentYourTime’s access at any time in your Google Account Third-party apps & services permissions.
- No Sale, No Advertising, and No Third-Party Transfers: RentYourTime never sells, rents, or trades Google user data to any third party, broker, or marketing entity. Google user data is never used or transferred for advertising, personalized marketing, or retargeting purposes. Google user data is never transferred to third parties except trusted hosting infrastructure providers operating as GDPR Article 28 data processors under strict data processing agreements.
- Limited Use Compliance: RentYourTime’s use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Payments (Stripe)
Payments are handled by Stripe on the Stripe Checkout payment page. The controller is the seller. You enter card and other payment details directly into Stripe’s form — we never receive or store your card number. We pass to Stripe: your account email (or Stripe customer ID), your RentYourTime account ID, the chosen plan or product, discount information and — if you consented to analytics — your DataFast visitor and session IDs (used to attribute revenue to a marketing channel) and a note that you consented, so that we can count the completed payment in our analytics (section 7). Through signed notifications (webhooks) Stripe sends us IDs and statuses of subscriptions, payments, invoices and refunds. Stripe also processes data as a separate controller, e.g. for fraud prevention and its own legal obligations (Stripe Privacy Policy).
Recipients
We entrust data to providers who process it on our behalf (processors, Article 28 GDPR) under data processing terms that form part of their service agreements. Some recipients act as separate controllers.
| Recipient | Role and scope | Status |
|---|---|---|
| Cloudflare, Inc. (USA) | Hosting and delivery of rentyourtime.app, DNS, traffic protection; processes data of every request to the website; storage (Cloudflare R2) and delivery of profile photos you upload yourself | Processor |
| Supabase Pte. Ltd. (Singapore) | Account and service database; data stored in an AWS data centre in eu-west-1 (Ireland) | Processor |
| Amazon Web Services EMEA SARL (Luxembourg) | Email delivery (Amazon SES, eu-central-1 — Frankfurt); API server infrastructure | Processor |
| The Rocket Science Group LLC d/b/a Mailchimp, an Intuit company (USA) | Newsletter and launch announcement: the list of subscribers, their subscription status and campaign statistics (only if you are on the waitlist or subscribed) | Processor |
| Trustpilot A/S (Denmark) | Public reviews on trustpilot.com, which you reach only through our links; review invitations by email (not active at present): email address, account ID and page language, to send one invitation on our behalf | Separate controller for its website and reviews; processor for review invitations, once switched on |
| Microsoft Ireland Operations Limited | Mailboxes on the rentyourtime.app domain (your correspondence with us) | Processor |
| Stripe Payments Europe, Limited (Ireland) and Stripe group companies | Payments, subscriptions, invoices and refunds | Processor; separate controller for its own purposes (e.g. fraud prevention) |
| Google Ireland Limited | Google Analytics 4 (with consent); Google Ads conversion measurement (with consent); Google sign-in; delivery of your Google profile picture to your browser or app | Analytics — processor; Google Ads — separate controller, and processor for the hashed e-mail addresses it matches; sign-in and profile picture — separate controller |
| JustShipIt Pte. Ltd. (DataFast, Singapore) | Analytics (with consent), AI crawler measurement | Processor |
| PostHog Inc. (USA); our project is hosted in PostHog’s US Cloud (United States) | Analytics, error reports and recordings of the information pages, on the website and in the apps (with consent) | Processor |
| Apple (for EEA users — Apple Distribution International Ltd., Ireland) | Sign in with Apple; in-app purchases on iOS, if you make them | Separate controller |
| Meta Platforms Ireland Limited | Facebook sign-in; delivery of your Facebook profile picture to your browser or app | Separate controller |
| Discord (for EEA users — Discord Netherlands BV) and Discord Inc. (USA) | Beta sign-ups through the bot; private notifications to the administrator about new waitlist, pilot and beta sign-ups (email address, source, date); Discord sign-in and connecting Discord to your account; delivery of your Discord avatar to your browser or app | Messaging provider processing data under its own terms; sign-in and avatar — separate controller |
| Google (Google Play), Apple (App Store) | In-app purchases in the mobile apps, if you make them — they send us the subscription status | Separate controllers |
| Advisers (e.g. accountants, lawyers), public authorities | Where required by law or necessary to defend claims | Separate controllers or processors |
Transfers outside the European Economic Area
Some recipients are based or have infrastructure outside the EEA (including the USA and Singapore) or may access data from outside the EEA: Cloudflare, Stripe, Google, Meta, Apple, Discord, DataFast (infrastructure including the USA), Supabase, PostHog (a US company; our project is hosted in the USA), Mailchimp (servers in the USA) and — for technical support — AWS and Microsoft. Transfers rely on:
- Commission Implementing Decision (EU) 2023/1795 on the adequacy of the EU-US Data Privacy Framework — for US organisations certified under it (Article 45 GDPR), including Mailchimp, which is covered by Intuit’s certification;
- standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 (Article 46(2)(c) GDPR) — in other cases, including DataFast, Supabase and PostHog (its data processing agreement); Mailchimp’s data processing addendum also includes them, should the Data Privacy Framework cease to apply.
Trustpilot A/S is established in the EEA. For review invitations by email — only once we switch them on — its sub-processors include companies in the USA, the United Kingdom and Australia; under Trustpilot’s data processing agreement, data leaves the EEA only with the safeguards the law requires, in particular standard contractual clauses.
You can get a copy of these safeguards by writing to privacy@rentyourtime.app.
How long we keep data
| Data | Period |
|---|---|
| Account, settings, usage data, external sign-in data | Until the account is deleted; after that — as described on the Data deletion page |
| Session tokens | Expire after 30 days (website) or 30 days after the last refresh (apps); revoked on sign-out and deleted when the account is deleted |
| Email verification and password reset tokens | Valid for 24 hours or 60 minutes; expired tokens are removed during later operations of the same kind, and all of them when the account is deleted |
| Mobile app session records (IP address, user agent) | Until the account is deleted — then the IP address and user agent are removed |
| Payment records: subscriptions, invoices, Founder purchases and support payments | Until the tax liability limitation period ends — as a rule 5 years from the end of the calendar year in which the tax payment deadline fell (Articles 70 § 1 and 86 § 1 of the Polish Tax Ordinance) — or, if longer, until contractual claims become time-barred |
| Founder Black shipping details | For shipping and for the period of liability for the goods’ conformity, together with the purchase records — not deleted automatically on account deletion |
| Founder profile (name, consents, including the choice about showing your photo) | Until you withdraw consent, change the settings or delete the account |
| Profile photo | Until you remove or replace it or delete your account. Removing or replacing the photo, or deleting the account, deletes the stored file; copies may remain in browser and Cloudflare caches for up to 24 hours |
| Profile picture address from Google, Facebook or Discord | Until it is replaced by a newer address at your next sign-in with that provider, is deleted (Facebook or Discord reports no picture), or you delete your account; you can also ask us to erase it earlier. Removing your own photo does not delete it. The picture itself stays with the provider |
| Newsletter (Mailchimp) | Until you unsubscribe or withdraw consent. After that — and after account deletion — Mailchimp keeps your address marked as unsubscribed until you ask us to delete it; campaign statistics for as long as the contact exists in Mailchimp |
| Review request history (dashboard) | Until the account is deleted; it is included in the copy of your data you can download |
| Review invitation data at Trustpilot (only once invitations are switched on) | Under Trustpilot’s data processing agreement: the message we send to trigger an invitation — 30 days; other invitation data — up to 2 years, or earlier if we ask Trustpilot to delete it. Reviews you write and your Trustpilot account are kept under Trustpilot’s own policy |
| Waitlist, Teams pilot, beta | Until you opt out or request deletion, delete an account with the same email address, or the list or programme ends; no automatic deletion period is applied at the moment |
| Administrator notifications in Discord | Until the messages are deleted |
| Security event log | No automatic deletion period at the moment; entries contain no passwords or tokens and, after account deletion, are not linked to your email address |
| Analytics data (consent only) | Google Analytics 4 — per the property setting (2 or 14 months in the standard version); Google Ads — per Google’s terms for conversion data; DataFast — per the provider’s terms; PostHog — per the data retention of our PostHog project (recordings are kept for a shorter period than events); cookies — see section 7. Deleting your account does not remove analytics data already sent to PostHog: write to us and we will delete the data linked to your account ID |
| Website hosting logs (Cloudflare Workers) | 3 or 7 days, depending on the plan |
| Database backups | Overwritten on a rolling basis; according to the database provider’s documentation they are available for no more than 30 days |
| Correspondence, including GDPR requests | While the matter is handled and then — to the extent needed to show it was handled properly — until any claims become time-barred |
Your rights
Under the GDPR you have the right to:
- access your data and obtain a copy (Article 15);
- rectification (Article 16);
- erasure (Article 17);
- restriction of processing (Article 18);
- data portability for data you provided, processed by automated means on the basis of contract or consent (Article 20);
- object to processing based on legitimate interests, on grounds relating to your particular situation (Article 21(1)); an objection to direct marketing (our newsletter) always prevails (Article 21(2));
- withdraw consent at any time, without affecting the lawfulness of earlier processing (Article 7(3)) — analytics: “Cookie settings” in the footer, and “Share usage analytics” in the app settings; Founder profile and photo: dashboard and account page; newsletter: the unsubscribe link in any newsletter email or “News and product updates by email” in the dashboard settings (the same setting will also stop review invitations, once we switch them on);
- lodge a complaint with a supervisory authority — in Poland: President of the Personal Data Protection Office (Prezes UODO), ul. Stanisława Moniuszki 1A, 00-014 Warszawa, uodo.gov.pl; you may also contact the authority in the EU/EEA country where you live or work.
How to exercise your rights
- Yourself: once signed in on the account page, you can download a copy of your data (JSON file) and delete your account; change your Founder name and consents in the dashboard.
- By email: privacy@rentyourtime.app, preferably from the address linked to your account.
We reply without undue delay and within one month of receiving your request; for complex or numerous requests this can be extended by two further months — we will tell you within the first month (Article 12(3) GDPR). Exercising your rights is free, subject to Article 12(5) GDPR. If we have reasonable doubts about the identity of the person making the request, we may ask for additional information (Article 12(6) GDPR) — usually a confirmation from the email address linked to the account.
Automated decision-making and profiling
We do not make decisions about you based solely on automated processing that produce legal or similarly significant effects (Article 22 GDPR). The system automatically checks whether your account email is on the waitlist in order to apply the discount offered to list members — if you think the discount was applied incorrectly, contact us. Analytics (with consent) is used for statistics and to improve the product, not for decisions about individuals.
Do you have to provide data
Providing data is voluntary but necessary for some features: an email address (and a password or external sign-in) to create an account; billing details in Stripe to buy; shipping details to receive the Founder Black kit; an email address to join the waitlist. A username, a profile photo, the Founder profile, analytics consent and the newsletter are entirely optional.
Security
We apply technical and organisational measures appropriate to the risk (Article 32 GDPR), including encrypted connections (HTTPS), storing passwords and tokens only as cryptographic hashes, limiting data access to authorised persons, rate limiting, verifying payment notification signatures and sign-in provider tokens, and data minimisation. We do not store payment card data. No system is perfectly secure; in the event of a personal data breach we will act under Articles 33 and 34 GDPR, including notifying you without undue delay where required.
Minors
The service is intended for people aged 16 and over. We do not knowingly collect data from younger people. If you believe someone under 16 has created an account, write to privacy@rentyourtime.app and we will delete it.
Changes to this policy
We update this policy when our processing or the law changes. Each version has a number and effective date at the top of the page. We will announce material changes on the website and, to account holders, by email. If a change requires your consent, we will ask for it separately. Previous versions are available on request.
This policy: https://rentyourtime.app/privacy · Terms: https://rentyourtime.app/terms · Data deletion: https://rentyourtime.app/privacy/data-deletion