tikiSTUDIOSTerms of Use →

Basso Privacy Policy

Last updated: November 15, 2026

About this policy

Tiki Studios ("Tiki Studios", "we", "us") is an independent mobile studio brand based in Türkiye. We make mobile apps and games, including Basso, Pipzi, PromptMaster, MaskedTalk, LiftAlong and Wickstart. This Privacy Policy covers all of them, and every app or game we release in the future.

The policy has two parts. The first part, below, applies to all of our products. The second part has one section per product, describing exactly what that product collects, why, and who processes it. If a product section and the general part differ, the product section is the more specific one and applies to that product.

Some products have extra pages that stay on their own websites. For MaskedTalk these are the Child Safety Standards and Account Deletion pages on maskedtalk.live.

Who is responsible

Tiki Studios is the data controller for the personal data described in this policy. For any privacy question or request, contact us at legal@tikistudios.io.

What we collect, in general

What we collect depends on the product. The product sections list the details. Across our products, the categories are:

  • Data you give us, such as an email address, username, profile details, messages, photos, reviews or journal entries, in products that have accounts or community features.
  • Data created on your device, such as progress, results, settings and preferences. In several products this data never leaves your device.
  • Usage and diagnostic data, such as which screens you open, feature events, crash reports and performance data, linked to a random app-instance or installation identifier.
  • Purchase data, such as which product you bought and your subscription status. Payments are processed by the app store. We never see your card details.
  • Device or installation identifiers, where described in a product section for functionality, subscriptions, usage or diagnostics.
  • Advertising identifiers, only in products that show ads or measure our own ad campaigns, and only as described in the product section and in the advertising section below.
  • Support correspondence, if you email us.

We do not collect precise location in any product. We do not sell personal data.

How and why we use data

We use personal data to:

  • Provide the product: run your account, sync your content, deliver messages and calls, and unlock what you paid for. The legal basis is performance of our contract with you.
  • Keep products safe: verify age limits, moderate content, prevent fraud and abuse, and respond to reports. The legal bases are our legitimate interests and, where it applies, legal obligations.
  • Understand and improve our products: usage analytics, crash reporting and performance monitoring. The legal basis is our legitimate interest in building reliable, useful products. Where a product lets you turn analytics off, the setting is described in its section.
  • Show ads in products that contain them. The legal basis is your consent where the law requires it, otherwise our legitimate interest.
  • Measure our own ad campaigns: learn which of our ads lead people to install a product, use it and subscribe, so we know where to advertise. This is not used to show you ads. The legal basis is your consent where the law requires it, otherwise our legitimate interest.
  • Answer you when you contact support.
  • Meet legal obligations, such as keeping purchase records or responding to lawful requests.

For users in Türkiye, these purposes and legal bases correspond to Article 5 of the Personal Data Protection Law No. 6698 (KVKK). For users in the European Economic Area, the United Kingdom and Switzerland, they correspond to Article 6 of the GDPR.

Service providers

We use service providers that process data on our behalf, under their own data-processing terms. Not every product uses every provider; each product section names the ones it uses.

  • Google Firebase (Google LLC / Google Ireland Ltd): analytics, crash reporting, performance monitoring, remote configuration, push notifications and, in some products, authentication.
  • Google AdMob (Google): advertising, in products that show ads.
  • RevenueCat, Inc.: subscription and purchase management.
  • Adjust GmbH (Berlin, Germany): measuring which of our ad campaigns lead to installs and subscriptions, in products whose section says so.
  • Apple, Google Play, Huawei AppGallery and Samsung Galaxy Store: app distribution and payment processing, under their own privacy policies.
  • Hetzner Online GmbH: server hosting for products that have a backend. Our servers are in the European Union (Finland).
  • Slack Technologies: the internal tool our moderation team uses to review safety reports, where a product section says so.

Advertising and tracking

Only products whose section says so show ads. In those products:

  • If you are in the EEA, the UK or Switzerland, or another region where consent is required, Google's consent form asks for your choices before any ad is requested. You can change your choices later in the app's settings.
  • On iOS, we ask for permission through App Tracking Transparency before using your device's advertising identifier. If you decline, ads are not personalized.
  • On Android, you can reset or delete your advertising ID, or opt out of personalized ads, in your device settings.

Paid plans that remove ads do not request ads.

