Privacy Policy

Who we are

Aspinflu is made by The Lavysh Tech, a company established in South Carolina, United States. The Lavysh Tech is the data controller for the information described here, which means we decide how it’s used.

Email: zakhar@lavysh.net

Who can use Aspinflu

Aspinflu is for people aged 13 or older, or older if the law where you live sets a higher minimum age. It isn’t directed at children, and we don’t knowingly collect personal information from children under 13.

We don’t ask your age. The “kid-friendly” option in the AI generator is a content preference that changes what the slices say. It isn’t an age check, and it doesn’t tell us how old you are.

If you think a child under 13 has sent us personal information, email us and we’ll delete it.

What stays on your device

The following never leaves your phone unless you share it yourself (see Sharing below). We have no copy and no way to get one:

• wheels you create, including their names and slice labels
• images you add to slices, whether you choose them from your photos or take them with the camera, and how you framed them
• your spin history: which slice won, and when
• ready-made wheels you’ve added or changed
• your settings: language, sounds, vibration, spin feel and appearance

When you add an image, Aspinflu only gets the one photo you choose or take, never access to the rest of your library.

Deleting the app deletes all of it. Because we never had a copy, there’s nothing for us to delete on our side.

Sharing

When you share a wheel or a spin result, Aspinflu hands it to your phone’s share sheet, and it goes straight to the app or person you choose. It doesn’t pass through us.

A shared wheel file contains the wheel’s name, its slices and settings, and any photos you added to its slices, so share it only with people you’d show those photos to. When you open a wheel file someone sends you, it’s imported directly onto your phone.

What leaves your device

1. AI wheel prompts

When you ask Aspinflu to generate a wheel, the app sends our server:

• the text you typed or dictated
• how many slices you asked for
• the tone you picked
• the language for the result
• your content preferences (kid-friendly, no alcohol) and a maximum label length
• the anonymous ID described in section 2

Our server passes your prompt and those settings, without the anonymous ID, to Google’s Gemini API, which writes the slices and sends them back.

Google processes prompts under its terms for paid Gemini API customers: it doesn’t use them to improve its products, and it keeps them only for a limited period to detect abuse and meet legal requirements.

To make the daily limit work, our server keeps a count of how many wheels have been generated per anonymous ID per day. Each day’s count is deleted automatically after 3 days. The app also keeps a copy of the count on your phone, to show you how many you have left.

2. The anonymous ID

The first time you open Aspinflu, the app asks Firebase Authentication, a Google service, for a random anonymous ID.

We use the ID to:

• count your AI generations each day, as described above
• connect related entries in our server logs, which we keep for 30 days, when we investigate errors or abuse

It’s never attached to your usage data, and it’s never sent to Google’s AI.

Firebase keeps the ID together with when it was created and last used. Google also logs the IP addresses used to get one, and keeps those logs for a few weeks.

The ID stays the same when the app updates. On Android, deleting the app removes it from your phone. On iPhone, iOS can keep it in the device’s keychain after you delete the app, so reinstalling may bring back the same ID.

3. Usage and crash data

Aspinflu uses Google Analytics for Firebase and Firebase Crashlytics to learn how the app is used and to find out when it breaks.

The events we record ourselves are limited to counts, fixed option names and yes/no values. For example: a wheel was spun; a wheel was created by hand, by AI or from a ready-made wheel; how many slices it had; which tone was picked; that an AI generation failed, and which broad kind of failure it was. Our code doesn’t allow wheel names, slice labels, prompts or anything else you typed into an event.

Firebase also automatically records standard technical information: your device model, operating system and app version, language, approximate location (such as country or city, worked out from your IP address), and when and for how long you use the app.

This data is tied to a random app-instance ID that Firebase creates on your phone, which changes if you reinstall the app. On Android, Firebase also reads your device’s advertising ID, unless you’ve deleted it in Android settings. On iPhone, it reads Apple’s identifier for vendor, which is shared only by apps from the same developer. We don’t use either one to show you ads.

Crash reports record which part of the code failed, a technical description of the error, and your device model, operating system and app version. We write the app so that crash reports don’t contain anything you typed, and for errors the app handles itself we leave the error text out entirely.

Google processes this data for us under Firebase’s terms. To learn how Google uses information from apps that use its services, see policies.google.com/technologies/partner-sites.

4. Voice input

If you tap the microphone to dictate a prompt, Aspinflu uses your phone’s built-in speech recognition: Apple’s on iPhone, or your phone’s speech service (usually Google’s) on Android. Depending on your device and language, the audio may be processed on your phone or sent to Apple or Google to be turned into text, under their privacy policies.

Aspinflu never receives or stores the audio, only the text, which goes into the prompt box. The microphone is used only while you’re dictating, and only after you’ve given permission.

5. Technical connection data

Like any internet service, our server sees the IP address each request comes from. Our hosting provider, Google Cloud, logs each request’s IP address and time, the address called, whether it succeeded, and the type of app or device that made it. Our own server logs record the anonymous ID, the length of your prompt (never its text), the number of slices, the result language and how long the request took. We use these logs only to keep the service running and to stop abuse, and they’re deleted after 30 days.

