Legal
Privacy Policy
Last updated: November 5, 2026 · Effective: July 25, 2026
Who we are
Just Frank is a community platform operated by JustFrank Holdings Inc., a Canadian corporation. Just Frank powers private communities, each led by a community owner (a “Host”). This policy covers both the Just Frank platform and the Just Frank mobile app.
Contact: hello@itsjustfrank.com
Mailing address: JustFrank Holdings Inc., Suite 202, 1965 West 4th Avenue, Vancouver, BC V6J 1M8, Canada.
Plain-language summary
- You create a profile to use Just Frank. We store the data you give us.
- Content you post (feed posts, comments, journal entries, dharma reviews, messages) is stored so the app can work. Who can see it depends on where you posted it.
- We use AI (“Frank” and other community AIs) to help you. Your conversations with AI are processed by a third party (Anthropic) and stored so the AI has context. Making pictures and videos, and writing out speech, uses the other AI services named in section 3.
- If a business calls or texts you through Just Frank, the call and texts are carried by Telnyx. A call is kept as a recording only if you say yes on the call, leave a voicemail, or talk to the business’s AI assistant, which tells you first (section 4b).
- We use analytics and session recordings to understand how the app is used, and they are linked to your account — not anonymous. Form inputs are always masked. We don’t sell your data.
- You can request deletion of your account and data at any time.
1. Data we collect
Account data
Email address, name, profile photo, username, bio, and other profile fields you choose to fill in.
Content
Anything you post, write, send, or upload inside Just Frank: posts, comments, direct messages, reactions, journal entries, dharma reviews, loop entries, voice notes, photos, calendar events, scheduler bookings, and notes. For a business: the files its team keeps in Storage, including photos and videos backed up from the owner’s iPhone (section 4c).
Phone calls and texts
If a business uses Just Frank to call or text you: your phone number, when the call or text happened and how long a call lasted, the texts themselves, and, when a recording is kept, the recording, a written transcript and a short summary. See section 4b for when that is.
AI conversations
Your messages to Frank (or your community’s AI), the AI’s responses, and the context it uses to answer you (e.g. recent posts, classroom progress, journal entries — scope depends on the feature and your privacy settings). We retain conversation history so the AI has memory across sessions.
Community membership
Which communities you belong to, your role (member, admin, owner), when you joined, and your engagement level.
Device data
When you use the Just Frank mobile app (iOS or Android): your device type, OS version, app version, crash reports, and push notification tokens (if you enable push).
Usage data
Pages viewed, features used, session duration, and product analytics events (e.g. post_created, dharma_review_submitted). Used to improve the product. These events are linked to your account, including your email address and name — they are not anonymous.
Session recordings
We record how you interact with Just Frank — your clicks, navigation, and scrolling — so we can diagnose bugs and understand where people get stuck. These recordings are linked to your account.
What we never record: everything you type into a form is masked before it leaves your browser. That includes passwords, email fields, and any field we have marked sensitive. We do not capture the contents of your form inputs.
If your browser sends a Do Not Track signal, we do not record you at all.
Analytics provider
Analytics and session recordings are processed by PostHog, on servers in the United States. They process this data only on our behalf.
Cookies and local storage
Essential cookies keep you signed in, keep the app secure, and remember a few simple settings (your session, CSRF protection, two-factor, your light/dark preference, and the last lesson you opened in each course, kept for a year so the course reopens where you left off). These are required for Just Frank to work at all, so they are always on.
Everything else depends on where you are. The non-essential ones are:
- Analytics and session recordings (PostHog) — a cookie and a stored identifier that let us see how the product is used and replay how you moved through it. These are linked to your account.
- Marketing attribution — a first-party cookie, kept for 60 days, that records which link brought you to a community so the right person is credited if you join.
- Ad measurement. On Just Frank’s own marketing pages (such as the home page, pricing and sign-up) we run Meta’s pixel so we can see which of our own ads bring in new businesses. Meta sets its own cookie (
_fbp). When someone who came from one of our ads starts a trial or pays for a Just Frank plan, our server tells Meta, with that person’s email address scrambled (hashed) so Meta can match it but not read it. A business can also put its own Meta pixel, TikTok pixel or Google tag on its own community pages to measure its own ads (see section 3e).
In the European Union, the EEA, the United Kingdom, Switzerland and Quebec, or when we cannot tell where you are, we ask first and none of these run until you say yes. If you decline, none of them are set.
Everywhere else (including the rest of Canada and the United States), they run from your first visit and a bar at the bottom of the page says so. One click on “Opt out” turns them off, and they stay off.
Changing your mind: signed in, go to your account’s Security page and use the Cookies row to turn them off or back on. Clearing your browser’s storage for this site also resets your choice. If your browser sends a Global Privacy Control signal, or a Do Not Track signal, we treat that as a “no” everywhere and never run them. We never sell your data.
Fonts and embedded videos are served in a way that does not contact third parties before you consent: we serve web fonts from our own servers, and YouTube embeds use YouTube’s privacy-enhanced mode, which sets no advertising cookies unless you press play.
Payment data
If your host charges for your community, payment is processed by Stripe. We receive only the minimum needed (subscription status, last-4 of card, country). We never see your full card number.
Connected services
If you connect Google Calendar (via the Just Frank Calendar feature), we receive calendar events you choose to sync, per the scope you grant. See §3b for our Google API Services Limited Use disclosure.
If a community admin connects a Facebook Page or Instagram Business account via the Just Frank → Meta integration, we receive the IDs and names of the Pages and Instagram Business accounts they grant access to, and the granted permission scopes. Just Frank holds the access token itself, encrypted at rest. See §3a for who holds the connection and how. We do not receive contact lists, friends lists, or any data outside the granted scopes.
What we do NOT collect
Precise location, contacts, health data, advertising identifiers, or biometric data. (Face ID / fingerprint unlock happens entirely on your device’s secure enclave; we never see the biometric template.) We never ask your device where you are. A photo or video you upload is stored as the file is, so it keeps any location your camera saved inside it.
2. How we use your data
- Provide the Just Frank platform and app
- Power AI assistance (Frank and community AIs) with your context
- Send notifications you opted into (in-app, email, push)
- Improve the product (analytics, feature usage)
- Keep Just Frank secure (fraud detection, abuse prevention)
- Comply with legal obligations
We do not sell your data. We do not use your content to train AI models. Our main AI processor (Anthropic) is bound to process data only on our behalf and not train on it. The picture, video and speech services in section 3 are covered in section 4d.
3. Who sees your data
Inside your community: hosts, moderators, and other members can see content based on where you post it. A post in the main feed is visible to all community members; a direct message is visible only to the recipient; your journal and dharma reviews are private to you (and optionally to your AI if you enable classroom context in your Frank settings).
Just Frank platform staff: access is limited and role-based, and is used only to operate, support, and secure the service — not to browse your content. Administrative actions taken through our admin tools are recorded in an audit log. A small number of engineers can also reach the production database directly for maintenance and incident response; that access is restricted to senior staff by credential.
Third-party processors. The services below process data on our behalf under their standard data processing terms. This list is complete as of the date at the top of this page.
| Service | Purpose | Data shared |
|---|---|---|
| Supabase | Database, auth, file storage | All platform data (encrypted at rest) |
| Vercel | Web + API hosting | Request logs, IP |
| Anthropic | AI model inference | AI conversation turns + context |
| OpenAI | Writing out voice notes sent to a business’s connected social account, and writing out the speech in videos a business turns into reels, for businesses that have these features | The audio of the voice note, or the sound of the video clip |
| Stripe | Payment processing (if your host charges) | Billing info |
| Google Calendar sync, Google Sign-In (optional), Google Meet rooms and their recordings for businesses that use them, Google Ads and a business’s own Google tag for businesses that connect them | Calendar scope you grant, OAuth profile; for Google Ads, the ads the owner makes and, after a visitor accepts cookies, a sale or sign-up that came from the owner’s Google ad (see §3b) | |
| Firebase Cloud Messaging | Android push notifications | Device token, notification payload |
| Apple Push Notification service | iOS push notifications | Device token, notification payload |
| Meta Platforms (Instagram, Facebook, WhatsApp) | Publishing scheduled posts to a connected Instagram Business/Creator account, and sending and receiving that account’s direct messages, when a community admin connects it (see §3a); running a business’s Facebook and Instagram ads, its lead forms and its WhatsApp messages when the owner connects them; and the Meta Pixel on Just Frank’s own pages and on a business’s pages (see §1 Cookies and §3e) | The Instagram account the admin grants, the post content + media the admin schedules, and the direct messages exchanged with that account; the ads the owner makes and the leads and WhatsApp messages they receive; for the pixel, page visits and Meta’s cookie, and for a sign-up or payment that came from an ad, a hashed email address |
| TikTok (TikTok API for Business) | Publishing posts to, and reading and replying to comments on, a TikTok account a business owner connected (see §3c); the owner’s TikTok ads and lead forms, and the business’s own TikTok pixel on its pages (see §3e) | The connected account’s ID, username and access tokens; the posts the owner schedules; comments on those posts and the commenters’ TikTok identifier, username and display name |
| Publishing posts to a connected LinkedIn profile or company page, and showing comments on a connected page’s posts (see §3d) | The connected member’s ID and name, the page’s ID and name, access tokens, the posts the owner schedules; page comments (kept 48 hours) and commenters’ member IDs | |
| Zernio | Legacy social publishing and inbox provider, used only for connections not made directly to Meta. For those, Zernio brokers the connection and holds the access tokens (see §3a) | Connecting admin’s social identity and access tokens, plus the content an admin chooses to publish or the messages they manage |
| Amazon Web Services (Amazon SES) | Email delivery (notifications, community email, broadcasts), from servers in Canada | Your email address and the contents of emails we send you |
| PostHog | Product analytics and session replay (see §1 — Session recordings) | Your user ID, email, name, pages viewed, and interactions in the app |
| Plaid | Bank account connection, where a Host uses our accounting features | Bank account and transaction data for the account a Host chooses to connect. Members do not connect bank accounts |
| Zoom | Community meetings and recordings, where a Host connects Zoom | Meeting metadata, recordings, and transcripts for meetings run through the integration |
| Cloudflare | Video hosting and media delivery (R2 storage, Stream) | Videos, images, and files uploaded to communities, and the files a business keeps in Storage (in a private bucket), call recordings from the note-taker, and DM attachments |
| Bunny.net | Video hosting and delivery, alongside Cloudflare Stream | Videos uploaded to communities |
| Sentry | Error and crash reporting | Error reports, which may incidentally contain your user ID or request details |
| Telnyx | Phone calls and texts a business makes or receives through Just Frank, their recordings and written transcripts (see §4b) | The phone numbers on the call or text, the sound of the call, the texts, and, when a recording is kept (§4b), the recording and its transcript |
| fal | Making AI pictures and videos (it runs OpenAI’s image model, Google’s Veo video model and others for us; see §4d) | The words asked for and any photos or video frames attached to the request, which can show people’s faces |
| Runway | Making AI videos and their sound (see §4d) | The words asked for and any pictures attached to the request |
| Kling | Making AI videos, as a backup service, from servers in Singapore (see §4d) | The words asked for and any picture attached to the request |
| BytePlus | Making AI videos (ByteDance’s Seedance model), from servers in Southeast Asia (see §4d) | The words asked for and any picture attached to the request |
| Voyage AI | Helping the AI find the right passage: it turns text into numbers we can search | Questions asked to the AI, the documents a community gives its AI, and meeting transcripts |
| Fly.io | The computers that run our meeting note-taker and put reels together | The sound and video of a meeting the note-taker joins, and the clips a business turns into a reel |
| Inngest | Running background jobs (sending scheduled emails, writing call summaries, and similar) | The details each job needs, such as a member or contact ID, an email address, or a message |
| ImprovMX | Forwarding replies to a business’s own email domain to an inbox the owner reads, when the domain has no mailbox of its own | The replies people send to that domain, including their email address |
| Cloudflare Turnstile and hCaptcha | Checking that a sign-up or form is sent by a person, not a bot | Your IP address and browser details, read by the check while you fill in the form |
| GIPHY | Searching for GIFs to add to a post, comment or message | The search words you type. The GIF you pick is then loaded from GIPHY by your browser, which sees your IP address |
| OpenStreetMap (Nominatim) | Turning the place you type as your profile’s location, or into a location search, into a point on a map (for the community member map) | The place text that was typed, such as a city |
Law enforcement: we disclose data only when legally compelled by a valid order, subpoena, or warrant.
3a. Connecting an Instagram account (Meta)
A community admin can connect their own Instagram Business or Creator account to Just Frank so they can schedule and publish posts to it, and read and reply to the direct messages that account receives. The connection is per-community and admin-initiated, and it is made through Meta’s own login and consent screen. Members do not connect their personal Instagram accounts through Just Frank.
Permissions we request
- instagram_business_basic — read the connected professional account’s ID, username and profile details, so we can show the admin which account is connected and attribute posts and conversations to it.
- instagram_business_content_publish — publish photos, videos, Reels, Stories and carousels to the connected account at the time the admin scheduled them.
- instagram_business_manage_messages — receive the direct messages sent to the connected account, display them to the admin in a unified inbox, send the admin’s replies, and run the automated replies the admin has configured.
We request only these permissions. Through this Instagram connection we do not request access to advertising accounts, comments, insights, or any account the admin has not explicitly connected. Ads are a separate connection the owner makes, described in §3e.
What we send to Meta
When an admin schedules a post, at the scheduled time Just Frank sends Meta the post text the admin authored, the images or videos they attached, and the access token for the connected account. When an admin or one of their automations replies to a direct message, we send Meta the reply text. Nothing is published or sent without the admin having composed and scheduled or configured it.
Just Frank does not transmit member identities, community posts, comments, reactions, AI conversations, journal entries, or email subscriber data to Meta.
What we receive from Meta, and how we use it
This is the data the messaging permission gives us. When someone sends a direct message to a connected Instagram account, Meta delivers that message to Just Frank by webhook and we store:
- The sender’s Instagram-scoped user ID, username, display name and profile picture, as provided by Meta.
- The text of the messages exchanged in that conversation, and the time each was sent.
- Any answer the sender gives to a question an admin’s automation asked them, and any label (“tag”) the admin or their automation applies to that person.
We use this only to operate the inbox and automations for the admin whose account received the message: to show them the conversation, let them reply, and run the automated replies they configured. We do not use it to build advertising profiles, we do not sell it, we do not use it to train AI models, and we do not use it for any purpose unrelated to that admin’s own inbox. Where an admin has enabled Just Frank’s AI assistant to draft a reply, the conversation text is sent to our AI provider solely to produce that draft, which the admin must approve before it is sent.
An Instagram contact is kept separate from a community’s email subscribers. Messaging someone on Instagram does not add them to any email list.
Automated messages
Where an admin has set up an automated reply, the first automated message in a conversation is labelled as automated and tells the recipient they can reply STOP to opt out. That label is added by Just Frank when the message is sent and cannot be removed by the admin. A person who replies STOP (or UNSUBSCRIBE, CANCEL, QUIT, END, or OPT OUT) is removed from the automation immediately. If a human admin replies to a conversation themselves, the automation stands down and stops sending.
Who holds the connection, and how
For accounts connected directly to Meta, Just Frank holds the access token itself, encrypted at rest, and calls Meta’s Instagram API directly. Some older connections are instead brokered by Zernio, a third-party social publishing provider; for those, Zernio holds the token and processes the data on our instructions under its data processing terms. In both cases the token is scoped to the single account the admin connected.
Connections are scoped to the community that created them — one community’s connection cannot be used to publish or message on behalf of another.
How long we keep it
Direct message conversations are kept so the admin has the history of their own inbox. They are kept when the connection is removed too, so a business that disconnects by mistake does not lose its inbox. When Meta sends us a deletion request for a person, that person’s conversations, messages, contact record, automation enrolments and labels are deleted straight away. When a person asks us directly (see below), we delete the same data once we have checked the request.
Disconnecting and data deletion
To disconnect Instagram, remove Just Frank in Instagram’s own settings → Apps and Websites. That revokes Just Frank’s access at Meta directly, and Meta tells us, so the connection is marked disconnected here too. You can also write to us at the address below and we will disconnect it for you.
Anyone who has messaged a connected Instagram account can request deletion of their data by submitting a request via itsjustfrank.com/legal/data-deletion, or by emailing us at the address in §11. Just Frank also honours Meta-initiated requests. Meta sends deletion requests to /api/public/meta/data-deletion-callback, and we delete that person’s messages, conversations, contact record, automation enrolments and labels on receipt. Meta sends app removals to /api/public/meta/deauthorize-callback, and we mark that Instagram connection disconnected and delete the access token we held for it.
3b. Google API Services — Limited Use
Just Frank’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Just Frank connects to Google Calendar only when you choose to link your Google account from the Just Frank Calendar feature. When you do, we request the following Google OAuth scopes:
https://www.googleapis.com/auth/calendar— to read your calendars and to create, update, and sync calendar events between Just Frank and Google Calendar.https://www.googleapis.com/auth/userinfo.emailandopenid— to identify which Google account you connected.
Google Ads
A business owner can connect their own Google Ads account to Just Frank, or ask Just Frank to make one for their business, from the business’s Ads page. The connection is per business and owner-initiated, made through Google’s own sign-in and consent screen. Members do not connect Google Ads accounts. When the owner connects, we request these Google OAuth scopes:
https://www.googleapis.com/auth/adwords: to list the Google Ads accounts the owner’s sign-in can reach so they can pick one; to show that account’s campaigns, spend and results on the owner’s Ads page; to pause, turn on or change the budget of a campaign when the owner presses those buttons; and to create the Search, Performance Max and YouTube ads the owner writes and reviews in Just Frank. Every ad we create starts paused and runs only when the owner turns it on. We never change the account’s billing.https://www.googleapis.com/auth/datamanager: to tell the owner’s own Google Ads account when someone who clicked one of its ads later buys or signs up on the owner’s Just Frank pages, so Google can report which ads worked. We send this only when that visitor accepted cookies, and we send the click identifier Google gave the visitor, the value and currency, and, only if the owner has accepted Google’s customer data terms, the visitor’s email address hashed with SHA-256.
YouTube (picking videos for a Google ad). If a business owner connects a YouTube channel from the business’s Ads settings, we request the Google OAuth scope https://www.googleapis.com/auth/youtube.readonly: to read the channel’s name and picture and its list of videos (title, thumbnail, length, and whether each is public, unlisted or private), so the owner can pick one of their own videos for a Google video ad. We never upload, change or delete anything on the channel. We store the sign-in encrypted. The owner can disconnect YouTube at any time in Ads settings, which deletes our copy; we also ask Google to revoke it, unless the business has its own Google Ads sign-in connected, which a revoke could end too. You can always remove Just Frank’s access yourself from your Google Account’s security settings.
Specifically, in relation to data obtained through these Google APIs, Just Frank:
- uses Google user data only to provide and improve the user-facing calendar sync, Google Ads and YouTube video picking features you enable inside Just Frank;
- does not transfer Google user data to others except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with prior notice to users;
- does not use Google user data to target or serve advertisements to you. The Google Ads access is used only to run the ads you make for your own business, in your own account;
- does not sell Google user data, and does not use it to train, develop, or improve generalized or non-personalized AI / machine-learning models;
- does not allow humans to read Google user data unless we first obtain your affirmative agreement to view specific data, it is necessary for security purposes (such as investigating abuse), it is required to comply with applicable law, or the data has been aggregated and anonymized.
You can disconnect Google Calendar and revoke Just Frank’s access at any time from your Just Frank calendar settings, or from your Google Account → Security → Third-party access page. Disconnecting revokes the token at Google and deletes the stored access and refresh tokens from Just Frank.
An owner can disconnect Google Ads at any time from the Google Ads card on their business’s Ads page. That deletes the stored token and account details from Just Frank and asks Google to revoke our access. The Google Ads account itself, and its history, stay with the owner. If Just Frank made the account, the owner can also remove Just Frank’s manager access from Google Ads (Admin → Access and security).
3c. Connecting a TikTok account
A business owner can connect their own TikTok account to Just Frank so they can publish posts to it and see and reply to the comments on their posts. The connection is per business and owner-initiated, made through TikTok’s own login and consent screen. Members do not connect their personal TikTok accounts through Just Frank.
Permissions we request
Through TikTok’s API for Business, the “TikTok Accounts” permissions: read the connected account’s basic profile (so we can show which account is connected), list its posts, read and reply to comments on its posts, and publish video and photo posts.
What we send to TikTok
At the time the owner scheduled a post, we send TikTok the caption and the video or photos the owner attached. When the owner replies to a comment, we send the reply text. Nothing is published or sent unless the owner wrote and scheduled it.
What we receive from TikTok, and how we use it
When someone comments on a connected account’s post, TikTok notifies Just Frank and we store the comment text, its time, the post it is on, and the commenter’s TikTok identifier, username and display name. We show the comment in that business’s inbox so the owner can reply, and we add the commenter to that business’s own contact list (CRM) with a “TikTok” label, so the owner can recognise them if they get in touch another way. We use this only for that business. We do not sell it, use it for advertising profiles, or train AI models on it, and we never download or re-post TikTok content.
Disconnecting and deletion
The owner can disconnect TikTok from Media → Settings, which deletes the stored access tokens. Anyone can also remove Just Frank from the TikTok app (Settings and privacy → Security → Manage app permissions). A commenter can ask for their data to be deleted at itsjustfrank.com/legal/data-deletion or by email (see §11).
3d. Connecting LinkedIn
A business owner can connect their own LinkedIn profile, and a LinkedIn company page they administer, through LinkedIn’s own sign-in and consent screen.
Your LinkedIn profile
We request permission to know which LinkedIn member connected (name and ID, via “Sign In with LinkedIn”) and to publish posts on their behalf. We do not read comments or anything else on a personal profile.
Your company page
We request permission to publish posts as the page, read the comments on the page’s posts, reply as the page, and be notified when someone comments.
What we receive from LinkedIn, and how we use it
For a connected company page, we receive the comments people leave on the page’s posts and the commenter’s LinkedIn member ID. We show them only to that page’s administrators, in their Just Frank inbox, so they can reply. We delete the text of those comments from Just Frank after 48 hours, and we keep a commenter’s name only for as long as it is on screen, never stored. We do not add LinkedIn commenters to any contact list or CRM, we do not export or combine LinkedIn data with other data, and we do not use it for advertising, sales leads or recruiting.
Disconnecting
The owner can disconnect from Media → Settings, which deletes the stored access tokens. Anyone can also remove Just Frank in LinkedIn under Settings & Privacy → Data privacy → Permitted services.
3e. Ads, lead forms, WhatsApp and pixels
A business owner can connect their own Facebook and Instagram ad account (through Meta’s own sign-in), their TikTok ad account, their Google Ads account (see §3b) and their WhatsApp Business number. These connections are made by the owner, for that business only. Members do not connect them.
- Ads. We send the ad platform the ads the owner writes and the budget they set, and we show the owner the results. Every ad we make starts paused and runs only when the owner turns it on.
- Lead forms. When someone fills in a lead form on a business’s Meta or TikTok ad, the platform sends us what they typed (usually a name and email address) and we add them to the sign-up form the owner chose, so they join that business’s email list. Before a Meta lead form can run, the owner must give a link to their own privacy policy.
- WhatsApp. Messages people send to a business’s connected WhatsApp number, and the replies, go through Meta and are shown in that business’s inbox.
- Pixels and tags. A business can add its own Meta pixel, TikTok pixel or Google tag to its community’s public pages, so it can see which of its ads worked. They follow the same cookie rules as ours (§1, Cookies), load only on the community’s public pages (such as its landing and join pages), never on sign-in, member or admin pages, and never on a page embedded in someone else’s website. When a visitor who allowed cookies signs up or pays, we may tell that business’s own ad account, with the email address hashed.
4. AI and your data
Just Frank’s AI features (“Frank” and community-specific AIs) run on Anthropic Claude models. When you interact with AI:
- Your current message plus relevant context (recent posts, profile, classroom progress, journal entries — scope depends on the feature and your Frank privacy toggle) is sent to Anthropic.
- Anthropic processes the request and returns a response.
- We retain your conversation history so the AI has memory across sessions.
- Anthropic does not train on your data. It is processed under a commercial agreement that prohibits training use.
You can control AI context by adjusting privacy settings in Just Frank. Options include “full context,” “ask-only,” and “never use my classroom/journal data.”
4a. Getting help on WhatsApp
If you message the Just Frank support line on WhatsApp, this is what happens to what you send.
- We check it is you first. Before anything else we ask for the email on your Just Frank account and send a code to it. We only talk with people who have a verified Just Frank account. Texting the code back links your phone number to your account.
- What we keep. Your messages, and any screenshots, screen recordings or voice notes you send. We also keep a short profile so we can greet you by name: your name, your business, past problems you reported and any ratings you gave us.
- Why. To find and fix the problem you told us about, and to get better at support. Messages are saved to help us fix problems and improve our support, and our team reads some conversations to train how we answer.
- Who handles it. WhatsApp (Meta) carries the messages. An AI support assistant built on Anthropic’s Claude reads them and writes replies, under the same terms as section 4: Anthropic does not train on your data. A person on the Just Frank team approves every fix and can read the conversation.
- What we look at. Only your own account and your own community or business, and only to find the problem. We never look at anyone else’s.
- What we never send you. Account information of any kind, not even your own: no email addresses, member lists, revenue, payment or settings details. Ask for those inside Just Frank instead.
- How long we keep it. Screenshots, recordings and voice notes: 90 days. The text of the conversation: 12 months. Your support profile: while your Just Frank account exists. It is stored in the Just Frank database, where only our administrators can open it, with files in private storage. A working copy is kept on a server we operate and follows the same limits.
- Deleting it. Ask on WhatsApp or email hello@itsjustfrank.com and we delete your support history in full.
4b. Phone calls and texts from a business
A business can call and text people from Just Frank, and answer calls to its Just Frank number. The calls and texts are carried by Telnyx.
- What is kept. Who called whom, when, and for how long, and every text sent and received. These sit on the person’s contact record in that business’s CRM.
- Recordings. A call is kept as a recording only when the person on the call says yes to being recorded, when they leave a voicemail, or when they talk to the business’s AI assistant, which says at the start that it is an AI and that the call is recorded. If the person says no, or never answers the question, the recording and its transcript are deleted at Telnyx and never saved by Just Frank.
- Transcripts and summaries. Telnyx writes out a kept recording as text. Our AI processor (Anthropic) then writes a short summary and a next step for the business, and checks whether the person complained about being called. A complaint stops that business calling the number and pauses its calling until we review it.
- Who sees it. The business’s owner and the team members it lets use the CRM. Recordings and transcripts are kept for that business. To have one deleted, ask the business, or email us at the address in §11.
- Stopping texts and calls. Reply
STOP(orARRET) to a text and that business can no longer text you from Just Frank, until you textSTART. If you complain on a call about being called, your number goes on our stop list.
4c. Business storage and phone backup
A business can keep its own files in Just Frank Storage, and the owner’s iPhone app can back up the phone’s photos and videos into it.
- Where it lives. In a private bucket on Cloudflare R2. Inside Just Frank, only the owner and the team members the business lets use Media can open them.
- Phone backup. The app sends each photo or video, an ID for that phone and for the picture on it (so the same picture is never stored twice), and when it was taken. Files are stored as they are, so they keep anything the camera saved inside them, including the place a photo was taken if your camera records that.
- Deleting. A deleted file goes to Recently deleted, where it can be put back for 30 days. After 30 days it is removed for good.
4d. AI pictures, videos, reels and meeting notes
- Pictures and videos. When someone asks Just Frank to make a picture or a video, we send the words they asked for, and any photo or picture they attached, to the service that makes it: fal (which runs OpenAI’s image model and Google’s Veo video model for us), Runway, Kling or BytePlus. An attached photo can show a person’s face. Only attach a photo of someone who has agreed to it. The finished picture or video is saved in Just Frank. These services return the result to us; their own terms decide how long they keep what they received.
- Reels. When a business turns its video clips into a reel, the clips are put together on computers we run at Fly.io, and the speech in them is written out by OpenAI to make captions and find the pauses.
- Meeting note-taker. If a business turns it on, our own note-taker joins a booked video call, posts a message in the call’s chat saying the call is being recorded, records it and writes it out. The writing out is done by a speech model running on computers we run, not sent to an AI company. Our AI processor (Anthropic) writes the summary. The recording itself is deleted after 1 year; the transcript, summary and notes stay with the business.
- Search for the AI. To help the AI find the right passage, text such as a question to the AI, a document a community gives its AI, or a meeting transcript is sent to Voyage AI, which turns it into numbers we can search.
5. Retention
- Active account data: kept while your account is active.
- After you delete your account: your account is closed straight away and any paid memberships end then, so you are not charged again. Your data is erased 30 days after you ask (our daily erasure run picks it up the day that date passes). Until then you can stop it by emailing us. If you own a community or a business, hand it over or close it first; Delete account tells you how.
- What erasure deletes: your profile and sign-in, your journals, memberships, points and private conversations, and the pictures, videos and voice notes you uploaded are deleted.
- What erasure keeps: your posts, comments, reactions and messages in group conversations stay in their communities without your name, so the conversations around them still make sense. Payment and purchase records are kept for tax and accounting, with your name taken off them, along with audit logs and anything under a legal hold.
- AI conversations: retained alongside your profile; deleted when you delete your account or explicitly clear your AI history (where supported in your community’s configuration).
- Backups: deleted data may persist in encrypted backups for up to 90 days before being purged.
6. Your rights
You can:
- Access your data — export from your settings or by emailing us
- Correct inaccurate data — edit in the app, or email us
- Delete your account and data: on your account page under Security → Delete account (in the app: Settings → Delete account), or email us
- Port your data — export in machine-readable format (JSON or CSV)
- Opt out of non-essential communications — Settings → Notifications
- Withdraw consent to optional processing — revoke calendar sync, revoke AI context, etc.
EU / UK residents (GDPR): you also have the right to object to processing, restrict processing, and lodge a complaint with your local data protection authority.
California residents (CCPA / CPRA): you have the right to know, delete, correct, opt out of sale (we don’t sell), and non-discrimination. Email us to exercise these rights.
Data Controller: JustFrank Holdings Inc.
7. Security
We use industry-standard practices:
- TLS 1.2+ for all data in transit
- Encryption at rest (Supabase: AES-256)
- Row-level security (RLS) on all database tables
- Password, magic-link, or OAuth sign-in. Passwords are stored only as salted hashes — we never store or see your plaintext password
- API keys and secrets stored as encrypted environment variables, never in our source code
- Biometric unlock on mobile uses your device’s secure enclave — we never see the biometric template
No system is perfectly secure. In the event of a breach affecting your data, we will notify you within the timeframe required by applicable law (typically 72 hours under GDPR).
8. International transfers
Just Frank uses infrastructure providers (Supabase, Vercel, Anthropic, Google, Firebase) with data centers primarily in the United States and Europe. Transfers from the EU / UK are covered by Standard Contractual Clauses where required. Email is sent from Amazon servers in Canada. Two of the AI video services work from Asia: Kling from Singapore and BytePlus from Southeast Asia, so a request sent to them, and any picture attached to it, goes there.
9. Children
Just Frank is not intended for users under 16 (or the minimum age required by your country’s law, whichever is higher). We do not knowingly collect data from children. If you believe a child has given us data, email us and we will delete it.
10. Changes to this policy
We will post the updated version at this URL with a new “Last updated” date. Material changes are announced in-app and by email at least 14 days before taking effect.
11. Contact
Privacy questions: hello@itsjustfrank.com
JustFrank Holdings Inc.
Suite 202, 1965 West 4th Avenue
Vancouver, BC V6J 1M8
Canada
Canada