Privacy policy

Last updated October 14, 2026

Who we are

BlueCheck is a work app for small businesses: projects, contacts, calendar, boards, time tracking and reports at app.bluecheck.tech. It is run by Family Fund Inc., which does business as BlueCheck. In this policy, "we" means Family Fund Inc.

One BlueCheck account also works with other BlueCheck services, such as BlueCheck ID. This policy covers the BlueCheck work app, including the BlueCheck connector that lets AI apps such as Claude work in your account (see Connected AI apps).

If you have a question about this policy or your data, email support@bluecheck.tech.

What we collect

What you give us

Account details: your email address, your first and last name, and a profile photo if you add one. Your password is stored by our sign-in provider, Supabase, only as a one-way hash. Our server passes it to Supabase when you sign in or change it and never stores it.
Your agreement: each time you sign in, you tick a box to agree to the terms and this policy. We keep which versions you agreed to, when you first agreed to each, and when you last did.
News and updates: if you ask for news and updates from BlueCheck, on the sign-in screen or in Settings > Profile, we keep your email address, that you asked, where you asked and when. If you turn them off, we keep when you did.
Your weather place, if you set one in Settings > Weather while signed in: the ZIP code, the town it belongs to and its map coordinates, and whether you read Fahrenheit or Celsius. We keep it with your account so every device you sign in on shows the same weather. Only you can see it.
Your app choices: which apps you turned on or off in Settings > Apps, and when. We keep them with your account so every device you sign in on shows the same apps. Only you can see them. Turning an app off hides it; it does not delete anything you made in it.
Your team: the names and email addresses of people you invite, and each person's role and which apps they can open.
The demo: if you open the BlueCheck demo through its share link, we make a separate demo login for you on the demo team. You do not have to sign in first. If you are not signed in, that demo login belongs to no account, and we delete it after 7 days without use. The other people in the demo see it as "Demo visitor", never your name or profile photo, but they can see what you add there, such as cards and comments. Your own account does not join the demo, and nothing you do in the demo reaches it.
Your work: projects, estimates and rates, contacts, calendar entries, boards, cards, checklists, comments, @mentions and time entries.
Route my day: the map coordinates we find for the addresses on your cards and calendar blocks when you plan a route with them, so the next plan does not look them up again. Changing an address clears them. If you choose Use my location, your browser's position is used for that one plan and is not stored.
Information about other people that you add, such as a contact's name, company, job title, email, phone number, address, website and notes.
Mail, if your team uses BlueCheck Mail: the messages you send and receive and their attachments, your addresses, aliases, signatures, drafts and scheduled messages. See Mail.
Mail sorting: your mail categories and rules, where each message was sorted for you, and the bill details read from finance mail (see Mail sorting).
Files you attach, voice notes, video clips and photos. Files are kept exactly as you upload them, so a photo may still contain the place and time it was taken. Photos taken with the in-app camera are re-encoded without that data.
Dictation: when you speak into a text field, we receive the audio and the last few words already in that field, which helps the speech-to-text get names right.
Bug reports: your description, the address of the page you were on, your browser type, language, window size and theme, and your user id if you are signed in. Bug reports do not include a screenshot.
Payments: you enter card details on Stripe's own checkout page. They never pass through our servers.

What we collect automatically