Ad measurement. Some products, including products without ads, use Adjust to learn which of our own ads bring people to them. This measures our campaigns; it does not show you ads or target ads to you individually. Each product section says what is sent, when it starts and how to turn it off. In the EEA, the UK and Switzerland it starts only with your consent. On iOS, the advertising identifier is used for it only if you allow tracking.

International transfers

Some of our service providers, including Google and RevenueCat, process data in the United States and other countries. Where data leaves the EEA, the UK, Switzerland or Türkiye, the transfer relies on the safeguards the law provides, such as the European Commission's Standard Contractual Clauses and the providers' data-processing terms.

How long we keep data

  • On-device data stays on your device until you delete it in the app or delete the app. Your phone's own backups (iCloud or Google backup) may keep a copy under your control.
  • Account data is kept while your account exists and is deleted after you delete your account, as described in the product section.
  • Analytics data is kept for up to 14 months. Crash reports are kept for up to 90 days.
  • Purchase records are kept as long as needed to restore your purchases and to meet tax and accounting rules.
  • Support emails are kept only as long as needed to handle your request.

Product sections give specific retention periods where they differ.

Your rights

Depending on where you live, you can ask us to:

  • tell you whether we process your data and give you a copy;
  • correct inaccurate data;
  • delete your data;
  • restrict or object to certain processing, including processing based on legitimate interests;
  • give you your data in a portable format;
  • withdraw consent at any time, without affecting processing that already happened.

To use these rights, email legal@tikistudios.io. For products without accounts, we can only identify data linked to a random app identifier, so deleting the app or its data is often the most complete option. We may need to verify your request before acting on it. We respond within 30 days, or sooner where the law requires.

You can also complain to a data-protection authority. In Türkiye this is the Personal Data Protection Authority (KVKK Kurumu). In the EEA, it is the authority in the country where you live or work.

California and other US states. We do not sell personal information. We share it for cross-context behavioral advertising only through the ads in products that show ads, and through ad measurement, which reports campaign results to the ad networks we advertise with. You can control both as described above and in each product section. We do not use sensitive personal information to infer characteristics about you. You will not be treated differently for exercising your rights.

Children

Our products are not directed to children under 13. Some products have higher minimum ages: MaskedTalk is for adults 18 and over. Product sections state the minimum age and how it is checked.

If you are a parent or guardian and believe a child has given us personal data, contact legal@tikistudios.io and we will delete it.

Security

We protect data with encryption in transit (HTTPS/TLS), access controls on our servers, and the app sandboxing and storage encryption of your phone's operating system. Data kept only on your device is protected by your device lock. No system is perfectly secure, so we also try to collect as little as we can.

Our website

tikistudios.io does not use cookies, analytics or advertising. Fonts are served from our own server; no third party receives your IP address to deliver them. Links to app stores and other websites are governed by those sites' own policies.

Changes to this policy

When we change this policy, we post the new version here and update the date at the top. If a change is significant, we tell you in the affected product or on this page before it takes effect.

Contact

Tiki Studios, Türkiye · Email: legal@tikistudios.io

Basso

Basso is a voice-training app. This section applies to every version of Basso: App Store, Google Play, Samsung Galaxy Store and Huawei AppGallery.

Basso is published by Şinasi Demirel under the Tiki Studios name. For Basso, the data controller is Şinasi Demirel (Tiki Studios), the individual publisher. You can reach us at support@tikistudios.io.

The short version

  • Basso never uploads your voice or recordings. Microphone audio is analyzed on your phone in real time and is never uploaded to us or anyone else. Optional recordings stay on your device, and your phone's own backup may include them.
  • No account in the App Store, Google Play and Galaxy Store versions; subscriptions there use RevenueCat's anonymous app-user ID. The Huawei version uses HUAWEI ID sign-in and a pseudonymous billing account, described below. Basso never receives your Huawei password and does not ask for your email, name or profile photo.
  • Your detailed training records stay on your device. Selected numeric pitch measurements and usage events are sent to Firebase Analytics, as described below.
  • No ads in the app; ad measurement you control. Basso shows no advertising. To learn which of our own ads bring people to Basso, the App Store and Google Play versions use Adjust, and on iPhone and iPad Apple Ads attribution. In the EEA, the UK and Switzerland this needs your consent; everywhere you can turn it off in Settings → Ad measurement. It never happens for users under 18.
  • Analytics is switched off for users under 18. Until the birth-year screen, the first onboarding events are held in memory and discarded for anyone under 18.

