Privacy Policy

1Who Is Responsible for Your Data

Family Agreements is developed and operated by SIA "Valmsoft", a company registered in Latvia under number 40203790753. The company decides why and how the app, its servers and this website process the data described in this policy, which makes it the controller of that data. In this policy it is called "the developer" or "we".

Where providers process data under their own privacy policies, they are responsible for that processing themselves. The company's registered address and other details are in the Contact section.

2Information We Collect

Below is what information Family Agreements collects and what it is needed for.

Adult account information:

• Email address. If you use Sign in with Apple, this may be a hidden address issued by Apple, if you chose not to share your own
• The name other family members see you under. When the account is created, it is the name Google or Apple passed on, if you sign in with them; otherwise, the part of the email address before the @ sign
• Your Google or Apple account identifier, if you sign in with them
• Sign-in tokens, so you don't have to sign in again
• The date and time of your last sign-in or session renewal. The server updates it at most once a day, and the retention period for inactive accounts and families is counted from it (see "Data Retention")

The email address is needed to sign in, for emails about your account and family — a sign-in code, an invitation, a welcome message, a warning before an inactive family is deleted — and to manage the account; its domain also goes into the internal product report (see "How Information Is Used"). Other adults in your family can see the address.

If you invite another adult to the family, their email address is stored in the invitation, and an email with a code is sent to that address. The invitation itself is valid for 10 minutes and is then deleted; the address stays in the family history as a record of who was invited.

Child profiles:

• Display name chosen by the parent or child
• Internal identifier (UUID)
• Membership within a family group
• Date and time of the last sign-in or session renewal

A child has no email address and no password: they sign in by scanning a QR code shown by an adult.

Device data — for adults and children alike:

• The identifier of the device a session is tied to. It is a random code the application creates itself; on iPhone it is kept in the keychain and is not lost when the application is reinstalled
• The push notification token and the device platform (Android or iOS): the server uses them to send notifications about what happens in the family

Family Pro subscription:

• The plan, the store (Google Play or the App Store), the expiry date and whether it renews automatically
• The purchase identifier in the store: the server uses it to check the subscription with Google or Apple
• Which adult in the family took out the subscription

The application never receives payment details such as a card number or a billing address: only the store sees them.

Beyond that, the application collects information about how it is used, along with crash diagnostics: without it there is no way to see where the application breaks and which step people get stuck on. It is collected by Firebase Analytics and Firebase Crashlytics, both Google services. This data contains no names and none of the text you type in, but it cannot be called fully anonymous either — the complete list is below.

What this includes:

• Actions: which screen was opened and closed, choosing a role, signing in, creating a family, invitations and QR code scanning, creating, editing, completing and reviewing tasks, showing the Family Pro screen and the steps of a purchase, the first-run walkthrough, the request to rate the application, and switching the collection on and off
• Attributes: the role (adult or child), the plan (free or Family Pro), whether a family exists, which step of the initial setup you are on, and how you signed in (an emailed code, Google or Apple); whether the application runs in an emulator or in an automated Google Play check
• App Store purchases: on iPhone, Google Analytics itself records subscription purchases and renewals, with the plan, price and currency
• Standard events Google Analytics collects automatically — for example, the first launch, sessions and time spent in the application, application and system updates
• Error codes, server response statuses and the addresses of failed requests, with the identifiers stripped out
• Crash reports: the place in the code, the screen, the application version, the device model, the Android or iOS version, the role, the plan, and a request code. With that code, the crash can be found in the server log, where the family identifier is recorded next to it — so a crash report can be matched to a family. The fact that a crash happened, and when, also goes into the usage statistics
• The device language, the approximate location (the country and city Google derives from the IP address), and a random installation identifier — it changes when the application is reinstalled

What it does not include:

• Names, email addresses or any contact details
• Task and reward titles, or any other text you type in
• Account, family or profile identifiers
• The device advertising identifier, the Android ID, or the identifier for vendor on iPhone (IDFV)

The collection is on by default. It is switched off with the statistics switch in the application settings, which adults and children both have. The choice is stored on the device itself and applies only where it was made: on a child's phone, the collection has to be switched off separately. After the application is reinstalled, the collection is on again.

One last event goes out before the collection stops — the fact that it was switched off. After that the application sends neither statistics nor crash reports, and whatever has not yet left the device is deleted. Data Google has already received stays with Google until its retention period runs out.

3Family Data

The application may store information related to family activity, including:

• Household tasks
• Task completion status
• Comments an adult adds when sending a task back or deciding on a reward request
• Reward catalog entries
• Reward requests
• Family goals and contributions to them
• Points balances
• Points history
• The family history: who did what, and when

This information is needed for the application to work; in addition, how much of it there is and the days the family was active go into the internal product report.

4Camera Permission

Family Agreements may request access to the device camera.