Error reports: when something breaks in the app, your browser sends us the error message and technical details, the part of the app it happened in, your browser type and, if you are signed in, your user id.
Sign-in records: if you choose "Stay signed in", we keep a random id for your device and your browser type for 30 days so we can skip the emailed code on that device.
Activity dates: when you signed up, when you last signed in and were last active, and counts of your recent actions. We use these to run and support the service.
Request logs: our hosting providers keep short-lived technical logs of requests, such as IP address, time and the address requested. We use your IP address briefly to limit repeated sign-in attempts. We do not store it in our database.
Connector logs: when an AI app you connected uses BlueCheck for you, our server logs which tool it used, whether it worked, how long it took, your user id and the app's id. If something fails on our side, it also logs the technical error. These logs do not include what the app asked for or what we sent back.
Action records: when you change something in BlueCheck, or when the BlueCheck command-line tool or an AI app you connected reads or changes something for you, we record your user id, your team account, where the request came from (the app, the command-line tool, an AI app or voice), the connected app's id, the kind of action (for example, moving a card), the id of the item it acted on, whether it worked, how long it took, and a one-way fingerprint of the request. We do not record what you typed or what we sent back. Reading your work in the app itself is not recorded.
Access keys: when you sign in to the BlueCheck command-line tool or connect an AI app, we keep a record of that access: which app it is, when it was created, last used and when it expires or was turned off, and a count of its recent requests so we can limit them. The key itself is held by our sign-in provider, Supabase, and is not stored in this record.
Usage records: when a feature uses an outside service or a resource we pay for by use, such as an AI model, we record your user id, your team account, the feature, the service and model, how much was used (for example, how much text or audio was processed), what it cost us, and the action that caused it. We do not record what was sent to the service or what it returned.

What we get from other services

If you sign in with Google, Google tells us your name, email address and a link to your Google profile picture.
If you connect a Google account in Settings > Connected accounts, Google tells us that account's email address, Google's id for it and the permissions you granted, and gives us keys to act for you. See Connected Google accounts.
Stripe tells us about your subscription, payments and invoices. These records can include your billing name and address and your card's brand and last four digits.
If you connect an AI app, it sends us the requests you ask it to make, such as words to search for or the text of a card to create. See Connected AI apps.

How we use it

To run BlueCheck: sign you in, save and show your work, share it with the people you choose, and send the emails you ask for, such as team invites and sign-in codes.
To keep accounts safe: 2-Step sign-in codes, limits on repeated attempts, limits on how many requests each access key can make, spotting unusual activity such as many deletions in a short time, and looking into abuse.
To bill your account through Stripe.
To keep a record that you agreed to the terms and this policy.
To send you news and updates about BlueCheck, such as new features, tips and offers, only if you asked for them. You can turn them off at any time.
To fix problems and improve the app, using error reports, bug reports and activity counts.
To see what BlueCheck and each of its features cost to run, using action and usage records.
To answer requests from AI apps you connect, using only what each request needs.
To plan your day's route in Calendar: OpenStreetMap puts addresses on the map, and Anthropic's Claude sets the order unless you turn AI off for the plan (see Service providers).
To sort your mail into your categories, with Anthropic's Claude for what your rules cannot place unless you turn that off (see Mail sorting).
To answer you when you contact us.

We do not sell your personal information. We do not show ads, use advertising or analytics trackers, or share your data for advertising. We do not use your content to train AI models. Speech-to-text runs on a server we run ourselves.

When you add information about other people, such as your contacts, you are responsible for having the right to share it with us. We handle it only to provide BlueCheck to you and your team.

Who can see your information

Your team. Everyone on your BlueCheck account can see the account's projects and contacts, with each contact's details and notes, project calendar entries, files on projects and contacts, items in the team's trash, and the member list with names and emails. Owners, admins and managers can see everyone's time entries and reports on the account. Members and viewers see only their own. Projects, contacts and time entries belong to the account: when someone leaves the team, what they added there stays with the team, and they no longer see it.
Mailbox members. Only the people an owner or admin adds to a mailbox or shared mailbox can read its mail, and only while they are on the team. A viewer on the team can read a mailbox they are in but cannot change it or send from it. Owners and admins manage the team's domains, mailboxes and who is in them. A personal mailbox has one person, and only the team's owner can give it to someone else while that person is still on the team. The people in a shared mailbox are told when someone is added or removed.
Only you. Your own calendar and your notifications are private to you, unless you link a calendar entry to a shared project.
Board members. A board is shared with the people added to it, who may belong to other BlueCheck accounts. They see the board's cards, comments, files and voice notes, and every member's name and email address.
AI apps you connect. If you connect an app such as Claude, it receives what its requests return from your BlueCheck account. See Connected AI apps.
Profile photos. Your photo is stored at a public web address so it can appear in the app. Anyone who has that address can view it.
Action and usage records. You can see your own action records through the BlueCheck command-line tool or a connected AI app. Your team account's owner can see the action records of everyone on the account. The people who run BlueCheck can see all action and usage records, to keep the service safe, fix problems and see what it costs to run.
The people who run BlueCheck. A small number of our people can see account records, such as names, email addresses, sign-up and last-active dates, plan and billing status, bug reports and error reports, and the list of people who asked for news and updates. We look at the content of your work only when you ask us to for support, or when we must for security or the law.
When the law requires it, or to protect people's safety or our rights, we may share information with authorities. If BlueCheck is sold or merged, your information would move to the new owner under this policy.