Data kept only on your device

These records are stored on your device, in a local database or as temporary files. They are not sent to our Huawei billing server. Selected numbers and usage events go to Firebase Analytics as described in the next part.

  • Voice audio. Voice tests and exercises stream microphone audio straight into Basso's on-device pitch analysis. The audio is discarded as it is analyzed. Two optional features keep audio, which Basso keeps on your device and never uploads. Record & compare saves one temporary recording (a WAV file of up to about 10 seconds) so you can play your take back against the coach's, deleted automatically when you close the feature. The Voice Time Capsule, if you choose to keep recordings, saves the passage you read in your first voice test and in each weekly voice test so you can hear your progress later. You can delete all capsule recordings at any time, with or without a subscription, in Settings → Delete voice recordings; this also stops new ones being saved.
  • Voice measurements: median pitch and pitch percentiles in hertz, pitch stability, lowest comfortable pitch, voiced ratio, ambient noise level, a measurement-quality flag, your device model and the local hour of the test.
  • Profile and settings: your birth year (used only for the under-18 protections described below), whether you are under 18, your goal, daily practice time, language and reminder times.
  • Training progress: your program, completed sessions and exercises, settings, and a local copy of your subscription status.
  • Speak Check: texts you write to practice reading aloud, and the summary of each take (share of speaking time in your target pitch zone, median pitch, duration). They are never uploaded and never included in analytics.
  • Favorites: exercises you star in the library.
  • Voice Match: your take is analyzed while you read and is not kept. Only its scores (melody, pace, overall) and the line it was for are stored. The reference lines come with the app.
  • Challenges and goals: the start date of the 30-Day Voice Challenge or the number of days you chose for a monthly goal. Your progress is worked out on the device from your completed sessions.

Reminders are scheduled by your phone's operating system; no server is involved. Share cards, including "Your year in voice", are created on your device and leave it only through the app you choose to share to.

Your phone's operating system may back up eligible app data, files (including Voice Time Capsule recordings) and preferences, or move them to a new device, under your backup settings. We do not store these copies. Clearing Basso's storage or uninstalling it does not necessarily remove an existing backup; manage those copies with your backup provider.

Data that leaves your device

Firebase Analytics (Google). Basso records usage events:

  • app opens;
  • onboarding start, each onboarding screen you reach (a fixed step name), the time you spend on it and whether you go on, skip it or go back, your goal and daily practice-time choice, age confirmation, and finishing onboarding;
  • your onboarding answers: "That's me" or "Not me" for each of four fixed quick-check statements (for example whether your voice gets quieter in meetings), and "Sounds right" or "Not sure" for each of the three results shown after the voice test (your pitch, how much it moves and your starting lion stage). They are sent as fixed identifiers with yes/no values, never as text. The same fixed answers, and whether you allowed the microphone, are also attached to the event for the screen you leave;
  • the first-day tour of the Today screen: when it starts, which step you see, and whether you finish or skip it (and at which step);
  • microphone-permission result and whether the ambient-noise check passed before a test;
  • voice-test completions with a measurement-quality flag, and skipping the low-range test;
  • viewing your result and your plan, and which training track you were assigned (track name and the version of the configuration that chose it);
  • weekly re-tests, paywall views, trial starts, purchases (product identifier only) and restores;
  • session starts and completions (session identifier and duration) and completed exercise blocks;
  • sharing, notification opens, settings changes, and whether the notice suggesting a speech-language pathologist was shown to you.

Voice-test and re-test events include pitch values in hertz (median and low-range pitch, and the change from your baseline). Events never contain audio, free text, names or contact details. They are linked to a random Firebase app-instance ID, together with device model, OS version, app version and approximate location derived from your IP address (such as country, region or city). No GPS permission is used.

If your birth year shows you are under 18, Basso does not collect analytics. Before you enter your birth year, the events from the first onboarding screens are held only in the app's memory. They are sent once you confirm an adult birth year, and discarded if you are under 18 or close the app first. App opens and Firebase's own automatic events (such as the first-open event) are not held back.

