Privacy Policy

This policy explains how Jar, the iPhone app, and its page at rflx.app/jar handle information. Jar is published by rflx.app (“we” or “us”). Contact us at rflx.app@gmail.com with privacy questions or requests.

In short: what you write, photograph, and record in Jar stays on your iPhone unless you give a jar away. Jar has no accounts, shows no ads, sells nothing, and does not track you across apps or websites. Google Firebase receives usage statistics and crash reports, which never include what your lines say, your photos, or your recordings.

Your lines, photos, and recordings

Everything you put in Jar is stored only on your iPhone: the lines on the page, the photos and recordings you add, the jars on your shelf with their labels, dates, and notes, and your settings. Jar does not sync it through iCloud or send it to us. It may be included in your device backups, depending on your iCloud or computer backup settings. Deleting Jar deletes your jars, and we cannot recover them.

Jar does its work on your iPhone. When you add a photo, Jar keeps a smaller copy and uses Apple’s on-device Vision framework to choose which part of it to show on the page. Motion sensors let Jar react when you shake, tilt, or turn your phone face down; those readings are used on the spot and never stored or sent.

Permissions

• Photos: you choose each photo in Apple’s photo picker, which gives Jar only that photo, not your library.
• Microphone: used only while you hold the record button to make an audio line. Jar asks the first time you press it.
• Face ID: after your page has been scrambled, Jar can ask iOS to confirm it’s you before showing it again. iOS handles Face ID and only tells Jar whether it succeeded; Jar never receives your face data.

You can change these permissions at any time in iOS Settings.

Giving a jar

Giving a sealed jar is the one time its contents leave your iPhone, and only when you choose to. A gift contains the whole jar: every line, photo, and recording in it, its label, shape, liquid, and dates, the name you give as who it is from, and your note.

• By link: if you are signed in to iCloud, Jar puts the gift in your own iCloud private database, in a space created for that gift, and shares it with anyone who has the link. Anyone you send the link to, or anyone they pass it to, can open it; the first person to open it receives the jar. While it waits it uses your iCloud storage. Once it is opened or you take it back, Jar deletes it from your iCloud. Apple operates iCloud under Apple’s Privacy Policy; we cannot see what is in your private database.
• As a file: without iCloud, the gift is a .jargift file that goes wherever you send it, such as Messages, Mail, or AirDrop. Those services handle it under their own policies.

The person who receives a jar gets a copy of everything in it. Only give jars to people you trust with their contents.

When you receive a gift, Jar reads the file or link, checks that it is a jar, and puts it on your shelf. Opening a link through iCloud records on the gift that it was opened, so the giver’s Jar knows it arrived.

Usage statistics and crash reports

Jar includes Google Firebase Analytics and Firebase Crashlytics, which start when the app opens.

• Analytics records what kind of thing happened, never its content: for example that a text, photo, or audio line was added or dropped, the jar’s shape, size, and liquid, how many lines, photos, and recordings a jar held when sealed, how long a recording was in seconds, whether a jar was a time capsule, what kind of label it wears, whether a gift went by link or file, why a gift could not be opened, and which screens you visit. The Firebase SDK also processes an app-instance identifier, device and app information, session activity, and approximate location derived from your network address.
• Crashlytics receives crash diagnostics, such as stack traces, app and iOS versions, device model, timestamps, and an installation identifier, so we can fix crashes.

None of this includes what your lines say, labels, names, notes, photos, or recordings, and it is not linked to your identity. Jar does not ask to track you, so iOS does not give it your advertising identifier. There is no in-app switch for analytics. See Firebase’s privacy information and Google’s Privacy Policy.

The website and beta waitlist

GitHub Pages hosts rflx.app/jar. Its servers receive technical request information, such as your IP address, to deliver and secure the site; see GitHub’s Privacy Statement. The pages load the Nunito font from Google Fonts, so Google receives your IP address and browser information when you visit. The site sets no cookies and runs no analytics.

If you join the TestFlight waitlist, your email address and the date you joined are saved to a private Google Sheet we control, through a Google Apps Script that can only add rows to it. Your browser also remembers the address locally so the page can show that you’ve joined. We use it only to send you a TestFlight invite, never for newsletters or advertising, and we keep it until the beta ends or you ask us to delete it.

If you email us, we receive your address, your message, and anything you attach, and use them only to reply.

Sharing and retention

We do not sell or rent personal information, and we share it only with the providers named above to run the app, the site, and support. Information may be processed in countries other than your own. We may disclose information when required by law or necessary to protect people’s rights or the security of our services.

Firebase, Google, GitHub, and Apple apply their own retention rules. Deleting Jar does not erase information those providers have already received.

Your choices and requests

You can skip or turn off permissions in iOS Settings, delete lines and jars in the app, take back a gift that hasn’t been opened, or delete the app. Email rflx.app@gmail.com to ask about access to, correction of, or deletion of information we hold. Depending on where you live, you may also have rights to object to or restrict processing, receive a copy of your data, or complain to a data protection authority. Because Jar has no accounts, we cannot find usage statistics or crash reports from an email address alone.

Changes

We will update the date on this page when this policy changes, and give additional notice or ask for consent where the law requires it.