Service providers

We use these companies to run BlueCheck. Each gets only what it needs for its job.

Supabase: Database, sign-in and profile photos. Holds your account and all of your work data, and the keys and approval records of AI apps you connect.
Vercel: Hosts the app and runs its server code. Keeps the short-lived request and connector logs.
Cloudflare: Stores attachments, voice notes, video clips and document previews (Cloudflare R2), and routes email sent to our bluecheck.tech addresses.
Resend: Sends our emails, such as team invites, sign-in codes and the news and updates you asked for. It receives the recipient's email address and the message. For teams that use BlueCheck Mail, it also sends and receives their mail on their own domains: it receives each message, its sender and recipients and its attachments, and tells us when an address bounces or reports mail as spam.
Stripe: Takes payments and manages subscriptions. We send it your email address, name, account id, plan and number of seats.
Google: Sign-in, if you choose Continue with Google. If you connect a Google account, our server calls Google's services for the products you turned on, with that account's keys; with Calendar on, your calendar blocks go to the Google calendar you picked. Some of our emails also load a font from Google when you open them, which shows Google your IP address.
Hostinger: Hosts our own server for speech-to-text and for turning office documents into previews. Audio and documents are processed there and not stored.
Open-Meteo and the US National Weather Service: Weather in the top bar. Your browser sends the ZIP code you enter to Open-Meteo to find the place. Our server sends rounded coordinates, never your identity, to get the weather.
BlueCheck ID: Our own sign-in service. If you use an authenticator app for 2-Step, it checks the 6-digit code and receives your IP address and browser type.
Anthropic: AI sorting in Mail, unless you turn it off. For a message your rules cannot place, our server sends Anthropic's Claude API the sender, the subject, the first 2,000 characters of the text and the names of your mail categories. Never attachments. A shared mailbox's mail is sent only when everyone on it has AI sorting on, and Gmail mail only after you turn it on yourself. See Mail sorting. Also the order of Route my day, unless you turn AI off for a plan: our server sends the day, the time you leave, each stop's title, address, booked time, length and the first 300 characters of its notes, the start and end as you typed them ("My location" if you used your position) and the driving times between the stops. Claude answers with the order, the earliest time a note allows for a stop, and a short reason for some stops.
OpenStreetMap Foundation: Puts addresses on the map for Route my day, through its Nominatim service. When you plan a route, our server sends it the addresses that are not on the map yet and the start or end you typed, with a rough area of about 10 km to prefer nearby matches. It never receives your name, your account or your position, and sees only our server's IP address.

Connected AI apps

You can connect an AI app, such as Claude from Anthropic, to your BlueCheck account through the BlueCheck connector. Nothing is shared until you sign in to BlueCheck and choose Authorize. The app then has the same access you have in BlueCheck and never more. It sees only what you can see, and if your team level is viewer it can change only your own stars, watches, timer and notifications, and the mail in a mailbox of your own that is not your team's. It loses its tools for an app you turn off in Settings > Apps, though Trash, notifications, files and time entries can still show items from that app. The connector guide lists every tool it can use.

What the app can read and change

The app can read your projects, contacts, boards, cards, calendar, time entries, time reports, notifications and trash. When you ask, it can add boards and lists; add and change projects, contacts, cards, checklist items, calendar entries and time entries; post comments; start and stop your timer; mark notifications read; delete cards, calendar entries and time entries; and restore items from the trash. Cards, calendar entries and time entries it deletes go to the trash. Checklist items it removes, and timer runs it stops less than a minute after they started, are deleted right away. The app cannot change billing, invite or remove people, or change anyone's team access.