The camera is used only to scan QR codes shown by an adult: when a child joins a family, re-authenticates a device, or confirms the deletion of their profile. The QR code is recognized on the device itself.

What the application does not do:

• Does not record video
• Does not save images
• Does not send camera content to servers

The camera turns on only when the person holding the phone chooses to scan a QR code themselves.

5How Information Is Used

Information collected by the application is used only to:

• Check who signs in
• Manage family membership
• Keep track of task completion
• Keep point balances
• Process reward requests
• Display activity history
• Send push notifications about what happens in the family
• Check the Family Pro subscription with the store
• Delete accounts and families that no one has used for a long time
• Compile an internal report on how the product is used
• Find failures and improve the application

The application does not sell personal data.

From the server database the developer compiles an internal report on how the product is used: sign-ups and sign-ins, the days a family was active, the number of tasks, rewards and goals, and email address domains; a summary from Google Analytics is added to it. The report is computed per account and per family, but it contains no addresses and no names — only internal family identifiers, dates, plans, domains, numbers and yes/no attributes.

The developer reads the statistics and the report to find failures and the places where people give up on the application — not to watch a particular person or family.

6Data Storage

Application data may be stored on secure servers operated by the developer.

Stored data may include:

• Account and device identifiers
• Family data
• Tasks and rewards
• Points history
• Subscription details

The application server also keeps a request log: every request in it has a request code, the request URL contains the family identifier, and some lines also carry user and device identifiers. The developer uses this log to investigate failures, including by matching crash reports against it.

Reasonable security measures are used to protect stored information.

7Data Sharing

Family Agreements does not sell personal data and does not share it with third parties, apart from the service providers that work for the service:

• Secure hosting providers
• Cloudflare — delivering and protecting the website, and aggregate visit statistics for the developer (see This Website)
• Resend — sending emails: the sign-in code, the family invitation, the welcome message, the warning before a family is deleted
• Google and Apple — signing in with their accounts, and checking purchases made on Google Play and the App Store
• Google Firebase Cloud Messaging and the Apple Push Notification service — delivering push notifications
• Google Firebase — usage statistics (Firebase Analytics) and crash reports (Firebase Crashlytics)

Usage statistics and crash reports are processed by Google as a service provider and under its own privacy policy. They are stored on Google servers, including outside the country you live in.

When you sign in with Google or Apple, they confirm who you are and pass the application your email address, account identifier and name; Google also receives the device's IP address, among other things for fraud prevention. The server checks a subscription with the store by sending it only the purchase identifier.

The server sends push notifications without any text: they carry only the kind of notification and internal identifiers, and the application fills in the text itself. To make notifications work, the application registers the device with Firebase at launch — even before sign-in and without permission to show notifications; Firebase receives the device model, language and time zone, regardless of the statistics switch.

The application does not use advertising networks and does not track users for advertising purposes — neither across other apps nor across websites.

The device advertising identifier is not collected. On Android, the permissions the Google library adds by default have been removed from the application, and the sending of advertising and personalization signals is switched off; on iPhone, the application does not ask for access to the advertising identifier, and the collection of the identifier for vendor (IDFV) is switched off.

8Children's Privacy

Family Agreements is designed to be used within families under the supervision of parents or guardians.

What the server stores about a child:

• A display name, an internal profile identifier and membership in the family
• The session on their device: the device identifier, a sign-in token, a push notification token and the device platform
• Their activity in the application within the family
• The date and time of their last sign-in or session renewal, which the server updates at most once a day

A child has no email address and no password: they sign in by scanning a QR code shown by an adult. The application does not collect external contact information for children. Parents control the creation and management of child profiles.

A child's phone sends the same usage statistics and crash reports as an adult's: actions and crash diagnostics. The profile name and the titles of tasks and rewards do not go into them.

Children are shown no advertising, the device advertising identifier is not collected and no advertising profiles are built.

On a child's phone the collection is also on by default, and it is switched off with the same switch in the settings. The switch applies to one device: to stop the collection from a child's phone, switch it off on that phone.

9Data Retention

Account and family data is kept on the server for as long as it is in use. If no one uses the application for a long time, the server deletes it on its own. Using here means signing in or having the session renewed, which the application does by itself while it is being used. The count starts from the last day the application was used this way, and each new day of use starts it over.

When data is deleted:

• An account that does not belong to any family: after 30 days in which its owner has not used the application
• An empty family (no children, no completed tasks, never subscribed, and nothing created in it except invitations): after 60 days in which none of its members has used the application. The members' accounts are deleted along with the family
• Any other family: after 12 months in which none of its members has used the application. The members' accounts are deleted along with the family. The family's active parents are sent an email from support@family-agreements.app about 30 days and again about 7 days before the deletion; if any member uses the application, the deletion is canceled
• While a family has an active Family Pro subscription, it is not deleted: the 12 months start no earlier than the day the subscription ends. A family that has Family Pro access granted by the developer is not deleted either
• While any member of a family also belongs to another family, the server does not delete that family on its own: that member's account would have to be deleted with it

