Privacy Policy

• Your account: your email address, your name, your handle and your password. Passwords are stored only as a one-way hash, never as the password itself.
• Google sign-in, if you use it: your name, your email address and Google’s account ID for you, so we can recognise you next time. We do not get your Google password.
• Password resets: when you ask for a reset link, we keep a scrambled copy of the link (not the link itself), when it expires (30 minutes later) and when it was used or ended. Resetting your password also disconnects Google sign-in, if you had connected it.
• Messages you send us: when you use “Contact support” on the Help page, we keep your message, the topic you chose, the email address we reply to (your account’s, or the one you type if you are not signed in), which account sent it if you were signed in, and our reply with who sent it and when.
• Your profile: anything you choose to add: a bio, a location and a website.
• What you do in communities: posts, comments, likes, courses and lessons, lesson progress, events and RSVPs, who you follow, your memberships, points and levels, the reviews you write of communities you belong to, the last time you used each community (to show how many members are online), and the notifications we show you inside the app. If you run a community, also the intro video link and the pictures you add to its landing page; we store the pictures with Supabase, after removing the camera details a picture can carry (such as where and when it was taken, and the device), and we delete them when you delete the picture or the community.
• Videos you upload: on the Hobby and Pro plans, a community’s owner and admins can upload videos into lessons and their own posts. A video can show faces and carry voices. We store the file with Cloudflare R2 in a private storage space, with its name, size and length, and who uploaded it. Only people who can open that lesson or post can watch it, through a private link that stops working after 6 hours; there is no download button. We delete a video within a day after it is removed or replaced, after the lesson or post that used it is deleted (deleting an account deletes its posts), or after its community is deleted. If a community’s plan ends or moves to a smaller one and its videos go over the new limit, they keep playing for 30 days, then the newest ones over the limit pause, and paused videos are deleted 60 days after the plan changed unless the plan is restarted. We email the owner before each step.
• Billing records: your plan, and the subscription or membership IDs, status and dates that Whop, our payment provider, sends us. For a paid community we also keep what you paid, Akademya’s fee from it and, if your access ended, why (you left, were removed or banned, or the community was deleted). If the community is deleted, these records are kept, together with its name. Card details are entered on Whop’s checkout and never reach Akademya.
• If you charge your members: to set up your payout account we send Whop your email address, your country and your community’s name, and we keep the Whop account ID and its status. Identity checks and bank details are handled by Whop, not by us.
• Security data: to limit repeated sign-in, sign-up and password-reset attempts and support messages, we count them by IP address and, at sign-in and password reset, by the email address typed in, even when no account uses it. On the support form we count messages by your account if you are signed in, or by the email address you type if you are not. The address and the IP are stored as they are (for the support form, an IPv6 address is shortened to its first half), in counters kept apart from your profile. Each counter covers at most a day, and expired counters are deleted from time to time, so one can stay stored for a while after it expires.

Only to run Akademya: to sign you in, show your communities and content to the right people, keep points and leaderboards, take payments and apply your plan, keep accounts secure and stop abuse, and answer you when you contact us. Akademya sends email only for the password-reset link you ask for and for messages you send us from the Help page: our reply goes to you, and our own support mailbox gets a short notice that a new message is waiting, with no personal data in it. Notifications appear inside the app.

Anyone on the internet, including people who are not signed in to Akademya, can see:

• Your profile page: your name, handle, bio, location and website, the month you joined, how many people follow you and how many you follow, the public communities you belong to (with your role, points and level in each), and the titles of your five most recent posts in public communities, paid ones included.
• Everything in a free public community: its posts and comments, courses, events and who is going to them, leaderboards, and its member list, which shows each member’s name, handle, bio, role, points, level and when they joined.
• The name, description, category and member count of every community, private and paid ones included, and its landing page: its intro video and pictures, the titles of its published courses and upcoming events with their counts, how many members are online (a number, never who), and its members' reviews. A review shows your first name and last initial, your stars and words, and how long you have been a member (and whether you pay), also on a private or paid community's page.

Everything else in a paid or private community, including its member list, can be seen only by its members. A private community’s members are approved by its owner or admins, who also see who has asked to join.

We ask search engines not to show profile pages, community member lists and leaderboards in their results. That is a request to search engines, not a lock: anyone who opens those pages can still see them. Everything else that anyone can see, such as posts, comments, courses, and events with who is going to them, may appear in search results.

If you pay to join a community, that payment is made to the community owner through Whop, and the owner sees your purchase in their own Whop account.

• Supabase hosts our database, in Singapore.
• Vercel hosts the website and keeps standard request logs.
• Cloudflare stores the videos owners and admins upload (Cloudflare R2), in a private storage space.
• Whop processes every payment, under its own privacy policy.
• Google, if you choose to sign in with Google.
• Google also hosts our support mailbox, support@verixdigital.com, on Google Workspace. The notice it gets when you send us a message from the Help page contains no personal data. But if you reply to an email from us, or write to that address yourself, your message and your email address arrive in that Google-hosted mailbox.
• Resend delivers our emails: for a password reset it receives your email address and the link; for our reply to a support message, your email address and our reply, and also your message if you sent it signed in (the reply quotes it).

Your information may be processed outside the country you live in, including in Singapore and wherever these providers operate.