Firebase Crashlytics (Google). If Basso crashes, a crash report is sent with the technical details of the crash (the stack trace and the device state at the time), your device model, OS and app version, linked to a Crashlytics installation ID. Crash reporting is off in debug builds.

RevenueCat. In the App Store, Google Play and Galaxy Store versions, RevenueCat manages your subscription under an anonymous app-user ID that RevenueCat generates. Basso never signs you in to RevenueCat, and we do not link this ID to your identity. The store processes the payment; we never see your card details or your store-account identity. Once you confirm an adult birth year, RevenueCat also:

  • sends subscription events (free trial started, purchase or renewal, cancellation or its reversal, expiry, billing problem, plan change) to Firebase Analytics, linked to the same random Firebase app-instance ID, so we can see whether people who finish onboarding go on to subscribe;
  • records each time one of Basso's purchase screens is shown.

Neither happens for users under 18.

Manage subscription. With an App Store or Google Play subscription, Settings → Manage subscription opens a screen provided by RevenueCat. There you can restore purchases and cancel through your store, and on iPhone and iPad also ask Apple for a refund or change plans. If you cancel there, it may ask why, with a choice from a short list; RevenueCat stores your choice with the anonymous app-user ID.

Apple Ads attribution (iPhone and iPad only). After you confirm an adult birth year, Basso asks Apple's AdServices framework for an attribution token and passes it to RevenueCat. RevenueCat exchanges it with Apple, and Apple says whether the install came from an Apple Ads campaign. If it did, Apple also returns the campaign, ad group, keyword and ad identifiers and the country or region. RevenueCat keeps this with the anonymous app-user ID, so we can see which of our own Apple Ads campaigns lead to trials and subscriptions. This attribution uses no advertising identifier, is not combined with data from other companies' apps or websites, and does not depend on Apple's tracking prompt. The Android and Huawei versions do not do this, and it never happens for users under 18.

Ad measurement (Adjust). The App Store and Google Play versions use Adjust (Adjust GmbH, Berlin, Germany) to measure which of our ads lead people to install Basso, use it and start a trial or subscription. Adjust is not used in the Galaxy Store and Huawei versions, on our own test devices, or for users under 18, including anyone who entered an under-18 birth year during the current app session.

  • What Adjust receives from the app: an Adjust device identifier; on Android, the Google Advertising ID (unless you have deleted or limited it in your device settings) and the Google Play install referrer; on iPhone and iPad, the identifier for vendors and, only if you allow tracking in Apple's tracking prompt, the identifier for advertisers (IDFA); Apple's SKAdNetwork and AdAttributionKit postbacks; your IP address, device model, OS and app version, and install and app-open times. It also receives these moments: onboarding finished (with its number of steps and duration), your first voice test finished (that it happened, without any result), a purchase screen shown (which one, and where it was opened from), a free trial started and a paid purchase completed (with the product, without the price), a training session finished (with its identifier and duration), your first finished session, and a weekly voice check-up finished.
  • What RevenueCat sends Adjust: your subscription events (purchase, free trial started, trial converted, trial cancelled, renewal, cancellation, expiry and plan change) with the product, currency and revenue after store commission and estimated taxes, linked to the Adjust device identifier. To do this, Basso gives RevenueCat the Adjust device identifier and the device identifiers above (the IDFA only after you allow tracking), stored with the anonymous app-user ID; when Adjust attributes your install to an ad, Basso also gives RevenueCat the names of that ad network, campaign, ad group and creative. A refund reaches Adjust only as a cancellation, without an amount.
  • Never sent to Adjust: audio, pitch or other voice measurements, training records, your birth year, names or contact details.
  • What it is for: linking an install, and what follows it, to the ad campaign that led to it, and reporting those results to the ad networks we advertise with (Meta, Google, TikTok and Apple) so they can measure and improve our campaigns. We do not sell your data.
  • Your choice: in the EEA, the UK and Switzerland, Adjust starts only if you allow it right after you enter your birth year: on Android when Basso asks, and on iPhone and iPad by allowing tracking in Apple's prompt. Your choice is passed to Google as its consent signals. Elsewhere it starts after you confirm an adult birth year. Everywhere you can turn it off at any time in Settings → Ad measurement, which also withdraws your consent. On iPhone and iPad you can also refuse or withdraw tracking in Apple's prompt or in iOS settings. Adjust's privacy policy: https://www.adjust.com/terms/privacy-policy/.

