Privacy Policy for SlaysForDays
Last Updated: October 11, 2026
This Privacy Policy explains how SlaysForDays ("we," "us") collects, uses, shares, and protects personal information in our app. We are the data controller: Monrad Ruzt Technology, a Norwegian sole proprietorship (enkeltpersonforetak), organisation number 935 118 654, Vesterålsveien 75, 8416 Sortland, Norway. Contact: legal@slaysfordays.com.
1. Information We Collect
- Account info: name, email, profile data.
- Content you provide: wardrobe items, including the notes you type on a piece and the name you write for whoever has borrowed it, photos, stylist chat / analyze-garment text, and what you choose to post in a squad. A squad look keeps the caption you wrote (up to 280 characters) and a copy of each garment's label as it read when you posted, so a later rename or delete does not rewrite what your squad already saw. Squad members can see your looks and vote on them.
- Beauty answers: The makeup and hair advice screen stores the answers you picked there (your age band, hair length and texture words, notes about your skin, the zones you want skipped, colour words) in your cloud profile, so the advice is the same on your other device. They are your own short chosen words, they are deleted with the account, and you can use the screen without the cloud; if you are not signed in, the answers stay on this device.
- Waitlist: If you tap "notify me" on the Shops we like teaser, we keep your account id and the date you asked. No email address is stored.
- Reports and blocks: if you report a look or a member, or block an account, we keep what you filed and the accounts it names. See §3.
- Approximate location: If you enable weather in Planner, we request location permission and collect approximate location (Accuracy.Low, down to about 1 km). This is stored in your profile. You can deny permission; weather may then not work.
- Analytics/usage: If analytics is enabled, we collect device type, OS, IP address, usage data, and session duration via PostHog. If analytics is not enabled, no such data is collected.
- Guest AI usage: If you never sign in, our server still keeps one row for you, keyed by a random device id. It holds only how many AI calls that device has used, so the free allowance can be enforced.
We do not collect health records or biometric data. The one field that comes closest is the skin and sensitivity note in the beauty answers: you write it yourself, in your own short words, it is optional, and you can leave it empty.
2. How We Use It
- Provide and operate the app (contract).
- Personalize and improve the app (legitimate interest).
- Respond to support and send service messages (contract/legitimate interest).
- Comply with legal obligations (legal obligation).
- Analytics, if enabled (legitimate interest).
3. Sharing and Recipients
We do not sell your personal information. We do not use it for targeted advertising. We share only as described below.
Recipients
- Supabase — storage, database, auth.
- Google Play — payments. If you buy Slay Pro, Google takes the payment and hands the app a purchase token. Our server shows that token to Google to confirm the purchase, and we keep it in our own database together with your account, the product and base plan you bought, whether it is still active, and when it expires — those decide which features you get. A token is a receipt reference, not a card number; Google holds the payment itself and its own privacy notice covers it.
- PostHog — analytics, only if enabled.
- Anthropic (
api.anthropic.com) — receives wardrobe text and stylist chat / analyze-garment conversations, and the beauty answers that go with an advice request. - remove.bg (
api.remove.bg) — receives the photo you submit for background removal. - MET Norway (
api.met.no) — receives coordinates for weather. - Open-Meteo (
geocoding-api.open-meteo.com) — receives coordinates or city name for geocoding. - Legal authorities — when required by law.
Squad features: A squad is a private feed made of the people you share your closet with. If you post a look, or someone posts in a squad you belong to, its members can see the look and vote on it; the caption and the garment labels travel with it, and they are deleted together with the look. Only members of that squad can read it, because visibility follows the closet seat: when a seat is revoked, the feed goes quiet for that person. You control what you post and who you invite.
Closet invitations: When you share a closet, the seat row stores the email address you typed for the person you invited, together with your own, so the invitation can be delivered to the right account and the seat can be proven. Only the two of you can read those addresses.
Closet presence: A shared closet records which member was in it and when, so the other person can see that you are there. The people sharing that closet are the only readers, and a row is a heartbeat rather than a history: it goes when the app stops seeing that person.
Reports and blocks: If you report a look or a member, we store who filed it, which account and which post it is about, the reason you picked, any note you typed, and what the owner decided — open, reviewed, dismissed, or actioned. Only you and the owner's account can read that row: the person you report is not told, and the person you block is not told either, because a block only changes what you see. You can withdraw a report while it is open; once it has a decision, it stays as the record of that decision. If you delete your account, the reports you filed go with it, and a report about your account is kept — so that deleting an account cannot erase a complaint made against it.
Public image buckets: Garment images and avatars are stored in Supabase public buckets. Anyone with the exact UUID path can access the image without logging in. Bucket listing is owner-only, and paths are unguessable UUIDs. Do not upload images you need to keep strictly private.
4. Your Rights
Depending on your location, you may have rights to access, correct, delete, port, object to or restrict processing, and withdraw consent. We do not sell or share personal information for cross-context behavioral advertising. To exercise your rights, contact legal@slaysfordays.com. We respond within 30 days.
5. Retention
We keep personal information only as long as needed for the purposes above or to comply with legal obligations, then delete or anonymize it.
6. Security
We use reasonable technical and organizational measures, including encryption in transit and access controls. No method is 100% secure. See the public bucket note in §3.
7. International Transfers
Your data may be processed outside your country. Where required, we use appropriate safeguards (e.g., standard contractual clauses).
8. Children and Age
SlaysForDays is not intended for children under 13. In the EU/EEA, you must be 16+ or have verifiable parental consent if you are 13–15. If we learn that a 14-year-old in the EU/EEA has an account without required consent, we will delete the account. For users under 13, we do not knowingly collect data; contact us for deletion.
9. Changes
We may update this Policy. Material changes will be notified in the app or by email. The "Last Updated" date above reflects the latest revision.
10. Contact
Any question about this Policy, and any request under the rights in §4, goes to the controller named
at the top of this page.
Operator: Monrad Ruzt Technology, a Norwegian sole proprietorship (enkeltpersonforetak)
Address: Vesterålsveien 75, 8416 Sortland, Norway
Organisation number: 935 118 654
Email: legal@slaysfordays.com