A post or lesson can show a video from YouTube (run by Google) or Vimeo. The video player is loaded from YouTube’s or Vimeo’s own servers as soon as you open that page, whether or not you press play, so they receive your IP address, basic details about your browser, and any cookies your browser already holds for them. They are not working for us: they handle that information under their own privacy policies (Google’s, Vimeo’s).

To limit what they store in your browser, we load YouTube’s player in its privacy-enhanced mode (youtube-nocookie.com) and Vimeo’s player with its “do not track” setting. What each one stores is described under Cookies below.

A community's landing page can also show an intro video from YouTube, Vimeo or Loom. That player is not loaded until you press play, so nothing is sent to them before you do. Once you press play, the same applies as above, and a Loom video is handled under Loom's own privacy policy; its player may store data in your browser under Loom's rules.

The owner of a community on the Hobby or Pro plan may add their own Facebook (Meta) pixel, to measure their own ads. It runs only on that community's public pages (its page at www.akademya.co/<name>, joining it, and the page after paying), never inside a community, never on another community, and never on Akademya's own home, Discover or pricing pages. Akademya itself does not use it.

What Facebook receives from your browser there: that you visited the page, that you joined, that you started a checkout, and for your first payment to that community, its amount and money. Facebook also receives your IP address, details about your browser and any Facebook cookies your browser holds, and the pixel may set its own cookie (_fbp). If the community is on Pro and its owner also connected Facebook's server events, then when your first payment to that community goes through, Akademya sends Facebook that payment's amount and money with your email address and your Akademya account ID, each scrambled first (SHA-256 hashed), and, as Facebook requires, your browser's user agent, your IP address and Facebook's own cookies (_fbp, _fbc) if your browser holds them, so Facebook can match it to its own users. For this, those browser details are kept with your checkout from the moment you press Join until the payment is confirmed, and only when the pixel is on and your choice allows it. If the payment never comes, our nightly clean-up clears them once 7 days have passed (so about a week), and they are cleared when your account is deleted. Monthly renewals and refunds are not sent. Facebook handles this under its own privacy policy, and the community's owner decides how they use it for their ads.

If you visit from the European Union, the rest of the European Economic Area, the United Kingdom or Switzerland, or we can't tell where you are, we ask first (“Allow Facebook to measure ads?”). Nothing is sent to Facebook from your browser before you press Allow, and if you say No thanks, nothing is sent from our server either. Your choice is kept in a cookie for 180 days. To change it at any time, press “Facebook ads choice” at the bottom of that community's page: your answer is cleared (you stay signed in) and the question is asked again.

Akademya itself sets only three cookies: one to keep you signed in (it lasts up to 30 days, or until you sign out), a short one that lives for 10 minutes while you sign in with Google, and, only where we ask about Facebook on a Hobby or Pro community's page, one that remembers your answer for 180 days. Akademya uses no advertising or analytics cookies of its own; a Hobby or Pro community's Facebook pixel may set Facebook's, as described above.

On a page with a video, the video player can also store data in your browser under YouTube’s or Vimeo’s rules, not ours. When we checked on 29 September 2026, in a browser with nothing stored from either site, before and after playing a video: YouTube’s player set no cookies, but saved a few settings in your browser’s storage, such as caption preferences and connection speed. Vimeo’s player set three security cookies from Cloudflare, the network Vimeo uses; one of them lasts a year. Playing the video added no cookies. YouTube and Vimeo may change what their players store.

We keep your information while your account exists. You can ask us to delete your account by signing in to it and sending us a message from the Help page; we reply to confirm before we delete it. If you write to support@verixdigital.com instead, we will ask you to send the request that way, so we know it comes from you. Within 30 days of your request:

• We remove your email address, name, handle, password, Google sign-in link and profile (bio, location and website), the address and text of the messages you sent us from the Help page with our replies, the reviews you wrote of communities, and the browser details kept with any checkout for the Facebook pixel, and nobody can sign in to the account again.
• Replies you sent to our emails, and emails you wrote to support@verixdigital.com, are in our support mailbox (hosted by Google), not in Akademya. We delete them from that mailbox when you ask, and we do so as part of deleting your account.
• Everything else stays where it is, shown under the name “Deleted member”: your posts, comments, likes, courses, events and RSVPs, who you follow, your memberships, points and levels, and your lesson progress. If you want any of it gone, remove it yourself before you ask, for example by deleting your posts.
• We keep payment records (subscription and membership IDs, amounts, fees, statuses and dates), which we must keep by law.

Before we can delete it, anything that could still charge you must be cancelled: your Hobby and Pro plans and any paid community memberships (we will tell you which). And if you own a community, you need to delete it first (in its settings), because a community cannot yet be handed to someone else. Whop keeps its own records of your payments, under its own privacy policy.

You can change your name and profile at any time in your settings. While you are a member of a community, you can delete your own posts and comments in it; after you leave, are removed, or your paid access ends, you can no longer delete them yourself. To get a copy of your information or correct it, write to support@verixdigital.com; to delete your account, follow the steps above. We will respond within 30 days. Depending on where you live, you may also have the right to complain to your local data protection authority.

Akademya is not meant for children under 13, and we do not knowingly collect their information. If you believe a child has given us their information, write to support@verixdigital.com; we confirm by writing to the account's own email address, then delete the account.

If we change this policy, we will post the new version here with a new date.

Privacy questions and requests: write to support@verixdigital.com.