Apple refund requests. If you ask Apple for a refund of a Basso subscription, Apple may ask us for information about the purchase. RevenueCat answers for us: whether the subscription was delivered, whether a free trial was offered, and that you agreed to this in our Terms. It sends no usage data. We do not ask Apple to refuse your refund; Apple makes the decision.

Google Play chargebacks. If you dispute a Google Play charge for Basso with your bank or card issuer, Google may ask us about the purchase. RevenueCat answers for us that a free trial was offered and that we have no preference about the outcome. It sends no usage or account data; Google makes the decision.

Huawei version only. Huawei In-App Purchases has no subscription-management service we can use from the app, so the Huawei version uses our own billing server instead of RevenueCat:

  • When you buy or restore a subscription, Basso uses HUAWEI ID to sign you in. Huawei gives the app a single-use authorization code with the identity permissions needed to prove you own the subscription. Our server redeems it with Huawei and turns your app-specific HUAWEI ID OpenID into a pseudonymous Basso billing ID: a one-way hash of Basso's app ID and that OpenID. The server does not keep the raw OpenID or Huawei's access and refresh tokens. We never receive your name, email or phone number.
  • The server issues its own short-lived session for that pseudonymous ID. No Firebase Authentication account is created, and the app does not contact Google sign-in. A pseudonymous ownership hint on your device is used only to clear stale access after you switch accounts; it does not grant access.
  • The server stores that pseudonymous ID, purchase-intent identifiers with their product and times, subscription identifiers and purchase tokens, the product, payment environment, subscription status, expiry and verification times. Signed receipts, price and currency are processed to validate a purchase, but the complete signed receipts are not kept. We use these records to verify that you own the subscription and that it is paid, to restore interrupted purchases, and to stop receipts being replayed or moved between accounts.
  • To prevent reuse and abuse, the server also keeps hashed authorization-code identifiers and IP-address or rate-limit identifiers. The hosting may process request metadata and operational logs. Huawei purchase notifications only update subscription records that were already verified; an unsigned notification cannot grant access.
  • Voice audio, your birth year and your training progress are never sent to this server.
  • The server runs on Hetzner in Helsinki, Finland. Its records are stored in Google Firebase Firestore in Frankfurt, Germany. Google decides where else it processes data under its own Firebase terms, so the Frankfurt location does not mean Analytics data stays in Frankfurt.
  • Huawei processes the payment; Basso never receives card or bank details.
  • You can delete this account in the app under Settings → Delete Basso billing account. See Delete your Basso billing account for what is deleted and what is kept.

We do not sell personal data, and we do not share Basso data with anyone other than the providers named in this section.

Problem reports. If you tap Report a problem, Basso opens an email to support@tikistudios.io in your own mail app. The email is prefilled with diagnostics: app version and build, store and flavor, OS version, device manufacturer and model, language, the time in UTC, your subscription status and expiry as stored on the device, and your training position (program and track, current session and week, the Home card shown, your last completed session and its time, completed-session count and streak). In the App Store, Google Play and Galaxy Store versions it also includes the RevenueCat app-user ID; in the Huawei version it includes the pseudonymous Basso billing ID when you are signed in, and RevenueCat is not contacted. You can read and edit it before sending. If no mail app can open it, Basso copies the report to your clipboard and shows the support address. Nothing is sent unless you send it. When you do, your mail provider and our support mailbox process your address, your message and the diagnostics to help you. The diagnostics never include card details, passwords, payment PINs, purchase tokens, signed receipts or voice recordings. Anything else you add is part of your message.

What Basso does not collect

  • Your voice audio: it is processed on your device and never uploaded.
  • Names, contact details or passwords: the app never asks for them. The Huawei version processes the pseudonymous identity described above. If you email us, we receive your email address and your message.
  • Cross-app tracking without your permission: Basso has no ad networks in the app. Advertising identifiers are used only for the Adjust ad measurement above: the Google Advertising ID on Android, and the IDFA on iPhone and iPad only if you allow tracking. The only other ad-related data is the Apple Ads attribution record.
  • Precise location, contacts, photos or other device data beyond what this section describes.

How Basso uses data

We use the data above to run and improve Basso: to see which features are used and how people progress through the programs, to fix crashes, to manage subscriptions, and to measure which of our own ad campaigns lead to installs and subscriptions. We do not show ads in Basso, we do not build profiles of you, and we do not target ads to you individually. Ad networks receive campaign results only so they can measure and improve our own campaigns.