If a request arrives without an anonymous ID, for example because one couldn’t be created, we count it against a scrambled form of your IP address instead: a salted, one-way hash of the address (or, for IPv6, of its network prefix). The address itself is never stored in our database.

The first time the app needs its rounded typefaces, it downloads them from Google Fonts and keeps them on your phone. As with any download, Google sees your IP address and the standard technical details of the request. Nothing about you or your wheels is sent.

6. Anything you send us

If you email us or send feedback from the app, we receive what you wrote and your email address. We use them to reply and to improve Aspinflu. Our email is provided by Google.

This website

This website, aspinflu.lavysh.net, uses no cookies, analytics or trackers, and loads nothing from other sites. It’s hosted by Cloudflare, which processes visitors’ IP addresses to deliver the pages and to protect the site from attacks.

Information we don’t collect

To be explicit, Aspinflu does not collect:

• your name, email address or phone number, unless you email us
• your age or date of birth
• your precise location. Aspinflu never asks for location permission (Firebase works out an approximate area from your IP address, as described in section 3)
• your contacts, your calendar, or any photo other than the ones you pick for a slice
• your wheels, their names, slices or images, or your spin history
• recordings of your voice
• payment information, since there’s nothing to buy

Aspinflu has no accounts and shows no ads.

Who handles your data

When you dictate a prompt, Apple or Google also handle your voice, as part of your phone’s operating system and under their own privacy policies.

We don’t sell your data or share it for advertising. We don’t share it with anyone not listed here, unless the law requires us to.

Where your data is processed

The Lavysh Tech is based in the United States, and our server and its database are in the United States. Google and Cloudflare may also process data in other countries where they operate.

If you use Aspinflu from outside the United States, including from the European Economic Area or the United Kingdom, your data is transferred to the United States, where privacy law differs from your own. Our providers protect these transfers with recognised safeguards, such as the EU Standard Contractual Clauses.

How long we keep things

Your rights

Every Aspinflu user has the same rights, wherever you live. You can ask us to:

• tell you what data we hold about you
• correct it
• delete it
• give you a copy in a portable format
• restrict or stop processing it, or object to our processing
• stop collecting usage and crash data. The switch in Settings does this immediately, without emailing anyone

You’ll never be treated differently for using any of these rights.

How to use them

Because Aspinflu has no accounts, it works like this:

1. Your wheels, images, spin history and settings. They only exist on your phone. Deleting the app deletes them.
2. Usage and crash data. Switch off Usage and crash data in Settings → Your privacy to stop collection. To delete what’s already been collected, email us the app-instance ID shown on that screen, and we’ll delete the data recorded against it. Without that ID, we can’t tell which records are yours.
3. Daily AI counts and the anonymous ID. Counts delete themselves after 3 days. The anonymous ID holds nothing about you, and the app doesn’t currently display it, so we can’t find it from your email address alone. If you’d like it deleted, email us, and we’ll tell you honestly whether we can find it.
4. Email you sent us. Ask, and we’ll delete it from our mailbox.

Email zakhar@lavysh.net for any of these. We reply within 30 days.

If we can’t identify you from the information you give us, data protection law allows us to say so rather than guess. We’ll tell you plainly if that happens, and what would let us go ahead.

If you’re in the European Economic Area, the United Kingdom or Switzerland

We rely on these legal bases:

• Performance of our agreement with you (our Terms of Use), to provide the features you use, including generating AI wheels from your prompts.
• Our legitimate interests in counting AI generations fairly, keeping the service running and secure, and understanding and fixing the app through usage and crash data. You can object to usage and crash data at any time with the switch in Settings.

The Lavysh Tech is established in the United States and hasn’t appointed a representative in the EU or the UK. You have the right to complain to your local data protection authority, though we’d appreciate the chance to put things right first.

If you’re in California or another US state with a privacy law

You have the rights listed above. We don’t sell your personal information, and we don’t share it for cross-context behavioural advertising. We don’t use or disclose sensitive personal information. To use any of your rights, email us. You don’t need an account, because there aren’t any.

Do Not Track. We don’t use your data for advertising, and this website sets no cookies, so nothing changes when your browser sends a “Do Not Track” signal.

Security

Traffic between the app and our server is encrypted with HTTPS. Your wheels are stored in the app’s private storage on your phone, protected by its operating system and, if you’ve set one, your passcode or biometric lock. No system is perfect, and we don’t claim otherwise.

If a breach affects your data, we’ll notify the people affected wherever we can, and the relevant authorities, as the law requires, including under South Carolina’s breach notification law.

Changes to this policy

We update this page whenever what Aspinflu does with data changes, in the same code change that alters the behaviour, so the two can’t drift apart. Significant changes will be called out in the release notes of the app update that introduces them. The version and date at the top of this page show when it last changed, and every version is listed below.

Contact

The Lavysh Tech
zakhar@lavysh.net