If your team uses BlueCheck Mail and Mail is on for you, the app can also read the mail in the mailboxes you are a member of, your mail accounts and addresses, and your Bills to pay. When you ask, it can draft, send and answer email from your own addresses, move mail between folders and categories, and mark bills paid. Mail it sends goes out the same way as mail you send yourself (see Mail).

What the app receives

When you ask the app to do something in BlueCheck, it sends us a request and we send back the result. Depending on what you ask, the result can include your name and email address; your account's trial or subscription status; the names and team levels of your team members, and the names of the people on your boards (or their email addresses, if they have not set a name); projects with their contacts, rates and estimates; contacts' details and notes; boards, lists, cards, checklists and comments; calendar entries; time entries and time reports; your notifications; and items in the trash. If you use its Mail tools, it can also include the messages it reads (sender, recipients, subject, date and text, and the names and sizes of attachments), your mail accounts and addresses, and your bills with their amounts and due dates. It never includes files, the contents of attachments, voice notes, video clips, photos or payment details.

Once the app receives this information, the company that makes the app handles it under its own terms and privacy policy, for example Anthropic's for Claude and OpenAI's for ChatGPT. That company may keep it, for example in your chat history. We do not control what it does with it. The results can include information about other people, such as your contacts and teammates and the people who write to you, so connect an app only if you are allowed to share that information with it.

What we receive and keep

Sign-in: when you choose Authorize, our sign-in provider, Supabase, gives the app a key that works only for your account and keeps a record that you approved that app. The key tells us your user id and email address. The app never sees your password.
Requests: each request carries only what that task needs, such as words to search for or the text of a card you asked for. We do not receive your conversation with the app or anything from other tools you use in it.
Your changes: anything you ask the app to create, change or delete is saved in BlueCheck the same way as a change you make yourself, and your team sees it the same way.
Action records and limits: each request the app makes is also written to our action records (see What we collect), and each connected app may make up to 120 requests a minute and 2,000 an hour.
Logs: each time the app uses a tool, our server writes one log line with the tool used, whether it worked, how long it took, your user id and the app's id, plus the technical error if something failed on our side. It does not log what you asked for or what we sent back. Our hosting provider, Vercel, keeps these logs for a short time set by our hosting plan and then deletes them.
We do not sell this information or use it to train AI models.

Disconnecting

You can disconnect at any time in the AI app. In Claude, open Customize > Connectors, choose BlueCheck and disconnect or remove it. The app then stops sending us requests. We keep our record that you approved the app, so connecting again later can skip the Authorize step. To have us delete that record and end the app's access on our side as well, email support@bluecheck.tech. Deleting your BlueCheck account ends every connection.

Connected Google accounts

In Settings > Connected accounts you can connect one or more Google accounts. Google asks you first, and asks again for each product when you turn it on. Calendar asks to see and edit events on your calendars, see the list of your calendars, and make and keep a calendar named BlueCheck. Gmail, where it is offered, asks to read, label, archive, trash and send your mail. We never ask for full access to your Gmail account.

What we keep

The Google account's email address and Google's id for it.
The permissions Google granted, the products you turned on, when the account last synced, and the last sync problem in plain words.
The keys Google gives us to act for you. Our server encrypts them before it stores them. They never reach your browser or our logs.
Sync bookmarks and the ids of Google's change notifications, so we fetch only what changed.

Google Calendar

When Calendar is on for an account, BlueCheck keeps your BlueCheck calendar and the Google calendars you chose in step:

From Google: the events of the calendars you tick in Settings > Connected accounts, copied into your BlueCheck calendar with their title, day and times, description as text, reminders, which calendar they come from and Google's ids for them. A repeating event comes in as one copy per day it happens, from one year back to two years ahead.
To Google: your calendar blocks from 30 days back, and every block you make after, project blocks included, go to the calendar you pick (a new calendar named BlueCheck, or your primary calendar) with their title, times, note, project name, reminders, a link back to the block and the block's BlueCheck id, which Google keeps with the event. Edits and deletes go both ways. Anyone you share that calendar with in Google sees them.
The list of your Google calendars: each one's name, colour, your access to it, its time zone and its default reminders, whether you ticked it and whether it shows in Calendar.
Your time zone from your Google Calendar, to place times and to show reminders in the bell when they are due. It is deleted when no account of yours has Calendar on any more. The block editor also keeps your browser's time zone for reminders.
When a calendar changes, Google tells our server so we fetch the change. That notice carries no event content.