Each email names the deletion date: the first is sent about 30 days before it, the second about 7 days before. The deletion date can only move later, never earlier: if an email goes out late, the date moves with it. The family is deleted no earlier than the date named in the emails, only once both emails have been sent, and not before the seventh day after the second one.

If an email cannot be delivered, because the account has no usable email address or the mail service rejects the address, the deletion still goes ahead on the same schedule, as if the email had been sent. Any deletion may also happen later than described here, sometimes considerably later: the server deletes data once a day, not all at once, and may hold a deletion back for its own checks.

Deletion cannot be undone. The same data is deleted as when a person deletes their own account; see "Account Deletion". Copies in database backups disappear when the backups' retention period runs out.

Usage statistics and crash reports are stored separately from the family account: Google keeps them until the retention period set for the Firebase project runs out.

The application server's request log is also stored separately from the account: its entries are removed when the log's retention period runs out, not together with the account.

The developer keeps snapshots of the internal product report, and they are not deleted together with the account. They contain no names and no email addresses, but next to a family's internal identifier they hold the email domains of its adults, the plan and subscription status, dates and numbers.

10Account Deletion

On iPhone the account is deleted in the application itself, with the "Delete account" item in the settings. Deletion is confirmed the same way you sign in — with an emailed code, with Google or with Apple. A child deletes their own profile in the same place, with "Delete my profile", confirmed by a QR code shown by an adult.

There is no deletion inside the application on Android: there, as from any other device, you may request deletion of your account and associated data by contacting the developer at support@family-agreements.app from the address the account is registered to. An account with a hidden Apple address is deleted in the application on iPhone. After verification, account data will be removed from the system.

If no other active parent remains in the family, the whole family is deleted together with the account: the children's profiles, tasks, rewards, goals, points and history. If there are other active parents, your account and personal data are deleted — the email address, the name, the link to Google or Apple, sessions and push notification tokens — while what was created for the family stays with it: tasks, rewards, goals and comments, and your actions remain in the family history without a name. When a child's profile is deleted, their task completions, points and reward requests are erased, and their contributions to a family goal remain without a name. If you were invited to another family but never joined it, the invitation record with your address stays in that family's history.

If you sign in with Apple and confirm the deletion with Apple, the server also revokes the sign-in tokens Apple issued to the application.

Usage statistics and crash reports are not deleted together with the account: Google keeps them separately from the account, and they disappear on their own once the retention period runs out. To stop new ones from being sent, switch the collection off in the application settings.

11Security

The developer takes reasonable measures to protect user information, including:

• Secure authentication
• Encrypted network communication
• Server-side authorization controls

However, no system can guarantee absolute security.

12This Website

This website, family-agreements.app, sets no cookies, shows no ads and uses no analytics or visitor tracking. Its pages contain no executable scripts, and your browser loads everything from the site's own address only.

The website runs through the Cloudflare network: Cloudflare receives the browser's request and passes it on to the developer's server. To deliver the page, protect the site from attacks and show the developer aggregate visit statistics, Cloudflare processes the request data, including the IP address, as a service provider, under its own privacy policy, including outside the country you live in. If a request looks like an attack, Cloudflare may show its own check instead of the page; that check runs a Cloudflare script and sets a technical cookie.

The website's server keeps an access log: the time of the request, the address of the requested page or file, the response code and size, and other technical details of the response and the connection. Once the log filter is enabled, the visitor's IP address is not written to new entries, and neither is the information the browser sends along with the request: the browser and system name and version, the language, the address of the page the visitor came from, cookies. The log is used to investigate failures, attacks and abuse and to protect the website. Its size is limited: when the log file reaches a set size, a new one is started and the oldest files are deleted.

Caddy also records operational errors in the server system journal. If request handling fails, for example when the error page itself is unavailable, these records may contain the IP address and request headers, including browser and language information, the referring page address and the IP address forwarded by Cloudflare. These records are used to investigate failures, attacks and abuse and to protect the website. The access-log filter and size limits do not apply to them; retention and deletion are governed by the system journal settings.

Access-log entries created before the filter is enabled may contain IP addresses and request headers. Updating the configuration does not delete them: the current file and archives are retained for the same purposes and deleted according to the log rotation rules. So the fact that new entries contain no IP addresses does not mean that stored logs contain none.

13Changes to This Policy

This Privacy Policy may be updated from time to time.

If significant changes occur, the updated policy will be published at the same URL: family-agreements.app/privacy-policy.

14Contact

If you have any questions about this Privacy Policy, contact:

• Developer: SIA "Valmsoft"
• Registration No.: 40203790753
• VAT No.: LV40203790753
• Registered address: Paula Lejiņa iela 6-108, Rīga, LV-1029, Latvia
• Email: contacts@family-agreements.app
• Website: family-agreements.app