Parigo privacy policy
Last updated: 20 November 2026
This policy applies to Parigo 1.0.0 on iOS (iPhone).
1. In short
- Parigo is a notebook: a list of expenses and accounts that you enter yourself. It does not manage your money, does not move euros and does not connect to banks.
- What you enter is stored only on your device: transactions, accounts and groups, and the transactions you confirm when importing a bank file. There is no user account and no server of ours. We cannot see it.
- The first time it opens, Parigo asks for your year of birth. You must answer, it is stored only on your device, and you can correct it later in Preferences. Before you answer, and always if you are under 16, Parigo does not start any third-party advertising or purchase service (neither Google's consent form, nor AdMob, nor RevenueCat).
- Parigo is free and, from age 16, shows ads (a small banner). Google AdMob serves them. Where needed, Google first shows you a consent form, and Parigo only requests ads when Google's SDK indicates that it may: after you have made your choice in the form, or where the form is not required. Declining in the form does not remove the ads: Google may serve limited ads in line with your choice. Removing the ads is what the subscription does. We ask Google for non-personalised ads with G-rated content (at 16 and 17, also with its treatment for adolescents). Under-16s are not shown advertising. The app does not ask for iOS's tracking permission (ATT) and does not access the advertising identifier (IDFA).
- There is an optional "No ads" subscription, from age 16. Apple charges for it and manages it. RevenueCat checks whether it is active using a random identifier of the app, with no name or email.
- Parigo does not send Google or RevenueCat the content of your accounts, transactions, amounts, names or groups. They do receive the technical and subscription data described in sections 4 to 6.
- Sharing a group is an exchange of files that you do by hand. Parigo does not sync anything on its own.
2. Who is responsible and how to contact us
Owner and controller: Emilio Franco González, an individual (self-employed). Address: Calle Cueva de la Pileta 2, 41020 Sevilla (España). Tax ID (NIF): 30263193T. Contact: soporte@parigo.app.
Contact for any question or request about this policy: soporte@parigo.app.
3. What data is stored on your device
What you enter is stored on the device itself, in the app's private storage, which other apps cannot access: accounts and their opening balance, transactions (amounts, dates, descriptions, categories), budgets, goals, groups and the names you type for their participants, recurring costs and your settings. Your year of birth (section 13) is also stored here, and only here: it is sent to nobody and is not included in private backups or exports.
System backups. Parigo asks the system not to include its data in the iPhone backup or in iCloud. According to Apple, that flag is only guidance to the system and does not guarantee that the data will never appear in a backup or on a restored device; we cannot guarantee how each version of iOS will act. If the system does not allow it or the app cannot check it, the app tells you on screen. That is why the intended way to move your data to another device or to recover it is the app's private backup (section 9). If you lose your phone without a private backup, you lose that data.
4. What leaves your device, when and to whom
These are all of Parigo's automatic connections. None sends the content of your accounts, transactions, descriptions, amounts, names, groups, statements or files to our servers (there are none), to Google or to RevenueCat. Separately, there are things you can take out of the device on purpose: a private backup, a group you share, or information you copy to the clipboard. That leaves only if you choose it, and it is explained in sections 9 and 10.
Before you answer the age question, and always if you are under 16, Parigo does not connect to Google or to RevenueCat. All it can then use over the network is the optional exchange-rate lookup (section 8, which asks for permission first) and opening the web pages of the policy, the terms and support.
| To whom | When | What it receives | More information |
|---|---|---|---|
| Google (consent form, UMP) | When Parigo opens, only if you are 16 or over according to the year of birth you gave and do not have an active subscription, to find out whether the form needs to be shown to you. For under-16s it is not started | Google processes technical connection data (such as your IP address) and stores your consent choice so that the form works. Google does not publish a detailed list of the data this form processes | Sections 5, 12 and 14 |
| Google (ads, AdMob) | Only if you are 16 or over according to the year of birth you gave, do not have an active subscription and a screen with a banner is in view (Home, Analysis or Groups), and only when Google's SDK indicates that ads may be requested (after your choice in the form or where it is not required). For under-16s it is not started | According to Google's documentation, the ads SDK may process: crash logs, performance data, device identifiers, data about the ads you see, approximate location inferred from the IP, and interactions with the app and ads, such as launches and taps. With the treatment for adolescents (ages 16 and 17) Google turns off personalised ads and remarketing; it does not detail what other data it stops processing | Section 5 |
| RevenueCat | Only if you are 16 or over according to the year of birth you gave. When Parigo opens and when you return to it, when prices load, and when you buy or restore. Also if you never buy. For under-16s it is not started | A random identifier, your subscription and purchase data (the receipt Apple provides and its dates), the device model and iOS version, the Parigo version, the language and, when available, the country of the app store and the device identifier for vendors on iOS (IDFV), the status of iOS's tracking permission (which Parigo does not ask for) and technical connection data, such as the IP address | Section 6 |
| Apple (App Store) | When you buy or manage the subscription | What Apple handles with your Apple account | Section 6 |
| Public exchange-rate services | Only when preparing or editing an expense or an income in another currency, if you have allowed the lookup and a rate is needed. It can happen even if you later cancel the form, and at any age | The date and the currency codes; as with any connection, your IP address | Section 8 |
| The service hosting these pages | If you open the policy, the terms or support from the app, at any age | What any website sees: your IP and technical browser details. The pages are hosted on GitHub Pages (GitHub, Inc.), which logs and stores the IP address of visitors for security purposes, according to its documentation, without stating how long. GitHub bases international transfers on standard contractual clauses and on the EU-US Data Privacy Framework | Sections 12 and 14 |
| Your email app | Only if you tap "Report this ad" | Parigo opens an email to soporte@parigo.app with a ready-made subject. It adds no data about you or your device: only what you write and what your email service sends goes | Section 5 |
| The channel you choose for sharing | Only when you send an invitation or a group file | What you send | Section 10 |
5. Ads and consent
- What you see. If you are 16 or over and do not have the subscription, a small banner labelled "Advertising" on Home, on Analysis and on the Groups list. Parigo only requests ads when Google's SDK indicates that it may (after you have made your choice in the consent form, or where the form is not required). It never appears when you record an expense or a payment, import a file, share, in settings or on the subscription screen. Parigo only requests banners, not full-screen ads. Parigo starts at most five ad requests per session, at least one minute apart. Automatic refresh and video ads are disabled for the AdMob banner ad unit.
- Not personalised. For anyone who sees ads, Parigo asks Google for non-personalised ads, with no keywords or content addresses. Parigo does not send it your banks, transactions, amounts, names or groups. Non-personalised ads are not based on your past behaviour, but Google may still use device identifiers or cookies to limit how often ads are shown, measure them in aggregate and prevent fraud (in limited ads, according to Google, they are not used for advertising purposes; see "Your choice"). "Non-personalised" does not mean "no data": Google processes technical device data and may read or store information on the device to serve the ad.
- Age protections. The first time it opens, Parigo asks for your year of birth and stores it only on your device (section 13). From that year it works out your age cautiously and decides as follows: under 16, no advertising, no consent form, no AdMob and no RevenueCat; 16 and 17, ads always non-personalised, with Google's treatment for adolescents (no personalisation and no remarketing) and with G-rated content; 18 or over, ads in version 1.0.0 non-personalised and with G-rated content (the treatment for adolescents is not applied to adults). When requesting the treatment for adolescents, Google receives an indication derived from your age (not your year of birth). With that treatment, Google turns off personalised ads and remarketing and applies its protections for adolescents; it does not detail what technical data it stops processing. Parigo also requests ads rated G. In AdMob, we have blocked all eleven standard sensitive categories and both restricted categories. These controls do not guarantee that an inappropriate ad will never appear: no filter is perfect and an ad may slip through. If you see an inappropriate one, you can report it (see below).
- Who serves the ad content. Google's SDK loads it; the ad itself may come from Google or from advertisers and ad-technology partners on the list that Google publishes at https://support.google.com/admob/answer/9012903, who may receive your IP address and technical device data.
- No tracking permission. The app does not ask for iOS's tracking permission (ATT) and does not access the advertising identifier (IDFA). Because Parigo does not ask for that permission, Google does not receive the IDFA. Google's SDK may use other identifiers of its own, such as a rotating SDK instance identifier, and technical data such as the IP address; Google does not publish a complete list of the identifiers it uses in that case.
- Your choice. If you are 16 or over, Parigo asks Google whether it should show you the consent form and presents it where appropriate, for example where the law requires it (such as in the European Economic Area, the United Kingdom and Switzerland), before ads are requested. Under-16s are not asked and are not shown the form. Declining does not block the app, oblige you to pay or remove the ads: Google may serve limited ads in line with your choice. According to Google's documentation on its ad serving modes (https://developers.google.com/admob/ios/privacy/ad-serving-modes), in that mode no device identifiers or local storage are used for advertising purposes and the ad is not personalised; the IP address and technical data of the request (device type, app and system version, language) are still processed to deliver the ad, and Google uses them for technical purposes such as security and the detection of fraud and abuse. The legal basis for that case is in section 14. Removing the ads is what the subscription does (section 6). You can change your choice at any time in Preferences → "Ad privacy options" and in "About this ad".
- About this ad. Next to each ad there is a button that explains why you see it and lets you change your choice or report it. Reporting opens your email app (section 4).
- Who sees no ads. People under 16 and anyone with an active "No ads" subscription. If Parigo cannot confirm your subscription at that moment, it does not request ads either. Nor are there ads before the year-of-birth question has been answered, which is required because, without it, Parigo cannot know whether it should start third-party services.
- If this changes. Parigo requests non-personalised ads. If it ever requested personalised ones, we would say so here first and ask for your permission.
- More information. How Google handles data: https://policies.google.com/privacy
6. "No ads" subscription
- The subscription is optional, monthly or yearly, and you buy it with your Apple account. Apple charges and handles the payment: we receive neither your card nor your name. It removes ads and adds no features. If, because of your privacy choice, you already see fewer ads or limited ads, the subscription removes them all; it adds no features. It is only offered from age 16: it is not offered to under-16s, because they do not see advertising (in Preferences they are told "You do not see advertising in Parigo"). Prices and terms: in the terms of use.
- What RevenueCat processes. Only from age 16, Parigo uses RevenueCat to know whether the subscription is active and to restore it. RevenueCat receives a random identifier of the app, with no name or email, the subscription data and the purchase information (the receipt Apple provides and its dates) and technical connection data. In addition, the SDK transmits technical device and app data, including the IDFV and storefront country when available. It also reports the iOS tracking-permission status, although Parigo does not request that permission. Parigo adds no custom attributes or advertising identifiers. It does so also for people who never buy, because Parigo asks it whether you have the subscription. Parigo sends RevenueCat none of the content of your accounts, transactions or groups, and has the SDK's optional diagnostics switched off. Even though the identifier is random, it persists on your installation and RevenueCat links activity to it, so we treat this data as personal data. RevenueCat acts as a data processor on our behalf: its data processing agreement (https://www.revenuecat.com/dpa) forms part of the terms of service that we accepted when creating the account and provides for standard contractual clauses for transfers. According to its policy, it stores the data on servers in the United States (Amazon Web Services). The legal bases are in section 14 and the retention in section 12. Its policy: https://www.revenuecat.com/privacy/
- What we receive. We receive sales information from Apple and subscription data linked to RevenueCat's random identifier, and not to your name or email. RevenueCat also gives us aggregated analytics on purchases and subscriptions (for example, how many subscriptions are active or how many renew). The purpose is the operation of the subscription and analysis of how it is doing.
- No account is needed. The subscription is recovered with "Restore purchases" using your Apple account.
- Cancelling. In the subscription settings of your Apple account (from Parigo, with "Manage subscription"). It stays active until the end of the period already paid. When the paid period ends, free use continues; ads may be shown according to your age and your choice in the form. Apple's policy: https://www.apple.com/legal/privacy/
7. Bank statements
To import transactions, you download the statement from your bank's website or app and choose the file in Parigo. The file is read on your device; it is not sent anywhere. You review the transactions before saving them. Parigo does not connect to your bank, does not ask for your banking credentials and does not move money. From an import, Parigo keeps the transactions you confirm and an import record (identifiers, dates and amounts), not the original file: that stays where you downloaded it, and uninstalling Parigo does not delete it. Parigo tries to remove the temporary copy that the file picker creates when reading it. Imported transactions are not sent to any server or any SDK. They can leave the device only if you export a private backup (section 9) or copy them. Statements and imported transactions are not automatically incorporated into shared groups. If you classify a credit from a joint account as a refund of an expense related to a group, that expense is reduced or cancelled. That change is included in the group files you decide to share.
8. Exchange-rate lookups
- When: only when preparing or editing an expense or an income in a currency different from your account's or group's, if you have not typed the rate yourself. The lookup starts when the form is prepared, without waiting for you to save, and can happen even if you later cancel it. The first time, the app explains it and asks for your permission. You can turn it off in Preferences and type rates by hand. This lookup is available at any age.
- What is sent: the date of the expense and the currency codes. Amounts, descriptions, names and categories are never sent. The lookup adds no further identifiers of the user or the device; the provider receives the IP address needed for the connection.
To whom: free public services, over an encrypted connection (HTTPS):
- First Frankfurter (
api.frankfurter.dev), an open-source project that publishes the European Central Bank's reference rates and states on its website that it does not collect or log personal data, IP addresses or request URLs (read on 19-11-2026; its own statement, not independently verified). It does not say who operates it or in which country, nor what transfer safeguards it uses; it sits behind Cloudflare, which sees the IP as with any connection (https://frankfurter.dev/). - If it fails or lacks the currency, a set of public exchange-rate files served by jsDelivr (
cdn.jsdelivr.net), operated by Volentio JSD Limited (England and Wales). According to its policy, it logs the IP and the addresses visited, keeps non-aggregated data for a shorter period until it is analysed and deleted, keeps aggregated data without limit and cites no specific transfer safeguards (https://github.com/jsdelivr/jsdelivr/blob/master/Privacy%20Policy.md). - As a fallback,
currency-api.pages.dev, hosted on Cloudflare Pages by the author of the data set, who publishes no policy. Cloudflare states that it acts as a processor for its customers, with no fixed retention period for end-user data, and bases its transfers on the EU-US Data Privacy Framework (and its Swiss and UK extensions) and, as a fallback, on standard contractual clauses (https://www.cloudflare.com/privacypolicy/).
With jsDelivr and
currency-api.pages.devonly the date and the base currency are requested, and the rest is resolved on your device. These providers may process your IP outside the European Economic Area and we do not control how long they keep it.- First Frankfurter (
- What those services see: as with any connection, the IP address and technical details. We do not receive them.
- What Parigo does with the answer: it stores the applied rate, its date and its source with the expense on your device. These are daily reference rates, not your bank's, and you can correct them.
9. Passphrase protection and private backups
- Optional protection: you can protect what is stored with a passphrase of your choice. The passphrase is not stored anywhere. There is no passphrase recovery: if you forget it, nobody, including us, can open that data.
- Private backup: you can export a file with everything you have entered. It is encrypted by default with a passphrase you type at that moment; to open it on another device you need the file and its passphrase. You can choose to export it unencrypted, with a warning: in that case anyone with the file can read it.
- What you do with the file (keep it in a cloud service, send it by email or messaging) is subject to the terms of the service you choose. Parigo cannot delete or recover those files.
- Protection does not replace your device lock and does not protect what you have already exported unencrypted (CSV files, unencrypted copies, screenshots, clipboard).
10. Sharing groups
You can share a group with other people. In this version it is an exchange of files that you do by hand: you send them an invitation and, after that, the group's changes in encrypted files, through the channel you choose (messaging, email, AirDrop, etc.). There is no server and no automatic sync. To share, you first need to turn on passphrase protection. We do not receive those invitations or files and cannot read them.
- What the others see: everyone in a shared group sees the names of its participants, the expenses, the payments, the amounts, the dates and who made each change. They do not see your personal accounts or anything outside the group. Transactions you imported from a bank file are not automatically incorporated into a shared group (the exception for refunds is in section 7).
- The invitation contains the group's key. Anyone who has it can read that group's files: send it only to the people taking part, through a private channel.
- You choose the channel. The service you use to send the invitation or the files handles them under its own terms; the files are encrypted, the invitation is not.
- Removing someone changes the key for future changes, but does not delete what that person already has on their phone.
- If you enter other people's names in a group, make sure they agree.
11. What Parigo does not do
No user accounts. No server of our own where your data is kept. No usage analytics or crash reports of our own sent to anyone. No tracking permission. No sale of your data. No requests for personalised ads. No requests for access to the device's location, contacts, photos, microphone or camera. Apart from what is described in section 4, Parigo makes no other connections on its own.
On iOS, Parigo does not ask for permission for the camera, microphone, contacts, photos, location or tracking. To pick a file and to send one, it uses the operating system's own file picker and share menu: it only accesses the file you choose. When you tap "Paste", Parigo reads the clipboard text to put it in the field; iOS may notify you or ask for confirmation when it does. In addition, after copying something sensitive (such as an invitation) or after pasting it, Parigo may read the clipboard again only to check whether it is unchanged and clear it (when you leave the screen or after one minute). What Parigo reads from the clipboard does not leave the device.
12. Retention and deletion
Your data stays on your device for as long as you keep it there. You can delete it at any time by deleting the app. Exported copies you delete yourself wherever you stored them.
RevenueCat records (random identifier and subscription data), only if you are 16 or over:
- If you have never bought: the record is kept for as long as Parigo offers the subscription, because it is needed to check whether you have it each time you open the app. There is no automatic deletion for inactivity: we delete it when you ask us to (see below) and, in any case, if Parigo stops offering the subscription.
- If you have bought: for as long as the subscription lasts and, afterwards, for the period needed to meet legal obligations and handle claims. We keep the accounting and tax documentation of sales, which comes from Apple, for up to 6 years.
- If you ask for deletion: you can write to soporte@parigo.app to exercise your rights over this data. We will answer your request within one month. Where erasure applies, we will carry it out without undue delay. So that we can find your record in RevenueCat, include your support code in the email: it is in Preferences → About, with a button to copy it. It is RevenueCat's random identifier; it does not carry your name or your email.
- What you should know. Deleting the app does not delete the record RevenueCat holds about you. Deleting the record does not cancel your Apple subscription either: that is done in the subscription settings of your Apple account (section 6). And if you keep using Parigo after the deletion, the SDK creates a new anonymous record when it checks your subscription, as RevenueCat warns; if you do not want one to be created, uninstall Parigo.
Google. Google keeps ad and consent-form data under its own policies (https://policies.google.com/technologies/retention); Google states, in general terms, that it anonymises part of the IP address in advertising logs after 9 months and cookie information after 18 months. We do not receive that data.
Web pages. Visitor logs of the pages hosted on GitHub Pages are kept by GitHub under its own policies; its documentation does not state the period.
An email you sent us is kept for as long as the enquiry lasts and, after that, for at most twelve months, in case it has to be reopened or the reply evidenced; after that period we delete it, unless a law requires keeping it longer.
13. Children
Parigo may be used by minors.
Age question. The first time it opens, Parigo asks for your year of birth, and you must answer to continue: without that answer, Parigo cannot know whether it should start third-party advertising or purchase services, and until then it starts none. Only the year is stored, only on your device: it is sent to nobody and is not included in private backups or exports. It is your own declaration; Parigo does not check it. If you entered it wrongly, you can correct it later in Preferences → "Year of birth" → "Change", and Parigo applies what corresponds to the year stored. Parigo works out age from the year alone and cautiously, as if you had not yet had your birthday in the current year.
What changes with age:
- Under 16: Parigo shows no advertising and does not offer the subscription (in Preferences it says "You do not see advertising in Parigo"). It does not start any third-party advertising or purchase service: neither Google's consent form, nor AdMob, nor RevenueCat. All it can use over the network is the optional exchange-rate lookup (section 8, which asks for permission first and sends no data about you beyond the IP address that any connection involves) and opening the web pages of the policy, the terms and support.
- 16 and 17: RevenueCat at start-up, to know whether there is a subscription; Google's form where applicable; ads non-personalised, with Google's treatment for adolescents and with G-rated content. When requesting that treatment, Google receives an indication derived from your age (not the year).
- 18 or over: the same, but without the treatment for adolescents; in version 1.0.0, always non-personalised and with G-rated content.
- Not answered: no third-party advertising or purchase service is started and there is no advertising; the question is required to continue.
16 is chosen because it is the highest age of consent in the European Union; in Spain it is 14.
Parigo sets no minimum age of its own. In Spain, where processing is based on consent, children under 14 need the consent of whoever holds parental authority or guardianship. Other processing rests on the legal bases in section 14. The technical data processed by the purchase and advertising services is the data in section 4.
If you are a parent or guardian and believe a child uses Parigo, write to soporte@parigo.app. The subscription is only offered from age 16; it is bought by an adult, or by a 16 or 17-year-old with the authorisation of their parent or guardian, under the rules of the Apple account. "Ask to Buy" in Family Sharing is an example of an Apple purchase control: it is not the same as authorisation to process personal data and does not by itself check capacity to contract.
14. Your rights
We do not hold the data you store in Parigo, so we cannot give you access to it, correct it or erase it: you hold it and control it on your device. For the data we do process (your email address, if you write to us, and the data of your subscription and purchase that RevenueCat processes, also if you never bought, from age 16) you may exercise your rights of access, rectification, erasure, objection, restriction and portability by writing to soporte@parigo.app. We will answer your request within one month. Where erasure applies, we will carry it out without undue delay. For RevenueCat data, include your support code (section 12). If you made a choice in Google's consent form, you can change or withdraw it at any time (section 5). For the data Google processes in ads, you can also contact Google. If you believe your rights have not been respected, you may complain to the Spanish Data Protection Agency (www.aepd.es).
What we use data for and the legal basis (GDPR and Spanish LOPDGDD):
- Answering your email: legitimate interest in replying to you.
- Year of birth: we process it only on your device, to meet child-protection obligations and, where applicable, on the basis of a legitimate interest in protecting minors by deciding, according to age, which third-party services are started. We do not receive it.
- RevenueCat (from age 16): knowing at start-up whether an active subscription exists is necessary to decide whether ads are shown and to offer or restore the purchase; we also use the aggregated purchase and subscription analytics that RevenueCat gives us. The basis is legitimate interest, if you have never bought, and performance of a contract, if you buy. The balancing: we use a random identifier, with no name or email and no app content; you can ask us to delete your record at any time with your support code (section 12); it is not started for under-16s; and checking only when you tap "Buy" would not let us know in time that you already have the subscription so as not to show you ads. You can object by writing to soporte@parigo.app.
- Initial query to Google (form): legitimate interest in meeting the obligation to ask for your choice before requesting ads where it is required, and in not requesting them without it; it does not carry your year of birth.
Showing ads (from age 16). Depending on what you choose in Google's form:
- If you consent: the basis is your consent, for what the form describes. You can withdraw it at any time (section 5).
- If you choose "Do not consent" (or manage the options and decline): Google serves limited ads. According to Google's documentation on its ad serving modes (https://developers.google.com/admob/ios/privacy/ad-serving-modes), no device identifiers or local storage are used for advertising purposes and the ad is not personalised; the IP address and technical data of the request (device type, app and system version, language) are still processed to deliver the ad, and Google uses them for technical purposes such as security and the detection of fraud and abuse. Our purpose is to show a contextual ad that funds the free use of Parigo. The basis is the owner's legitimate interest in funding a free app with non-personalised, minimally intrusive advertising. The balancing: no profile, no advertising identifiers, no data from your accounts, only from age 16, G rating and sensitive categories blocked. You can object by writing to soporte@parigo.app; the way to see no ads at all is the "No ads" subscription (section 6).
- Where the form is not required: the owner's legitimate interest in funding Parigo with non-personalised ads, with the same balancing and the same right to object.
- Looking up exchange rates: legitimate interest in providing the optional feature you turn on, with the least possible information. The permission the app asks for before the first lookup informs you and lets you decide; we do not hand over data about you beyond the IP address the provider sees on any connection (section 8).
- Opening the web pages (policy, terms, support): legitimate interest in publishing them and keeping them secure; GitHub logs the IP of visitors for security purposes, according to its documentation.
Third parties. RevenueCat acts as a data processor on our behalf (section 6). Google acts as an independent controller of the data it processes to show ads, under its controller-to-controller data protection terms (https://business.safety.google/adscontrollerterms/); Parigo is not its processor, nor is Google ours. For the consent form, the Google documentation we have consulted does not expressly state whether it acts as controller or processor; what Parigo does is query it before requesting ads, and we refer you to Google's information (https://policies.google.com/privacy).
Transfers. The data processed by Google, RevenueCat and GitHub may leave the European Economic Area, in particular for the United States. Google bases transfers of data from its advertising services on the EU-US Data Privacy Framework and, where that does not apply, on standard contractual clauses (https://business.safety.google/adsdatatransfers/). For RevenueCat, its data processing agreement provides for standard contractual clauses (https://www.revenuecat.com/dpa). GitHub bases them on standard contractual clauses and on the EU-US Data Privacy Framework (https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement). For the exchange-rate services, section 8.
15. Changes to this policy
If Parigo changes what it does with your data, this page and its date will be updated before the change reaches the app.