Copies of Google events stay while the calendar is ticked, Calendar is on and the account is connected. Unticking a calendar, or turning Calendar off for the account, deletes its copies from BlueCheck at once; Google keeps the events. An event deleted in Google goes to Settings > Trash in BlueCheck and is deleted for good 30 days later.

Copies are ordinary blocks in your calendar: the BlueCheck connector, the command-line tool and AI apps you connect can read and change them like any block, and teammates see a copy you tie to a team project on that project's page.

Only you can see your connected accounts. Calendar and Gmail data from Google is used only to provide the features you turned on. We do not use it for advertising, we do not sell it, we do not use it to train AI models, and our people do not read it unless you ask us to, it is needed for security, or the law requires it. Mail from a connected Gmail account that an AI app reads for you, at your request, goes to that app's maker (see Connected AI apps).

BlueCheck's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting

Disconnect in Settings > Connected accounts removes BlueCheck's access at Google and deletes the stored keys and the account record. It also deletes every copy of that account's Google events from BlueCheck with their reminders in the bell, the links between your blocks and Google, the account's calendar list and choices, and the time zone read from Google when no other account of yours has Calendar on, and stops Google's change notices. Blocks you made in BlueCheck stay in BlueCheck, and the events BlueCheck wrote to your Google calendar stay in Google, where you can delete them or the calendar named BlueCheck. You can also remove BlueCheck from your Google account at myaccount.google.com/permissions; BlueCheck then shows Reconnect for that account.

Mail

BlueCheck Mail lets a team send and receive email on its own domain. It is available only where an owner or admin has set it up.

What we store: the messages in each mailbox (sender, recipients, subject, the text and HTML of the message, some headers such as list and unsubscribe information, and dates), their attachments (in Cloudflare R2, up to 25 MB each and 40 MB per message; a larger one is listed by name but not stored), the mailbox's addresses and aliases, each person's signatures, labels, stars and read state, drafts and scheduled messages, how many messages each mailbox sent each day, the team's domains with their DNS records and status, and the team's suppression list: addresses that bounced or reported its mail as spam, which BlueCheck will not send to.
How mail moves: mail is sent and received through Resend (see Service providers). Incoming mail reaches us from Resend; outgoing mail goes to Resend with its recipients and attachments. Resend keeps its own copy of each message for its retention period.
Images: pictures that a message loads from the internet stay hidden until you choose Show images. Then our server fetches them for you, so the sender sees our server, not your address, but can still tell the message was opened. Your browser sends each image address to our server inside the request, not in the link, so it stays out of request logs.
Mail is shown in a protected frame that does not run anything the sender put in the message.
AI apps you connect: if you use the connector's Mail tools, the app receives the mail it reads for you and can send mail from your addresses when you ask (see Connected AI apps).

Mail sorting

Mail sorts each message you receive into one of your categories, such as Finance > Bills to pay or Personal > Contacts. In a mailbox you share, each person has their own categories, rules, sorting results and bills, and the others on the mailbox do not see them. The bill details read from a message (vendor, amount, due date and invoice number) belong to the message, so everyone who can read that mailbox sees them.

What we keep

Your categories, your rules, whether AI sorting is on and whether you turned it on yourself, and where each message was sorted for you: by one of your rules, by a built-in signal, by AI or by hand.
Facts from finance mail: the vendor, amount, due date and invoice number, read from the subject, the text and the names of attachments. We do not read inside attachments for this.
Bills to pay: which bills you marked paid and when, and the calendar block you added for a bill.
To file mail from your contacts and teammates, we compare the sender's address with your contacts' email addresses and your team's sign-in addresses, but only when the sender passed the email checks that show the address is real. This happens in our database and sends nothing anywhere.

