ARRVD Privacy Policy
Know they arrived. Not everywhere they went. This policy explains what information ARRVD uses to confirm arrivals, and what it doesn’t.
1. About this policy
This Privacy Policy applies to ARRVD, the family arrival app for iOS, and the services that support it (together, “ARRVD”). ARRVD is provided by futodama (“we”, “us”). The futodama privacy page covers this website in general; this page is the policy for ARRVD.
ARRVD is designed to confirm that a family member arrived at a place your family has set up. It is not a live-location or tracking service: it does not show anyone’s position on a map or keep a history of where they went. It does, however, use location information to detect arrivals, and this policy describes exactly how.
Questions: futodama0610@gmail.com
2. Information ARRVD processes
Account information
You sign in with Sign in with Apple, through Firebase Authentication. We receive an identifier for your Apple account, and Firebase assigns your ARRVD account an internal user ID. ARRVD does not ask Apple for your name or email address.
Family and membership information
- The family’s name, chosen by the person who creates the family (the Organizer).
- Each person’s role in the family (Organizer or Member), membership status, the date they joined, and their internal user ID.
- Which family your account belongs to.
Display names
A Member can set the name the family sees for them, and an Organizer can set or change a Member’s name. If no name is set, ARRVD shows a default label such as “Member 2”. Display names are only used to show who is who inside the family.
Invitations
When an Organizer invites someone, we create an invitation record containing the family’s name, the invited role, who created it, when it expires, its status and — once accepted — who accepted it. The invitation link contains a secret code; we store only a one-way (hashed) version of that code, never the code itself. If the Organizer enters a name for the person they invite, it is stored with the invitation and becomes that Member’s initial display name when they join (they or an Organizer can change it later); it is then removed from the invitation. To prevent misuse, we keep a short-lived count of failed invitation attempts per account.
Place information
For each place an Organizer adds, ARRVD stores:
- its name and address, and its latitude and longitude;
- the arrival area size (radius);
- the expected arrival time and days, the related alert settings (for example, whether to be told when arrival isn’t confirmed, the waiting time before that, and whether to be told about departures) and the place’s time zone;
- which Members the place checks arrival for; and
- who created it, and when it was created and last changed.
Location-related information
See section 3, which explains how location is used.
Arrival and activity information
When a Member’s device confirms an arrival (or a departure, if that place has departure notices turned on), ARRVD records an event containing the Member’s internal user ID, the place and its name, whether it was an arrival or a departure, and when it happened. When a Member’s arrival hasn’t been confirmed by the expected time, our server records a “not yet confirmed” event for that Member and place. These events do not contain map coordinates.
Sharing choice and watching status
We record whether a Member has allowed their arrivals and departures to be shared (the choice, the version of the explanation shown, and when). We use this record to respect the choice and to show that it was made; it contains no names, locations or place names. A Member’s device also reports to our servers whether it can watch the places assigned to it (each place’s registration status and the type of location permission). This report does not contain the device’s location.
Age range, guardian consent and country of residence
We record your age range (18 or over, or 13 to 17 — never your date of birth), and, for a Member aged 13 to 17, the guardian’s consent (see section 4). We also record the country you state you usually live in (see section 6).
Device and notification information
- To send notifications and to check that watching is working, we store, for Organizers’ and Members’ devices, a device identifier created by the app, a push notification token (Firebase Cloud Messaging), the platform, whether notifications are enabled, the app version, the device’s language setting and related timestamps. For Members’ devices we also store how watching is working, such as the location permission status and the number of records waiting to be sent (never the location). Firebase may use an installation identifier to deliver these messages. We also record which notifications have already been delivered to which device, so they aren’t sent twice.
- To check that requests come from a genuine copy of ARRVD, we use Firebase App Check with Apple’s App Attest service.
- On your own device, ARRVD keeps the places it is watching, recent arrival status, a local activity log, your role and the app-generated device identifier.
Purchase information (ARRVD Plus)
See section 9.
Support communications
If you email us, we receive your email address and whatever you include in your message.
Service logs
Our servers keep limited technical logs — such as internal identifiers and the outcome of automated checks — to run the service, keep it secure and fix problems. Records of requests to our servers also include the IP address and the app and device information sent with the request. Push tokens, place names, addresses and locations are not written to these logs.
What ARRVD does not do
- No advertising, and no advertising or analytics SDKs.
- No selling of personal information.
- No tracking of you across other companies’ apps or websites.
3. Location
- A Member’s device starts detecting and sharing arrivals and departures only after the Member chooses “Allow” in the app themselves. An Organizer cannot allow it on a Member’s behalf. A Member can stop sharing at any time from the home screen; their device then stops watching places, and no new arrivals or departures are sent or notified.
- ARRVD uses iOS Location Services — mainly region monitoring (often called geofencing) — so that a Member’s iPhone can notice when it arrives at, or leaves, a place assigned to that Member. iOS checks this on the device, including while the app isn’t open, if the Member has allowed it. Background checks generally need location access set to “Always”.
- A Member’s device only watches the places that Member is assigned to. Organizers’ devices don’t watch places.
- What ARRVD sends from a Member’s device is the arrival or departure event described in section 2 — which place, which kind of event and when. It does not send the device’s coordinates or a history of its movements, and it does not show the Member’s position to anyone on a live map.
- Places themselves do include an address and coordinates (see section 2). These are stored on our servers. The family’s Organizers can see and manage every place; a Member’s device receives only the places assigned to that Member.
- When an Organizer chooses “Use Current Location” while adding a place, the device determines its location once to fill in that place.
- Place search, map previews and address lookups use Apple Maps services. The search text or the place’s coordinates are sent to Apple to return results.
- If Location Services or ARRVD’s location permission is turned off or limited, arrivals may be detected late or not at all.
4. Age, guardians and turning 18
Organizers must be 18 or over and Members 13 or over. Before joining you choose your birth year and month; they are used only on your device to decide an age range and are never sent or stored. We record only the range — 18 or over, or 13 to 17. People under 13 can’t use ARRVD (the device keeps a note that “under 13” was answered so that it doesn’t ask again for 24 hours; the note stays only on that device and nothing is sent to us).
A Member aged 13 to 17 shares nothing until both a parent, guardian or person with parental responsibility (a guardian) and the Member themselves have agreed. The guardian uses their own Apple account to declare that they are 18 or over, that they are the Member’s parent, legal guardian or a person with parental responsibility, and that they understand and agree. We record who the consent covers, the version and language of the explanation, the date, and the relationship and name given. Organizers and the Member are told when a consent takes effect, and an Organizer can object if they don’t recognise the guardian (sharing then stops). This declaration is not an official identity check. The explanation a guardian agrees to is on the page for guardians.
When a Member who joined under 18 turns 18 and asks in the app, the guardian who consented can confirm it; the guardian’s consent then ends and only the Member’s own consent decides what is shared. No date of birth or ID is asked for this confirmation, and it doesn’t change past records (they are still deleted after 7 days).
5. What is shared within your family
- Everyone in the family can see the family’s name and its members, with their display names (or default labels) and roles.
- Organizers can see and manage all of the family’s places, including names, addresses and coordinates. Each Member can access only the places assigned to them, not the family’s other places.
- Organizers can see the family’s arrival, departure and “not yet confirmed” activity. For a Member under 18, only the Organizers their guardian allows can see their records, and only from when they were allowed; the guardian can stop this at any time. If the guardian is also an Organizer of the family, they can see the records from their consent on; this stops only when they withdraw their consent. Each Member can access only the activity about themselves, not other Members’ activity.
- Organizers can see each Member’s watching status (for example, watching, not sharing, or waiting to sync) — never a location.
- Organizers receive notifications about a Member’s arrivals, departures (when turned on for that place) and arrivals that haven’t been confirmed by the expected time. These notifications include the Member’s display name and the place’s name.
- Not shared with other family members: a Member’s live location or movement history (ARRVD doesn’t create either), push tokens or other device information.
6. Country of residence
When you join, you choose the country you usually live in — not a country you are visiting (change it in the app if you move). We never infer it from your location, IP address or App Store country. ARRVD serves people living in Malaysia and Japan. If you choose another country, you can’t newly join; a Member already in a family stops sharing arrivals and departures, and an Organizer stops receiving and seeing Members’ arrivals and departures (other Organizers and the Member’s own sharing are unchanged). It resumes when you state a served country again or when ARRVD starts serving yours.
7. How we use information
- To create and sign in to your account.
- To set up and run your family, including invitations and roles.
- To create and manage places and decide which Members each place checks.
- To detect arrivals and departures, and to determine when an arrival hasn’t been confirmed by the expected time.
- To send arrival, departure and “not yet confirmed” notifications.
- To provide ARRVD Plus and keep track of which plan applies to your family.
- To operate, secure and troubleshoot ARRVD, and to prevent misuse.
- To answer support requests.
8. Service providers
ARRVD relies on a small number of providers, which process information on our behalf or under their own terms:
- Apple — Sign in with Apple, the App Store and in-app purchases, Apple Push Notification service, iOS Location Services, Apple Maps services (place search, map previews and address lookups) and App Attest.
- Google Firebase (running on Google Cloud) — Firebase Authentication, Cloud Firestore (our database), Cloud Functions (server-side checks and notifications), Firebase Cloud Messaging, Firebase App Check and Firebase Installations.
We may also disclose information if required by law, or where reasonably necessary to protect the safety, rights or security of our users, the public or ARRVD.
9. ARRVD Plus and purchases
ARRVD has a free plan. ARRVD Plus, a paid plan, is purchased through the App Store once it is offered. Payments are handled by Apple using your Apple Account; we never receive or store your card number or other payment details. To provide ARRVD Plus and to restore purchases, the app uses the information Apple makes available about your purchase — for example, which product was purchased, whether it is currently active, and transaction identifiers or status. You manage or cancel subscriptions in your Apple Account settings.
10. How long we keep information, and deletion
- We keep account, family and place information while your account and family are in use, because ARRVD needs it to work.
- Arrival, departure and “not yet confirmed” activity is deleted automatically once 168 hours (7 days) have passed since it happened or since our servers received it, whichever is earlier. Deletion runs every hour. Records of which notifications were delivered to which device are deleted together with the activity.
- Consent records — a Member’s own sharing choice (section 2), a guardian’s consent, withdrawals, objections and the age range each person stated — are kept as follows: one still in force or current, for as long as it is; one that has ended (withdrawn, replaced, or the person left the family), for 3 years from its end; a decline, a withdrawal or an objection, for 3 years from when it was made. Each month we delete those past their 3 years; records needed for a complaint or legal proceedings are kept until that is resolved, then deleted. Apart from the name a guardian gives (section 4), which is erased when the guardian’s account is deleted, they contain no names or locations.
- Your age range and country of residence are kept while you belong to a family. A record that someone declared they are under 18 is kept until their move to adult or the deletion of their account, so a minor can’t rejoin as an adult.
- Device registrations are deleted when you sign out, when a Member stops sharing, or when you delete your account (the next time the device is online, if it is offline at the time).
- Service logs, including the records of requests with IP addresses (section 2), are deleted automatically after 30 days. Audit logs kept by Google Cloud of administrative changes we make to our servers (such as configuration changes), which do not record your use of ARRVD, are kept for up to 400 days.
- To recover from mistakes or outages, we can restore the database to any point within the past 7 days. Deleted information therefore remains in recovery data for up to 7 days and is then erased automatically; it is used only for recovery and can’t be seen in the app.
- Invitation records and failed-attempt counts are kept for the purposes described above.
- Information stored on your device is removed when you delete the app. Signing out on a Member’s device also stops that device from watching the family’s places.
- Deleting the app does not delete your account or the information stored on our servers.
Deleting your account
You can delete your ARRVD account at any time in the app, and confirm it with Sign in with Apple:
- Organizers — Settings › Account › Delete Account.
- Members — the Account section at the bottom of the home screen › Delete Account.
When you delete your account:
- Your ARRVD account and sign-in are deleted, and ARRVD’s Sign in with Apple authorization is revoked.
- The information ARRVD keeps about you is deleted: your family membership and display name, your device and notification registration, your arrival, departure and “not yet confirmed” activity, your place assignments, your sharing choices, and invitations you created or accepted.
- If you’re an Organizer and another Organizer remains, the family and its shared information stay with them.
- If you’re the family’s last Organizer, the family is deleted too, including its places, activity and invitations. Other members’ ARRVD accounts are not deleted; they are removed from the family.
- On the device you delete from, places being watched, the local activity log and ARRVD’s notifications are removed.
- Consent records, including the record of your sharing choices, are kept as described above, without your name.
- Technical logs, including request records with IP addresses (section 2), are deleted automatically after 30 days, and recovery data after 7 days (see above). Audit logs of administrative changes we make to our servers, which do not record your use of ARRVD, are kept for up to 400 days.
- Deleting your account does not cancel an ARRVD Plus subscription. Manage or cancel subscriptions in your Apple Account settings.
If you can’t use the app to delete your account, email futodama0610@gmail.com and we’ll help.
11. Your choices
- Location access — change it at any time in iOS Settings. Without it, arrivals can’t be detected.
- Notifications — turn them on or off in iOS Settings.
- Arrival sharing (Members) — make or change your choice in the app under “Arrival sharing”.
- Display name — change your own name in the app; Organizers can change Members’ names.
- Sign in with Apple — you can manage which apps use your Apple Account in your Apple Account settings.
- ARRVD Plus — manage or cancel your subscription in your Apple Account settings.
- Stop sharing or withdraw consent — Members can stop sharing at any time from the home screen, and guardians can withdraw their consent in Settings › Guardian requests and consents; in the app this takes effect right away. If you can’t use the app, you can also withdraw in writing by email to futodama0610@gmail.com (tell us the family name, the Member’s display name and your role). An email does not stop sharing by itself: we read it, stop sharing promptly by hand and reply to confirm (if we can’t tell which account it is, we reply to ask). Records arriving after sharing stops are refused by our servers.
- Delete your account — in the app, as described in section 10.
- Questions or requests — including requests to see, correct or delete information — email futodama0610@gmail.com.
Requests about your information
You can ask to see, correct or delete your information, to stop its use, or to receive it in a form you can move, by emailing futodama0610@gmail.com. A guardian can ask on behalf of their child. We first confirm that the request comes from you (or the guardian), and requests are free. For users in Malaysia we reply within 21 days; if we can’t complete it in time, we tell you in writing before then why, and complete it within 14 more days. For users in Japan we reply without delay. If you are not satisfied, you can complain to the Personal Data Protection Department (Malaysia) or the Personal Information Protection Commission (Japan).
12. Security
We take reasonable measures to protect information, including encrypted connections, database rules that limit each family’s information to that family, app integrity checks and storing invitation codes only in hashed form. No method of transmission or storage is completely secure, so we can’t guarantee absolute security.
13. Families and members
ARRVD is meant for use among family members. “Organizer” and “Member” are roles in the app; they don’t indicate a family relationship or any legal status as a guardian. An Organizer invites the people they want in the family and should explain how ARRVD works (only arrivals at and departures from registered places are shared — never a live location or a movement history). A Member’s arrivals and departures are shared only if the Member allows it on their own device, and, for a Member under 18, only with a guardian’s consent as well (section 4). If you believe information was added without proper permission, or you are a guardian who wants to review or delete a child’s information, please contact us.
14. International processing
futodama operates ARRVD from Malaysia. Database and server processing run in Google Cloud’s Singapore region; sign-in is processed on Google’s facilities in the United States; notification delivery and misuse protection (App Check) run on Google’s and Apple’s facilities in various countries. Service logs may be stored on Google’s facilities worldwide. For notification delivery, misuse protection and logs, the countries can’t be named in advance, because the providers choose among their facilities around the world. The purposes are providing watching, sending notifications and preventing misuse. Processing abroad is covered by each provider’s safeguards and terms, and we keep a record of where information goes and why.
Recipients, countries and their privacy laws
When you agree in the app to “Handling outside your country”, you agree that we provide ARRVD’s information to these recipients:
- Google (based in the United States) — database and server processing (Singapore), sign-in (United States), notification delivery, misuse protection and service logs (facilities in various countries).
- Apple (based in the United States) — delivery of notifications to iPhones and misuse protection.
- Singapore — the Personal Data Protection Act 2012 is a general privacy law, supervised by the Personal Data Protection Commission, with rules on consent, purposes, access and correction, protection and breach notification.
- United States — there is no general federal privacy law. Privacy is covered by laws for particular sectors, by state laws (for example California’s) and by the Federal Trade Commission’s action against unfair or deceptive practices.
- Other countries — for notification delivery, misuse protection and logs, the providers choose among their facilities around the world, so the countries can’t be named in advance. They are among the countries where Google and Apple run facilities.
- Malaysia — the operator is in Malaysia and handles your information under the Personal Data Protection Act 2010.
Measures the recipients take: Google processes the information only on our instructions under its data processing terms, with security measures, confidentiality of its staff, control of its subprocessors and notice of security incidents. Apple delivers notifications under its developer terms without accessing their content.
Without this consent you can’t use ARRVD. You can stop at any time by deleting your account (section 10).
15. Changes to this policy
We may update this policy as ARRVD changes. When we do, we’ll update the date at the top of this page, and we’ll let you know about significant changes in the app or on this page.
16. Contact
futodama (an individual developer) — futodama0610@gmail.com
This address is also our privacy contact for questions, requests and complaints. If you ask, we will tell you the operator’s name and address without delay.