Where Basso data is processed

Google Firebase, Hetzner, RevenueCat, Adjust and Huawei each process the Basso data described above. Their infrastructure may process data outside your country, including in Europe, the United States and other locations, under their own terms. The regions chosen for the Huawei billing server and its database do not decide where every provider processes data. Their privacy information:

Microphone

Basso asks for microphone access only to analyze your voice on your device. You can turn the permission off in your phone's settings. Voice tests and exercises then stop working, but the rest of the app keeps working.

Age

Basso is for people aged 13 and over. During onboarding Basso asks for your birth year. The birth year, and whether you are under 18, are stored only on your device. Users under 18 get no analytics collection, none of RevenueCat's analytics links (subscription events, purchase-screen views and Apple Ads attribution) and no ad measurement.

If you are a parent or guardian and believe a child under 13 is using Basso, contact support@tikistudios.io.

How long Basso keeps data

These periods apply to Basso instead of the general ones above.

  • On-device data (voice measurements, profile, progress, settings) stays in the app's storage until you clear it or uninstall Basso. Phone backups are kept separately and are managed through your backup provider.
  • Temporary files (the Record & compare recording and share-card images) are deleted automatically by the app or the operating system.
  • Analytics and crash data are kept under our Firebase project settings and Google's processing terms. Crashlytics keeps crash reports for 90 days before deleting them. See https://firebase.google.com/support/privacy.
  • App Store, Google Play and Galaxy Store purchase records are kept by RevenueCat under the anonymous app-user ID to manage and restore your subscription. On iPhone and iPad the Apple Ads attribution record is kept with them, as is any answer you give to the cancellation question in Manage subscription.
  • Huawei billing account: when you delete it, the server removes your purchase intents and the stored payment tokens, status and expiry, and the app ends its session. Automatic billing sign-in stays off afterwards, even after reinstalling. To stop another account from claiming your old purchase, and to let you restore it yourself later, the server keeps minimal hashed proofs that you own the subscription and the purchase intent, and a deletion marker. A purchase-intent proof holds only the pseudonymous owner, the product, its issue time and the linked subscription hash; no payment token or original intent ID is kept. Signing in, buying or restoring again can create a new Basso billing account. Your HUAWEI ID and Huawei's own store records are controlled by Huawei; deleting the Basso billing account does not delete them or cancel your subscription.
  • Huawei anti-abuse records: authorization-code markers expire after 10 minutes and rate-limit counters after 2 days. Expired records can stay until maintenance removes them, because automatic periodic cleanup is currently off. Application logs rotate within three 1 MB files per container, so how long they last depends on how much is logged. Proxy access logging is off. The billing server has no configured volume backups, Firestore backup schedules or point-in-time recovery. None of this changes Google's own processing and deletion periods.
  • Ad measurement data is kept by Adjust under its data-processing terms with us.
  • Support emails are kept only as long as needed to handle your request.

Deleting your data

  • On your device: clear Basso's storage or delete the app. To delete only the Voice Time Capsule recordings, use Settings → Delete voice recordings. Your phone's backups may keep a copy until those backups are deleted.
  • Analytics, crash and purchase records: email support@tikistudios.io. We delete what we can link to your app-instance ID or purchase ID.
  • Ad measurement data: turning off Settings → Ad measurement stops further collection. To have the existing Adjust record deleted, email support@tikistudios.io.
  • Huawei billing account: use Settings → Delete Basso billing account in the app. The steps, and what is kept, are on Delete your Basso billing account.

Your rights in Basso

You have the rights described in the general part of this policy. For Basso: for on-device data, delete the app or its data; for the Huawei billing account, use the signed-in deletion in Settings; for other provider records, or for access and correction requests, email support@tikistudios.io. We must check that the request is about your own record. Deleting a billing account does not cancel the subscription at the store. You can also complain to your local data-protection authority.

Security in Basso

Voice audio is processed on your device. Detailed training records stay in the app's private storage, protected by your phone's app sandboxing and encryption. The analytics events and subscription records that leave your device are protected by Google, Hetzner, RevenueCat, Adjust and Huawei under their security and data-processing terms. No method of sending or storing data is completely secure.