AI sorting

When AI sorting is on and your rules and our built-in signals cannot place a message, our server sends Anthropic's Claude API the sender's name and address, the subject, the first 2,000 characters of the text and the names of your categories. It never sends attachments, the other recipients or who you are. In a mailbox you share, a message is sent only when everyone on that mailbox has AI sorting on. Mail from a Gmail account is sent only after you turn AI sorting on yourself in Settings > Mail > Sorting. Claude answers with one of your categories, or with none, and then the message stays unsorted in your inbox. Anthropic does not use this to train its models and keeps it only as long as its commercial API terms allow.

AI sorting is on unless you turn it off in Settings > Mail > Sorting. Turned off, only your rules and our built-in signals sort your mail, and nothing from your mailboxes is sent to Anthropic.

Gmail in Mail

Where BlueCheck offers it, which is only after Google has reviewed how BlueCheck uses Gmail, you can turn Gmail on for a connected Google account. Its mail then shows in Mail beside your team's mailboxes. Only you can see it.

What we copy: for mail from the last 30 days (up to 500 messages) and new mail after that, the sender, recipients, reply-to address, subject, date, Gmail's short preview, whether it has attachments, the message's Gmail labels, and some headers: Delivered-To and X-Original-To (to pick the address a reply goes out from), Message-ID, In-Reply-To and References (to keep threads together), list and unsubscribe information, and Gmail's own check of the sender. When you open a message we copy its text and HTML, with its inline pictures stored inside the HTML, and the names, types and sizes of its attachments; an attachment itself is copied when you load it (stored in Cloudflare R2). We also copy your Gmail address and your verified send-as addresses with their signatures.
What changes in Gmail: what you do to Gmail mail in BlueCheck (read, star, archive, labels, spam, trash) is done in Gmail too, and mail you send from a Gmail address goes out through Gmail, so it is in Gmail's Sent. If you turn on Mirror categories to Gmail labels in Settings > Mail > Accounts, BlueCheck adds labels named BlueCheck/<Category>/<Subcategory> to your sorted Gmail messages. Turning it off stops new labels and leaves the ones already in Gmail.
Turning Gmail off, or disconnecting the Google account, deletes from BlueCheck everything copied from that Gmail account: its messages, threads, attachment records and stored attachments, sorting results, drafts from its addresses, and the addresses. Your mail in Gmail does not change. Turning Gmail off keeps BlueCheck's permission at Google until you choose Disconnect.
If BlueCheck loses access to your Gmail, or Mail is no longer open to you, the copy is deleted after 30 days unless you reconnect.
Delete forever and Empty Trash on Gmail mail remove BlueCheck's copy only. Gmail keeps those messages in its Trash until it empties it.
Gmail mail goes to AI sorting only after you turn AI sorting on yourself (see Mail sorting). It is never used for advertising or to train AI models, and the Limited Use rules above apply.

Cookies and browser storage

We use cookies only to keep you signed in. The sign-in cookie cannot be read by the page's scripts. During Google sign-in a second, short-lived cookie holds a one-time check value. While you sign in with Google or Microsoft, a cookie that lasts up to 15 minutes holds that you agreed to the terms and this policy and whether you asked for news and updates, so we can record them when you come back. Coming back deletes it. While you connect a Google account, a cookie that page scripts cannot read holds an encrypted one-time check value for up to 10 minutes. While you use the demo, another cookie that page scripts cannot read keeps your own sign-in, so Go to my account can bring it back. Going back to your account or signing out deletes it.

Your browser also stores your settings on your device: theme, wallpaper, dashboard layout, sticky notes, the weather place you chose, pinned boards, sound choices, the start, end, leave time and AI choice of Route my day, and a random device id. This stays in your browser and is not sent to us unless a feature needs it.

We do not use advertising or analytics cookies.

How long we keep it

