Privacy Policy
Last updated
Summary (not legally binding). This summary is a guide to the policy below; the numbered sections are what apply. To run Jurvo we collect your sign-in details, a profile (your nickname and date of birth, plus your country and time zone from your device's settings), the Cards you post and how you vote. We do not sell personal information, show ads, track you across other companies' apps or websites, or use third-party analytics. Everyone using the App can see your Cards, with your nickname only on public Cards, and no other user can see how you voted. Other signed-in Members can access some of your profile details, listed in section 3.4. Our systems do not send your Cards to any AI service today. Our database is in the United States. To see, correct, export or delete your information, email [email protected] (section 18).
1. Who we are and what this policy covers
Link to this sectionThis Privacy Policy explains how PuredLab LLC, a New Mexico limited liability company (registration no. 0008109479) (we, us or our) collects, uses, discloses and protects personal information in connection with Jurvo, which includes:
- the Jurvo app for iOS (the App);
- our website at jurvo.me (the Site); and
- emails and other messages between you and us.
Together these are the Service. You means anyone who uses the Service. Personal information means information that identifies you, relates to you or could reasonably be linked to you.
The terms Card, Vote, Verdict, Guest, Account and Member mean what they mean in our Terms of Service (section 1). In short: a Card is a dilemma with two options; a Vote is a choice between them; a Verdict is a Card's result; a Guest uses the App without signing in; an Account is what you have once you sign in with Apple, with Google or with an email address and password; and a Member is a person who has an Account.
This policy does not cover services of other companies that you use alongside Jurvo, such as Apple's App Store, Sign in with Apple, Sign in with Google, or the apps and websites where you share a Jurvo image. Their own privacy policies apply to them. Our Consumer Health Data Privacy Policy adds to this policy for consumer health data (section 19.4).
2. The short version
Link to this section- We do not sell personal information, and we do not share it for cross-context behavioral advertising.
- There are no ads in the App or on the Site, and we do not use advertising identifiers.
- We do not track you across other companies' apps or websites.
- The App and the Site contain no third-party analytics, advertising or tracking software.
- The Site sets no cookies (section 12).
- We do not use personal information to train AI models, and our systems do not send your Cards to any AI service today (section 8).
- We do not make decisions based solely on automated processing that have legal or similarly significant effects on you.
- We give every user in the United States the same privacy rights, whatever state they live in (section 17).
3. Information we collect
Link to this sectionThe tables below list each kind of personal information we collect, where it comes from, why we use it, how long we keep it and who can see it. The column "Who can see it" describes access by other people using Jurvo and by our moderators. A small number of our staff who administer our systems, and our service providers when they act for us (section 10), can access all of it; section 13 explains how we limit that access. Section 15 brings all the retention periods together.
3.1 Sign-in information
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Your email address | You, if you continue with email; Apple, if you continue with Apple (it may be a Hide My Email relay address, section 20.1); Google, if you continue with Google | To create your Account, sign you in and recognize you when you contact us | Until the deletion of your Account is complete, about 30 days after we receive your request | Not other users, and not our moderators |
| Your password | You | To sign you in. Our authentication provider stores it only as a one-way cryptographic hash, never in readable form | Same as your email address | No one can read it, including us |
| Apple sign-in details: Apple's identifier for you, your email address, whether Apple has verified it, and technical details of the sign-in | Apple | To link Sign in with Apple to your Account and sign you in. Apple does not give us your name, and the App does not ask for it | Same as your email address | Not other users, and not our moderators |
| Google sign-in details: Google's identifier for you, your email address and whether Google has verified it, your name and a link to your profile picture if your Google account has them, technical details of the sign-in, and, for a Google Workspace account, its domain | To link Sign in with Google to your Account and sign you in (section 20.2). The App does not show your Google name or picture to anyone, including you | Same as your email address | Not other users, and not our moderators | |
| Account status and sign-in times: whether the account is a Guest account, when it was created and when it last signed in | Our systems | To run Guest mode and protect your Account | Same as your email address | Not other users |
For a Guest, the account status and sign-in times are kept until the Guest profile is deleted (section 5).
3.2 Sign-in sessions
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Session records: the IP address and the device and software details (user agent) that the App sends when it signs in or renews a session, and when it did so | Your device | To keep you signed in, protect your Account and investigate misuse | Until you sign out or your Account is deleted; for a Guest, until the Guest profile is deleted (section 5) | Not other users, and not our moderators |
| Session tokens | Our authentication provider | To keep you signed in. Access tokens expire after an hour and are renewed automatically | Until you sign out or your Account is deleted; for a Guest, until the Guest profile is deleted (section 5) | Not other users |
3.3 Profile information
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Nickname (2 to 24 characters) | You, when you finish creating your Account | To show who posted your public Cards and to identify your profile | Until the deletion of your Account is complete | Everyone using the App, on your public Cards; signed-in Members, on your profile (section 3.4) |
| Language | Set to English by default | To show you Cards in your language | Until the deletion of your Account is complete | Signed-in Members (section 3.4) |
| Settings: whether your profile is public (it is by default, and the App does not let you change it), whether new Cards default to public or anonymous (anonymous by default), and settings that have no effect in the App today | Defaults, and your choice of default posting mode | To apply your choices | Until the deletion of your Account is complete | Signed-in Members (section 3.4) |
| Alias: two words and four digits | Generated by us for every account | For a possible future feature. We do not show it anywhere today | Until the deletion of your Account is complete | No one today |
| Account tier | Our systems | To decide which features and limits apply to your account. No paid tier is offered | Until the deletion of your Account is complete | Signed-in Members (section 3.4) |
| Standing: a standing score, whether the account is flagged for attention, and the number of confirmed violations | Our systems and our moderators | To decide whether a person reviews your Cards before they are published (section 8) | Until the deletion of your Account is complete | Our moderators. Not other users |
| Suspension status: whether your Account is suspended, and until when | Our moderators | To enforce the Terms | Until the deletion of your Account is complete | Our moderators; signed-in Members (section 3.4) |
| Deletion request: when the deletion of your Account was requested | Our staff, once we have verified your request. Our service also accepts it directly from your own Account, although the App has no option for this | To delete your Account at the end of the 30-day window | Until the deletion of your Account is complete | Signed-in Members (section 3.4) |
| Purchase identifier: a random identifier created with your profile | Our systems | Reserved for purchases, which are not available (section 9.3) | Until the deletion of your Account is complete | Not other users |
| Account type: whether the account is a Guest account or an account we use for Cards written by our team | Our systems | To run Guest mode and to keep our team's Cards separate in our systems | Until the deletion of your Account is complete | Signed-in Members (section 3.4) |
| Internal identifiers, and when your profile was created and last updated | Our systems | To link your information across our systems and keep records | Until the deletion of your Account is complete | Signed-in Members (section 3.4) |
Our systems also contain fields for gender, city, region, a link to a profile photo and your main reason for using Jurvo, and a record of notification preferences with a device token for push notifications (section 9.2). The App does not ask for any of them and never fills them in. Our service would still store anything written to them from your own Account, until the deletion of your Account is complete. Other signed-in Members could then access the gender, region, photo link and main reason (section 3.4), but not the city or the notification preferences. Your date of birth is described in section 3.5, and your country and time zone in section 3.6.
3.4 What other Members can see on your profile
Link to this sectionYour profile is public by default, and the App does not offer a way to make it private today. While your profile is public, anyone signed in to an Account (but not a Guest) can access the following details through our service, even though the App itself displays only some of them:
- your nickname;
- your country and time zone;
- your preferred language;
- your account tier;
- whether your Account is suspended, and until when;
- your profile settings, including your default posting mode;
- whether a deletion of your Account is pending, and when it was requested;
- when your profile was created and last updated;
- whether the account is a Guest account or an account we use for Cards written by our team;
- your internal account identifiers; and
- the fields for gender, region, a link to a profile photo and your main reason for using Jurvo, which the App leaves empty (section 3.3).
This applies to every account with a public profile, including Guest accounts. Other users cannot access your email address, password, Apple or Google sign-in details, date of birth, alias, standing, purchase identifier, sign-in sessions, individual Votes, skips or saved Cards.
3.5 Date of birth and age eligibility
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Date of birth, if you are 18 or older | You, when you finish creating your Account | To confirm that you meet the age requirement (section 6) | Until the deletion of your Account is complete | No other user and none of our moderators. The App does not show it, not even to you |
| Eligibility record: when you confirmed that you are 18 or older and completed registration | Our systems | To record that you registered | Until the deletion of your Account is complete | Not other users |
| Age block, if the date you enter shows that you are under 18: the mark that blocks the account, and afterwards a record that an account was blocked | Our systems | The mark keeps the account blocked until we delete it. The record lets us count the accounts we have blocked for age. Neither contains the date you entered, and the record contains nothing that identifies you or the account | The mark until the account is deleted, within 30 days of the block; the record permanently (section 6) | Not other users |
| Age block marker on your device | The App, if it blocks an account for age | To stop the App from being used on that device | On your device; it can survive deleting and reinstalling the App | Stays on your device |
3.6 Device region and time zone
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Country | Your device's region setting, read when your profile is created. We do not use GPS or location services | To give some preference to Cards from your country in your daily set, and to attach a country to each Card you post | Until the deletion of your Account is complete; the copy attached to each Card stays with the Card (section 3.7) | Signed-in Members, on your profile; anyone using the App, on your Cards, including anonymous ones |
| Time zone | Your device's time zone, read when your profile is created | To work out your day for the daily set, and the deadlines of Cards | Until the deletion of your Account is complete | Signed-in Members (section 3.4) |
3.7 Cards you post
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Your Card: the question (up to 240 characters), the two options, the category, mood and intensity you choose, whether it is public or anonymous, its language, and a random identifier the App adds so that the same Card is not posted twice | You | To publish your Card, collect Votes, work out and show its Verdict, include it in lists, the archive and share images, and moderate it | While Jurvo operates, or until it is removed by us or at your request (section 17). If your Account is deleted, the Card stays without your nickname or any link to your Account | Everyone using the App, including Guests. Your nickname appears only on public Cards |
| The Card's country | Copied from your profile when you post | To order the daily set by country | Same as the Card | Anyone using the App, for anonymous Cards too |
| Voting details: vote counts, the deadline, when and why the Card locked, and the frozen result | Our systems | To run voting and Verdicts | Same as the Card | Everyone using the App. Anyone with a Card's share code can also get its vote counts and percentages, but not its text, from our service |
| High-risk marker: a yes-or-no marker for Cards about sensitive subjects, such as self-harm | Our systems | When it is set, it keeps a Card out of lists and the archive. Our systems do not set it today, so it is "no" on every Card | Same as the Card | Anyone using the App can access it with the Card |
| The link between the Card and your Account | Our systems | To know who posted each Card, for moderation, safety and the law (section 7) | Until the deletion of your Account is complete; then the link is removed | Not other users. Our moderators see only a short anonymous reference, never your nickname, email address or date of birth |
When anyone shares a Verdict, the share image shows the Card's category, question, options and results, and the option the person sharing chose if they voted. It never shows the author's nickname. Share images go wherever the person sharing sends them.
3.8 Votes, skips, saved Cards, follows and the Cards shown to you
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Your Votes: which option you chose on which Card, and when | You | To count your Vote in the Card's totals, percentages and Verdict; to avoid showing you the same Card again; to estimate your category preferences (section 3.10); and to produce statistics about how the Service is used | Kept in totals. While your Account exists, each Vote is linked to it; when your Account is deleted, the link is removed and the Vote stays in the totals | Not other users, who see only totals and percentages. If you share a Verdict after voting, the image can show the option you chose |
| Votes waiting to be sent | Your device, if you Vote while offline | Stored encrypted on your device until the App can send them | Until they are sent | Stays on your device |
| Skips | You | To keep a skipped Card out of your daily set for 7 days, and to measure how often Cards are skipped | Until the deletion of your Account is complete | Not other users |
| Saved Cards | You | To keep the Cards you save | Until the deletion of your Account is complete | No other user |
| Cards shown to you: a record of each Card served to you | Our systems | To avoid showing you the same Card written by our team twice, and to measure how often Cards are skipped | Until the deletion of your Account is complete | Not other users |
| Follows and follow requests: which Members an Account follows or has asked to follow | Your own Account, through our service. The App does not offer following yet and never creates them | For a possible future feature | Until the deletion of your Account is complete | Any signed-in Member can see whom an Account follows; a follow request is visible to the two Members involved |
3.9 Usage counters
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Counters of how many Cards you have voted on and posted in a period | Our systems | To apply limits, including the Guest allowance, and to prevent abuse | Until the deletion of your Account is complete | Not other users |
| Balances for promotional features that are not offered today | Our systems | None today | Until the deletion of your Account is complete | Not other users |
3.10 Inferences
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| That you are 18 or older | Worked out from your date of birth | To let you register | As part of your eligibility record (section 3.5) | Not other users |
| Category preferences | Worked out from the categories of the Cards you Vote on, once you have voted on enough Cards | To order the Cards in your daily set | Not stored; worked out again each time they are needed | No one |
3.11 Moderation and safety records
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Moderation cases: when a Card is held for review, the Card, why it was held, and the moderator's note and decision | Our systems and our moderators | To review Cards and enforce the Terms | Until the deletion of your Account is complete | Our moderators |
| Reports made through our service: the Card, the reason given and the account that made the report. The App has no report button yet, but our service accepts reports sent directly from a signed-in Member's account | The Member who reports | To review reported Cards. A Card that receives a set number of these reports is hidden automatically until a moderator reviews it (section 8) | Until the deletion of the reporting Member's Account is complete, or until the Card is deleted | Our moderators see the reason and how many reports a Card has, never who made them |
| Moderation decision log: each moderation action, why it was taken, the Card and Account concerned, who took it and whether it was automated | Our systems and our moderators | To keep a record of decisions, handle appeals and protect our legal rights | 3 years after the action. When your Account is deleted, the link to your Account is removed | Our moderators |
| Console audit records: each action our staff take in our moderation console, and what it concerned | Our systems | Security and accountability | 3 years after the action. When your Account is deleted, the link to your Account is removed | Our administrators |
| Crisis-language matches (section 8) | Our automated check | To show you support resources | Nothing about you is stored. Our server records a log line that names the matched rule but not your Account, and keeps it for up to 7 days | No one |
| Content preserved for legal reasons | Our staff | When the law requires it or to protect people, for example apparent child sexual exploitation that we report to NCMEC (section 10.5) | As long as the matter or the law requires; for reports to NCMEC's CyberTipline, 1 year | Our staff, and the authorities the law requires |
3.12 Emails with us
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Your messages: your email address, what you write and any attachments | You, or other people who write to us about a Card or about you | To answer you, handle requests and reports (including privacy and deletion requests), keep a record of them and protect our legal rights | 3 years after the matter is closed | Our staff who handle the message |
Email sent to our addresses passes through Cloudflare's email routing to our mailbox provider (section 10.1).
3.13 Information stored on your device
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Sign-in session, in the iOS Keychain, on that device only (not synced to your other devices) | Our authentication provider | To keep you signed in | Until you sign out. It can survive deleting the App, and reinstalling the App on the same device then signs you back in | Stays on your device |
| Age block marker, in the iOS Keychain | The App, if it blocks an account for age | To stop the App from being used on that device | It stays after you sign out, and can survive deleting and reinstalling the App | Stays on your device |
| Votes cast while offline, and the key that encrypts them | The App | To keep offline Votes encrypted until they are sent | The Votes until they are sent or you delete the App. The key is kept in the iOS Keychain and can survive deleting the App | Stays on your device |
| Daily progress: the identifiers of today's Cards and of your account, in a protected file that is not included in device backups | The App | To pick up your daily set where you left off | Replaced each day | Stays on your device |
| App configuration: categories, moods and settings | Our servers | To show the App's options | Until replaced by a newer version | It contains no personal information |
| Introduction marker | The App | To remember that you have seen the introduction | Until you delete the App | Stays on your device |
| Share images | Made on your device when you tap share | To pass to your device's share sheet. We never receive a copy | We do not keep them | Whoever you send them to |
Apple does not guarantee what happens to Keychain items when an app is deleted. So far, the sign-in session, the age block marker and the key for offline Votes have survived deleting and reinstalling the App. If you have an Account, signing out before you delete the App ends the session on that device.
The App does not ask for access to your location, photos, camera, microphone or contacts, does not use an advertising identifier, and does not set cookies.
3.14 Site visitors
Link to this section| What | Where it comes from | Why we use it | How long we keep it | Who can see it |
|---|---|---|---|---|
| Request information: your IP address, browser and device details, the page you asked for, the page you came from, and the time | Your browser | To deliver the Site and protect it from attacks and abuse | Under the policies of Hostinger and Cloudflare, which process it for us. We never link it to your Account | Hostinger and Cloudflare, and our staff if they review the logs |
The Site has no forms or sign-in, sets no cookies and loads nothing from other companies.
3.15 Where information comes from
Link to this section- You: your sign-in details, nickname, date of birth, Cards, Votes, skips, saved Cards and messages.
- Your device: your country (from its region setting), its time zone, its IP address and its user agent; for Site visitors, the browser's request information.
- Apple: your Apple sign-in details, when you continue with Apple.
- Google: your Google sign-in details, when you continue with Google.
- Our systems: identifiers, the alias, counters, standing, moderation records and logs.
- Inferences: your age eligibility and your category preferences (section 3.10).
- Other people: when someone reports a Card or contacts us about you.
4. How we use information
Link to this sectionWe use personal information to:
- provide the Service: create and run your Account or Guest profile, serve your daily set, record Votes, publish Cards, work out Verdicts, build lists and the archive, and make share images possible;
- order the Cards we show you: using your country, time zone, language and category preferences. This is not advertising;
- keep Jurvo safe and fair: check age eligibility, moderate Cards, enforce the Terms and the Content Policy, apply limits, and prevent fraud, spam, abuse and vote manipulation;
- communicate with you: answer your messages and send notices about your Account, the Terms or this policy;
- protect security: secure Accounts and our systems, and investigate incidents;
- understand and improve the Service: produce statistics inside our own systems, such as how many Cards are voted on or skipped, without third-party analytics;
- comply with the law and protect rights: respond to valid legal process, report apparent child sexual exploitation to NCMEC, keep records, and establish, exercise or defend legal claims; and
- do anything else you ask for or agree to.
We do not use personal information for targeted advertising, we do not sell it, and we do not use it to train AI models or sell it for that purpose. Our automated checks can refuse or hold a Card, and our systems hide a Card that receives a set number of reports (section 8), but a person reviews every held or hidden Card, a person decides every warning, suspension and ban, and you can appeal (Content Policy section 16).
5. Guest mode
Link to this section- When you choose "Explore as a guest", we create a Guest profile linked to an anonymous sign-in session on your device. A Guest profile holds the information described in sections 3.2, 3.6, 3.8 and 3.9, and the default settings, alias, account type and internal identifiers described in section 3.3. We do not ask a Guest for an email address, a nickname or a date of birth.
- A Guest can Vote on a limited number of Cards. Guests cannot post Cards.
- If you create an Account from your Guest session, your Guest profile becomes your Account and keeps everything.
- If you sign in to an existing Account instead, your Guest profile and its activity stay behind and are not added to your Account. The Votes you cast as a Guest stay in Card totals.
- If you delete the App, your Guest session can stay in the iOS Keychain on that device, and reinstalling the App on the same device then signs you back in to your Guest profile (section 3.13). If you lose the session, for example by moving to a new device, the Guest profile stays on our servers, and you cannot get back into it.
- We delete a Guest profile that was never turned into an Account after 12 months without activity, together with its sign-in sessions and the account status and sign-in times described in section 3.1. Its Votes stay in Card totals without any link to the Guest.
- A Guest profile has no email address, so we usually cannot confirm that a request comes from the person who used it (section 18).
6. The age requirement, your date of birth and the age block
Link to this section- Jurvo is only for people 18 or older (Terms section 2).
- To finish creating an Account, you enter your birthday with a date picker and confirm it. The screen does not say what age is required.
- If you are 18 or older, we store your date of birth and when you confirmed it (section 3.5). We do not show your date of birth to anyone, including our moderators and you.
- If the date shows that you are under 18, we do not store it. Instead, we mark the account as blocked, and the App places a marker in the iOS Keychain on your device that stops the App from being used on that device, even after you sign out. Apple does not guarantee what happens to Keychain items when an app is deleted; so far, the marker has survived deleting and reinstalling the App. We do not lift age blocks.
- Within 30 days of the block, we delete the account and all of its information, including its sign-in record. Votes cast from the account stay in Card totals without any link to it. We keep only a record that an account was blocked for age, which contains no date and nothing that identifies you or the account.
- Guests are not asked their age, but the age requirement in the Terms applies to them.
7. Anonymity, and what is public and what is private
Link to this section- Public and anonymous Cards. A public Card shows your nickname. An anonymous Card shows "Anonymous" instead.
- Anonymous to other users, not to us. We keep the link between every Card and the Account that posted it for as long as your Account exists. Our moderators see a short anonymous reference instead of your identity, but our staff who administer our systems can see which Account posted a Card, and we may disclose it as section 10 describes.
- Country. Every Card carries the country from your profile, and anyone using the App can access it, including on anonymous Cards.
- Your words. The details in a Card and the way you write can identify you to people who know you.
- Alias. We generate an alias of two words and four digits for every account, but we do not show it anywhere today.
| Who | What they can see |
|---|---|
| Everyone using the App, including Guests | Cards (question, options, category, mood, intensity, language, country, high-risk marker, vote counts and results), your nickname on your public Cards, lists and the archive |
| Signed-in Members | The profile details listed in section 3.4, and whom an Account follows (section 3.8) |
| Anyone with a Card's share code | The Card's vote counts and percentages, without its text |
| People who receive a share image | What the image shows (section 3.7) |
| Only you, among people using Jurvo | Your individual Votes and your saved Cards |
| No other user | Your email address, password, Apple or Google sign-in details (including the name and picture link from Google), date of birth, alias, standing, sign-in sessions, skips, the Cards shown to you and your usage counters |
8. Moderation, automated checks and crisis-language handling
Link to this section- Automated checks before publication. Every Card a Member posts goes through automated checks before it is published:
- a personal information filter refuses a Card that contains an email address or a U.S. Social Security number in its usual written form. We keep none of a refused Card's text: our server logs the refusal, the rule that matched and your Account, and keeps that log for up to 7 days (section 15);
- the same filter holds a Card for review by a person if it contains a phone number, a street address, a web link, a social media handle or certain explicit words; and
- a Card from an account with a low standing score, for example after confirmed violations or reports, is held for review by a person.
- Most Members' Cards are published right after these checks. A held Card is published only if a moderator approves it. Cards written by our team do not go through these checks; a person on our team approves each one instead (Terms section 6).
- Human review. Our moderators work in a console that shows them the Card and a short anonymous reference to its author, not the author's nickname, email address or date of birth, and that records every action they take.
- Reports. The App has no report button yet, so people report Cards by email (Content Policy section 17), and a person reviews each report. Our service also accepts reports sent directly from a signed-in Member's account. When a Card receives a set number of those reports, our systems hide it automatically, lower its author's standing score and open a case for a moderator, who decides whether the Card comes back. Fewer reports are needed when the author's standing score is lower. If the moderator finds that the Card suggests its writer is thinking about suicide or self-harm, we remove it and restore the standing the reports cost (Content Policy section 7).
- No AI service. Our systems do not send Cards to any AI service today. Section 9.1 explains what would change if we started using AI-assisted moderation.
- Crisis-language handling. Before a Card you post is published, an automated check can look for phrases suggesting that the writer may be thinking about suicide or self-harm. We switch on its list of phrases only after qualified experts have reviewed it, and until then the check does not match anything. When it matches, the App does not publish the Card and shows you support resources instead, including the 988 Suicide & Crisis Lifeline and Crisis Text Line. A match is never held against you: it does not count as a violation, it does not affect your standing, and we store neither the Card nor any record of the match that is linked to you. Our server records a log line that names the matched rule but not your Account, and keeps it for up to 7 days.
9. Not available yet
Link to this sectionThe features in this section are not available yet. Each part explains what will change when the feature launches. We will update this policy before we launch any of them.
9.1 AI-assisted moderation
Link to this sectionWe may start using an AI model to help review Cards. If we do:
- the text of a Card, with its category and mood, will be sent to Amazon Bedrock, a service of Amazon Web Services, Inc., in the United States, which will return a suggested decision;
- the result may help decide whether a Card is published, held for a person or refused, whether it is marked as high risk, and whether it shows signs of a crisis;
- the AI model will not be able to publish a Card that our other checks refuse, and if it fails or gives an unclear answer, the Card will go to a person;
- we will keep a record of each automated decision, containing the provider, the model, the version of our instructions, a one-way fingerprint of the text (not the text itself), the result, and the timing and cost of the request, for 3 years; and
- before we start, we will tell you, name the provider and the model, and ask for your permission where the law or the App Store rules require it.
9.2 Push notifications
Link to this sectionThe App does not send push notifications today. If we add them, the App will ask for your permission first. If you agree, Apple's push notification service will give the App a device token, which we will store with your notification preferences so that we can send you notifications, for example when a Card you posted locks. You will be able to turn notifications off in your device's settings. We will keep the token and your preferences until you turn notifications off or the deletion of your Account is complete.
9.3 Purchases
Link to this sectionNothing in the App can be bought today. If we offer purchases:
- Apple will process every purchase, and we will never receive your payment card details, name or billing address;
- Apple will send us information about your purchases: the product, price and currency, the App Store country, the purchase and renewal dates, the renewal status, and the purchase identifier linked to your profile (section 3.3). We will use it to provide what you bought, handle renewals and refunds, and keep records;
- we may use RevenueCat, Inc. to manage purchases. The App contains RevenueCat's software, but it does not use that software today, and the software sends nothing; and
- we will keep purchase records until the deletion of your Account is complete.
9.4 Email codes and password reset
Link to this sectionThe Service does not send automated emails today, and we do not yet confirm that you own the email address you sign up with. When email confirmation and password reset launch:
- What we will send. An email with a 6-digit code that you enter in the App, in three situations: to confirm your email address when you create an Account with it; to confirm an email address that is added to your profile or replaces the one on your Account, for example when you create an Account from a Guest session; and to reset your password after you choose "Forgot password?". Each code works only once and only for a limited time.
- Only messages about your Account. These emails are transactional. They will contain no advertising, no tracking pixels and no tracked links, so we will not learn whether or when you open them or what you click. We will not send you marketing emails unless you agree.
- Who sends them. Resend, the email service of Plus Five Five, Inc., will send them for us as our email service provider. It will process your email address and the messages we send you. It keeps each message and its delivery record for 30 days, and its backups keep copies for up to 7 days after that. We will add it to section 10.1 when these emails start.
9.5 In-app reporting, account deletion and data export
Link to this sectionThese are not available in the App yet. Until they are, use email (Content Policy section 17 and section 18 of this policy). When they launch:
- Reporting. You will be able to report a Card from the App. Those reports will be stored and handled like the reports our service already accepts (sections 3.11 and 8): we will not show who reported a Card to its author or to our moderators, and the reports you made will be deleted when the deletion of your Account is complete.
- Account deletion. You will be able to start deleting your Account in the App, with the same 30-day window described on our Delete your account page.
- Data export. You will be able to download a copy of your information in the App, in a machine-readable format.
10. How we disclose information
Link to this section10.1 Service providers
Link to this sectionWe disclose personal information to companies that provide services to us. They process it on our behalf to provide those services. Apple and Google also provide their sign-in services to you under their own terms and privacy policies (section 20).
| Provider | What it does for us | Information it handles |
|---|---|---|
| Supabase, Inc. | Hosts our database, authentication, server functions, file storage and scheduled jobs, on Amazon Web Services in the us-east-1 region (Northern Virginia, United States) | Everything in section 3, except information that stays on your device and Site request information |
| Amazon Web Services, Inc. | Provides the computing infrastructure that Supabase runs on, and the sign-in service for our staff's moderation console | The same information as Supabase, as its infrastructure provider |
| Apple Inc. | Provides Sign in with Apple, and relays email that we send to Hide My Email addresses (section 20.1) | Apple sign-in details; emails we send to relay addresses |
| Google LLC | Provides Sign in with Google (section 20.2) | The Google sign-in details it sends us when you continue with Google. We send Google no information about how you use Jurvo, although Google knows that you signed in to Jurvo with your Google account |
| Cloudflare, Inc. | Provides DNS, delivery and protection for the Site, and routes email sent to our addresses | Site request information; emails you send us |
| Hostinger | Hosts the Site | Site request information |
| Our email mailbox provider | Receives and stores email sent to our addresses | Emails you send us |
10.2 Other people using Jurvo
Link to this sectionOther people using the App can see your Cards and the profile details described in sections 3.4 and 7. They see your nickname only on your public Cards.
10.3 People you share with
Link to this sectionWhen you share a Verdict or a list, the share image goes to the people, apps and websites you choose, and their own practices apply.
10.4 Legal requests, safety and emergencies
Link to this sectionWe may disclose personal information, including which Account posted an anonymous Card, if we believe in good faith that it is necessary to comply with the law or with valid legal process, such as a subpoena, court order or search warrant; to respond to an emergency involving danger of death or serious physical injury; to protect the rights, property or safety of Jurvo, the people who use it or the public; or to detect, prevent or address fraud, security or technical problems. Unless the law, a court order or someone's safety prevents it, we will try to tell you before we disclose your information in response to legal process, using the email address on your Account. We cannot notify Guests, who have no email address. Our Support page (section 8) explains how we handle requests from law enforcement.
10.5 Reports to NCMEC
Link to this sectionIf we become aware of apparent child sexual exploitation on the Service, we report it to the CyberTipline of the National Center for Missing & Exploited Children (NCMEC), as federal law requires. A report can include the content, information about the account involved and IP addresses. NCMEC may share reports with law enforcement.
10.6 Business transfers
Link to this sectionIf we are involved in a merger, acquisition, financing, reorganization, bankruptcy or sale of all or part of our business or assets, personal information may be transferred as part of that transaction, and this policy will continue to apply to it. We will tell you before your information becomes subject to a different privacy policy.
10.7 At your direction, and aggregated information
Link to this sectionWe disclose personal information when you direct us to or agree to it. We may also publish or share aggregated or de-identified information that does not identify anyone, such as Verdict totals or statistics about how the Service is used. We do not try to re-identify de-identified information.
11. No sale, no sharing for advertising
Link to this section- We do not sell personal information, and we have not sold it in the past 12 months.
- We do not share personal information for cross-context behavioral advertising, and we do not use it for targeted advertising.
- We do not sell or share anyone's personal information, including that of anyone under 16, and we do not sell sensitive personal information or consumer health data.
- We do not disclose personal information to data brokers, or to other companies for their own marketing.
12. Cookies and similar technologies
Link to this section- The App does not set cookies and does not use an advertising identifier. Section 3.13 lists what it stores on your device.
- The Site sets no cookies, keeps no information in your browser's storage, contains no analytics or tracking, and loads nothing from other companies. Cloudflare, which delivers the Site, may set a strictly necessary security cookie in specific situations, such as when it checks whether a visitor is a bot. Our Cookie Notice lists these cookies.
- Global Privacy Control. We treat a Global Privacy Control signal as a request to opt out of the sale and sharing of personal information. Because we do not sell or share personal information, the signal has nothing further to turn off.
- Do Not Track. We do not respond differently to Do Not Track signals, because we do not track anyone across other companies' websites or apps.
13. Security
Link to this section- Information moving between the App or the Site and our servers is encrypted in transit.
- Our database provider encrypts the data it stores.
- Passwords are stored only as one-way cryptographic hashes.
- The keys that give full access to our database stay on our servers. They are never in the App or on the Site.
- Our moderation console requires multi-factor sign-in, gives each staff role only the access it needs, shows moderators an anonymous reference instead of an author's identity, and records every action in an audit log.
- On your device, the App keeps your session in the iOS Keychain and encrypts Votes that are waiting to be sent.
- No security measure is perfect, and we cannot guarantee that information will never be accessed, disclosed or changed without permission. If a security incident affects your personal information, we will notify you and the authorities as the law requires.
- To report a vulnerability, follow our responsible disclosure policy.
14. Processing in the United States
Link to this sectionJurvo is offered only to people who live in the United States (Terms section 2). Our database is hosted in the United States, in the us-east-1 region of Amazon Web Services (Northern Virginia). Some service providers may process information in other countries; for example, Cloudflare handles each request to the Site at a data center near the visitor. If you use the Service from outside the United States, your information is transferred to and processed in the United States.
15. How long we keep information
Link to this sectionWhen a period below ends, we delete the information or remove the link to you, so that it no longer identifies you. Information for features that are not available yet has its own period in section 9.
| Information | How long we keep it |
|---|---|
| Profile, date of birth, settings, alias, account tier and standing | Until the deletion of your Account is complete, about 30 days after we receive your request |
| Sign-in record: your email address, password hash, and Apple or Google sign-in details | Until the deletion of your Account is complete, about 30 days after we receive your request |
| Sign-in sessions, including IP address and user agent | Until you sign out or your Account is deleted; for a Guest, until the Guest profile is deleted (section 5) |
| Cards | While Jurvo operates, or until they are removed. After your Account is deleted, Cards stay without your nickname or any link to your Account |
| Votes | Kept in totals. The link to you is removed when your Account is deleted |
| Skips, Cards shown to you, usage counters, promotional balances, saved Cards, follows and follow requests, notification preferences, reports you made through our service, and open moderation cases about you | Until the deletion of your Account is complete |
| Guest profiles never turned into an Account | Deleted, with their sign-in sessions, after 12 months without activity; their Votes stay in totals without any link |
| Age block | The account and all of its information, including its sign-in record, are deleted within 30 days of the block; a record that an account was blocked, which identifies no one, is kept permanently |
| Moderation decision log and console audit records | 3 years after the action; the link to your Account is removed when your Account is deleted |
| Crisis-language matches | Nothing about you is stored; a server log line without your Account is kept for up to 7 days |
| Content preserved for legal reasons | As long as the matter or the law requires; for reports to NCMEC's CyberTipline, 1 year |
| Emails with us | 3 years after the matter is closed |
| Service logs kept by our database provider, which can include IP addresses and account identifiers | Up to 7 days |
| Backups | Up to 30 days after deletion |
| Site logs kept by Hostinger and Cloudflare | Under those providers' policies; never linked to your Account |
| Copies of your information that we send you | Not kept by us after delivery. We also delete our copy of the email that carried it, so the period for emails with us does not apply to it |
| Information on your device | Until you delete the App, except the sign-in session, the age block marker and the key for offline Votes, which are kept in the iOS Keychain and can survive deleting and reinstalling the App (section 3.13) |
16. Children
Link to this section- Jurvo is not for anyone under 18, and we do not knowingly collect personal information from anyone under 18. Section 6 describes the age check and the block.
- If we learn that someone under 18 has an Account or is using Jurvo as a Guest, we block the account and delete its information as section 6 describes. If we learn that we have collected personal information from a child under 13, we delete it, as the Children's Online Privacy Protection Act requires.
- If you believe that someone under 18 is using Jurvo, email [email protected].
17. Your privacy rights
Link to this sectionWe give the following rights to every user in the United States, whatever state you live in, subject to the exceptions the law allows:
- Access. Ask whether we hold personal information about you; what categories we hold, where they came from, why we use them and the categories of third parties we disclose them to; and get a copy of the specific pieces of information.
- Correction. Ask us to correct inaccurate personal information, such as your nickname or date of birth. We handle a request to correct the date behind an age block like any other correction request: we consider what you tell us and decide whether the information we hold is inaccurate. Because the block records that the date entered showed someone under 18, not your actual age, and we do not keep that date, we will usually find nothing inaccurate to correct, and we do not lift age blocks. We will explain our decision, and you can appeal it (section 18).
- Deletion. Ask us to delete your personal information. Deleting your Account works as our Delete your account page describes. You can also ask us to delete the Cards you posted; we then delete them instead of keeping them without your nickname, unless an exception applies, for example if we must keep a Card for a legal reason.
- Portability. Get a copy of the personal information you gave us in a portable, machine-readable format.
- Opting out. Opt out of the sale of personal information, its sharing for cross-context behavioral advertising, targeted advertising, and profiling in furtherance of decisions with legal or similarly significant effects. We do none of these, but you can still ask, and we will record your request.
- Sensitive personal information. We use sensitive personal information only to provide the Service you ask for, keep it secure and comply with the law, so there is nothing further to limit (section 19.1).
- Withdrawing consent. Where we rely on your consent, you can withdraw it at any time.
- Appeal. Appeal a decision we make about your request (section 18).
- No discrimination. We will not treat you differently, for example by denying you the Service or changing its quality, because you exercised your rights.
We may keep information where the law allows, for example to comply with a legal obligation, protect security, or establish, exercise or defend legal claims. Votes whose link to you has been removed are no longer personal information about you.
18. How to exercise your rights
Link to this section- In the App. Not available yet (section 9.5).
- By email. Email [email protected] with the subject line "Privacy request", from the email address on your Account, and say which right you want to use.
- Verifying your request. We check the request against the email address on your Account. We may ask you to reply from that address, or to confirm details that only the account holder is likely to know, such as your nickname and roughly when you joined. If you use Hide My Email, tell us the relay address your Account uses (section 20.1). If you sign in with Google, the email address on your Account is the address of that Google account, so write from it. We use the information you give us for verification only for that purpose. For requests to delete information or to receive specific pieces of it, we may need more certainty, and we will tell you if we cannot verify your request.
- Authorized agents. Someone you authorize can make a request for you. We will ask for your signed permission and may ask you to confirm your identity with us directly, unless the agent has a valid power of attorney.
- Guests. You do not need to create an Account to make a request. A Guest profile has no email address, so we usually cannot confirm that a request comes from the person who used it, and we may be unable to act on it; if so, we will tell you why. Guest profiles that were never turned into an Account are deleted after 12 months without activity (section 5). If you still have your Guest session, you can also choose to create an Account from it and make your request from that Account's email address, but creating an Account collects an email address, a nickname and a date of birth, which a Guest profile does not have.
- Timing. We confirm that we received your request within 10 business days, and we respond within 45 days of receiving it, however long verification takes. When we act on a request to delete information, the deletion is complete within that time; for Accounts, the 30-day window on our Delete your account page runs from the day we receive the request. If we need more time, we may extend this once by up to 45 more days, and we will tell you why within the first 45 days.
- Cost. Requests are free. Where the law allows, we may decline, or charge a reasonable fee for, requests that are manifestly unfounded or excessive, and we will explain why.
- Appeals. If we decline your request in whole or in part, we will explain why. You can appeal within 60 days by replying to our decision, or by emailing [email protected] with the subject line "Privacy appeal". We will review your appeal and answer in writing within 45 days, explaining our reasons. If we deny your appeal, you can contact the attorney general of your state.
19. State privacy notices
Link to this section19.1 California
Link to this sectionIf you live in California, this section, together with the rest of this policy, is our notice at collection and our privacy policy under the California Consumer Privacy Act (the CCPA).
| Category | What we collect | Sources | Business purposes | How long we keep it | Disclosed to |
|---|---|---|---|---|---|
| Identifiers | Email address, Apple's or Google's identifier for you, nickname, internal account identifiers, IP address and purchase identifier | You, your device, Apple, Google and our systems | Providing the Service, security, moderation, communicating with you and legal compliance | Until the deletion of your Account is complete; sessions until you sign out or your Account is deleted (section 15) | Supabase and Amazon Web Services; Apple, for email we send to relay addresses; Cloudflare, Hostinger and our mailbox provider, for Site requests and emails |
| Personal information described in California Civil Code §1798.80(e) | Your name and a link to your profile picture, if you continue with Google and your Google account has them; and anything of this kind that you choose to write in a Card or an email, such as medical information | Google, and you | Signing you in with Google, and providing the Service you ask for | As section 15 describes for sign-in information, Cards and emails | Supabase and Amazon Web Services; our mailbox provider, for emails |
| Characteristics of protected classifications | Your age, from your date of birth | You | Checking age eligibility | Until the deletion of your Account is complete; for a blocked account, until we delete it within 30 days of the block | Supabase and Amazon Web Services |
| Internet or other electronic network activity | Votes, skips, saved Cards, Cards shown to you, usage counters, session records (IP address and user agent), service logs and Site request logs | You, your device and our systems | Providing the Service, ordering Cards, security, and statistics about the Service | As section 15 describes for each | Supabase and Amazon Web Services; Cloudflare and Hostinger, for Site requests |
| Geolocation data (coarse only) | Your country, from your device's region setting, and your time zone. We do not collect precise location | Your device | Ordering Cards, attaching a country to your Cards, and timing your daily set | Until the deletion of your Account is complete; on your Cards for as long as they exist | Supabase and Amazon Web Services |
| Inferences | That you are 18 or older; category preferences (not stored) | Worked out from your date of birth and your Votes | Registration and ordering Cards | The eligibility record until the deletion of your Account is complete; preferences are not stored | Supabase and Amazon Web Services |
| Sensitive personal information | Your account log-in (email address and password), and anything sensitive you choose to write in a Card or an email, such as information about your health, sex life or sexual orientation, religious or philosophical beliefs, or racial or ethnic origin | You | Providing the Service you ask for, security and legal compliance | As section 15 describes for sign-in information, Cards and emails | Supabase and Amazon Web Services; our mailbox provider, for emails |
| Content you post | Cards | You | Providing the Service | As section 15 describes for Cards | Supabase and Amazon Web Services; shown to other users at your direction |
We do not collect commercial information (nothing can be bought in the App), biometric information, audio or visual information (we keep only the link to a Google profile picture described above, never the picture), professional or employment information, or education information, except anything of those kinds that you choose to write in a Card or an email.
- Disclosures in the past 12 months. In the 12 months before the date of this policy, we disclosed personal information in the categories above for business purposes only to service providers named in section 10.1, each only for the information listed for it there. We have not sold or shared personal information.
- Sensitive personal information. We use and disclose sensitive personal information only for purposes for which the CCPA does not require a right to limit, such as providing the Service you ask for, ensuring security and integrity, and complying with the law. We do not use it to infer characteristics about you.
- Your rights. You have the rights to know, access, delete and correct personal information, to opt out of its sale and sharing, to limit the use of sensitive personal information, and not to be discriminated against for using these rights. Sections 17 and 18 explain how to use them, including through an authorized agent.
- Minors. We do not sell or share the personal information of consumers under 16.
- Financial incentives. We do not offer any.
- Shine the Light. We do not disclose personal information to third parties for their own direct marketing purposes (California Civil Code §1798.83).
- Do Not Track. Section 12 explains how we respond to Do Not Track signals.
- Complaints. You can contact the California Privacy Protection Agency or the California Attorney General.
19.2 Other states with comprehensive privacy laws
Link to this sectionResidents of Colorado, Connecticut, Delaware, Florida, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah and Virginia have rights under the privacy law of their state. We honor those rights as each law grants them, and we give the same rights to residents of every other state. Depending on your state, they include the rights to:
- confirm whether we process your personal data, and access it;
- correct inaccuracies in it;
- delete it;
- get a copy of it in a portable format;
- opt out of targeted advertising, the sale of personal data, and profiling in furtherance of decisions with legal or similarly significant effects (we do none of these);
- get a list of the specific third parties, or the categories of third parties, to which we have disclosed your personal data (section 10.1 names them, and we will give you a list on request); and
- appeal our decision on your request (section 18), and contact your state's attorney general if we deny your appeal.
We also honor universal opt-out signals, such as Global Privacy Control (section 12). We do not use personal data to train large language models. If you choose to include sensitive data in a Card, such as information about your health, we process it only to publish your Card at your direction, provide the Service and keep it safe, and we do not sell it or use it for targeted advertising or profiling.
19.3 Nevada
Link to this sectionWe do not sell covered information as Nevada law (NRS Chapter 603A) defines it. You can still ask us not to sell your covered information by emailing [email protected] with the subject line "Nevada opt-out".
19.4 Consumer health data in Washington and Nevada
Link to this sectionOur Consumer Health Data Privacy Policy explains how we handle consumer health data under Washington's My Health My Data Act and Nevada's consumer health data law, and how to use the rights those laws give you.
20. Sign in with Apple, Sign in with Google and Hide My Email
Link to this section20.1 Sign in with Apple and Hide My Email
Link to this section- With Sign in with Apple, the App asks Apple only for your email address. Apple lets you share your real address or hide it with Hide My Email. If you hide it, Apple gives us a unique, random relay address ending in @privaterelay.appleid.com, which forwards our emails to your real address.
- Apple forwards email to a relay address only from email domains that we have registered with Apple.
- You can stop forwarding, or stop using Sign in with Apple for Jurvo, in your Apple Account settings under Sign in with Apple. This does not delete your Account; to delete it, see section 18. If you stop forwarding, we cannot reach you by email.
- If you write to us from your real address, tell us the relay address your Account uses so that we can find your Account. You can find it in your Apple Account settings under Sign in with Apple.
- Apple's privacy policy covers how Apple handles your information.
20.2 Sign in with Google
Link to this sectionThese disclosures describe how Jurvo accesses, uses, stores and shares the information it receives from Google, as Google's API Services User Data Policy requires.
- What we receive. When you continue with Google and agree on Google's consent screen, Google gives us your Google account's unique identifier, your email address and whether Google has verified it, and, if your Google account has them, your name and a link to your profile picture. For a Google Workspace account, Google also tells us the account's domain. The App asks only for Google's basic sign-in permissions, not for access to your Gmail, contacts, calendar, files or any other Google data, and we use Google only to sign you in.
- How we use it. Only to create your Account, sign you in, keep your Account secure and recognize you when you contact us. The App does not show your Google name or picture to anyone, including you. We do not use information from Google for advertising, do not sell it, and do not use it to train AI models.
- How we store it. Our authentication provider, Supabase, stores it with your sign-in record in the United States, protected as section 13 describes. That includes your name and the link to your picture, although the App never shows them. We keep it until the deletion of your Account is complete (section 15).
- Who we share it with. No one, except the service providers that host the Service for us (section 10.1), or where the law requires it (section 10.4).
- Your control. You can remove Jurvo's access at any time in your Google Account settings, at myaccount.google.com/permissions. Removing access does not delete your Account or the information we already hold; to delete them, see section 18.
- Limited Use. Jurvo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Google's privacy policy covers how Google handles your information.
21. Changes to this policy
Link to this sectionWe may update this policy. When we do, we will post the updated policy on the Site and change the date shown at the top of it. If a change is material, we will tell you at least 30 days before it takes effect, by email to the address on your Account or by a notice in the App. Where the law requires, we will ask for your consent before we use personal information we already hold in a materially different way. We review this policy at least once a year.
22. Contact us
Link to this section- Privacy questions and requests: [email protected]
- Other questions: [email protected]
- Mail: PuredLab LLC, Attn: Privacy, 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, United States
If you have a disability and need this policy in another format, email [email protected] and we will provide it.