Your account and work data: for as long as your account exists.
Deleted items: projects, contacts, boards, lists, cards, calendar entries and time entries go to Settings > Trash, where they can be restored for 30 days. After that, a nightly job deletes them for good, except a project that still has logged hours or a contact that still has projects, which stays until that changes. The person who deleted an item, or an owner, admin or manager, can delete most items forever sooner. Checklist items you remove and timer runs shorter than a minute are deleted right away and never go to the trash.
Mail: messages and attachments stay until someone in the mailbox deletes them, and so do drafts, messages that failed to send, and Spam. Mail moved to Trash is deleted for good after 30 days, or sooner when someone empties Trash, and its attachments are erased from storage within a day after that. When a person leaves the team, the mail in the team's mailboxes stays with the team; an owner or admin can remove a mailbox, which deletes its mail. A domain that is not verified within 3 days is removed. Resend keeps its own copy of each message for its retention period. Records of sent or stopped messages in the send queue: 30 days. Daily send counts: 60 days. The suppression list: for as long as the team account exists.
Connected AI apps: our record that you approved an app stays until you ask us to delete it or you delete your account.
Connected Google accounts: the account record, its keys and its sync bookmarks stay until you disconnect the account or delete your BlueCheck account. Copies of Google Calendar events stay until you untick their calendar, turn Calendar off or disconnect the account; a record that a reminder was shown stays 60 days.
Mail sorting: your categories, rules and settings for as long as your account exists; a message's sorting, facts and bill for as long as the message is in Mail.
Mail copied from Gmail: until it is deleted in Gmail, or until you turn Gmail off or disconnect the account, when it is deleted here. If BlueCheck loses access to your Gmail, or Mail is no longer open to you, the copy is deleted after 30 days unless you reconnect. Gmail mail in Trash is deleted here after 30 days, as Gmail does.
Map coordinates of addresses on cards and calendar blocks: until the address changes or the card or block is deleted for good.
Connector logs: a short time, set by our hosting plan.
Action records, usage records and access key records: for as long as your account exists. We never edit action or usage records. An access key record changes only when the key is used or turned off. When your account is deleted, they are deleted with it.
Deleted files: a file disappears from the app as soon as you remove it. A stored copy can remain with our storage provider until we erase it. If you want a file erased, email us.
Sign-in codes: 10 minutes. "Stay signed in" device records: 30 days.
Your agreement to the terms and this policy, and your news and updates choice with its dates: for as long as your account exists. When your account is deleted, they are deleted with it.
Error reports: about 30 days. Bug reports: until we no longer need them to fix the problem.
Billing records, including the events Stripe sends us: as long as we need them for accounting and tax.

Your choices and rights

You can see and change your name, photo, weather place, the apps you use and whether we send you news and updates in Settings, and change or remove your work at any time. Every news and updates email also has a link to stop them. You can disconnect an AI app at any time (see Connected AI apps).

To get a copy of your data, correct it, or delete your account, email support@bluecheck.tech from the address on your account. We answer within 30 days. When we delete your account, we delete your profile and the data that only you own. Work you added to a team's projects or boards belongs to that team and stays with it. We keep billing records as the law requires.

Depending on where you live, you may have more rights, such as the right to object to some uses or to complain to a regulator. Email us and we will help.

Security

Data travels over encrypted connections, and our providers encrypt stored data. Database rules limit each person to their own and their team's data. Sign-in uses cookies that page scripts cannot read, and 2-Step sign-in sends a code by email or uses an authenticator app. Files are stored privately and shared through links that expire.

No system is perfectly secure. If we learn of a breach that affects your information, we will tell you as the law requires.

To report a security problem in BlueCheck, email security@bluecheck.tech.

Children

BlueCheck is a business tool and is not meant for anyone under 16. We do not knowingly collect information from children. If you think a child has given us information, email us and we will delete it.

Where your data is stored

We and our main providers store and process data in the United States. If you use BlueCheck from another country, your information is sent to the United States.

Changes to this policy

When we change this policy we update the date at the top. If a change affects how we use information you already gave us, we tell you in the app or by email before it takes effect.

Contact us

Family Fund Inc., doing business as BlueCheck. Email support@bluecheck.tech.

To report a security problem, email security@bluecheck.tech.