Abyssal StrengthOpen the app

Privacy

Privacy policy

Abyssal Strength is a strength and conditioning app, built and run by FM Digital Ventures LLC. This page explains in plain language what the app stores about you, why it stores it, where it lives, how long it is kept, and how to get rid of all of it. It describes the product as it is built today — not as it might be later — and it will be updated as the product changes. Effective 17 October 2026.

What we store

Only what the app needs to run your training, plus one kind of record that carries no account id at all: the rate-limit counters. Everything else is tied to your account — apart from the sign-in cookie and the two things the app keeps on your own device while you are signed in, described under Cookies: a set or a cardio entry waiting to be sent, and the screens you have opened.

  • Your email address, and a password hash. Your password itself is never stored — what is stored is an scrypt hash, from which the password cannot be read back.
  • Your training setup: training type, goals and areas of emphasis, experience level, training days per week, session length, units and the equipment you train with. The equipment answer is stored as the codes you picked from the app's own list, in the order you picked them, and the app reads it to choose which movements your plan prescribes; where no movement for a slot fits what you saved, the plan keeps the slot's movement and stores a note with it saying that it does not fit the equipment saved on your account. The app asks for no name, no date of birth and no gender, and has no fields for them.
  • Your programs: the name, the training days, the movements prescribed on them with sets, reps, load, effort target (RPE/RIR), rest and any note, plus any prescribed cardio.
  • Your logged training: every session you open or finish with its name and start and finish times; every set with reps, weight and unit, RPE/RIR, rest, whether it was a warm-up or a working set, and any note; every cardio activity with its modality, duration, distance, pace, intensity, the effort zone you pick (Zone 1–5), effort RPE and any note.
  • Your weekly body-weight check-in: the weight you typed and the unit you typed it in (lb or kg), the date and time you recorded it, and the timezone offset you were at when you recorded it — so the reading keeps the wall clock you actually saw. One row per day at most.
  • Your calorie log: each entry's food or meal name, your serving note as you wrote it, the calorie number you typed, and the date and time you logged it.
  • Your daily calorie target: the number you set, and the local date it began to apply from. One row per change, so an earlier day is never measured against a target that did not apply to it.
  • Your entitlement record, if your account has one: the tier your account is on, where that tier came from, and the dates it is valid from and until. No screen in the app can create or change one. There is exactly one write path, in server-side code that no page can call, and it exists so a tier can be granted by hand while there is no billing — for example to a store reviewer. No card number, payment, invoice, charge or receipt is stored for you anywhere.
  • Sign-in records: one row per device you sign in from, holding a hash of the session token (never the token itself), when it was created, when it was last used, when it expires, and the browser identification string that device sent.
  • A session cookie on your device, so the app knows you are signed in. It cannot be read by scripts on the page, and it lasts 30 days.
  • Rate-limit counters, held to stop abuse rather than to run your training. Signing in, signing up and signing out each count attempts against a short-lived bucket, and so does every call the app makes to its server functions while you are signed in. A bucket's name is built from truncated SHA-256 fingerprints — 32 hash characters each, never the value itself. Most buckets carry a fingerprint of the IP address the request came from, and the per-email buckets add a second one, of the e-mail address that was typed. Two of them carry no address at all: the per-account bucket names only a fingerprint of the e-mail address on the account, and the app's per-session call budget names fingerprints of your session token and of the server function being called. Each row holds those counts, a count of consecutive failed sign-ins (which is what makes the app answer an attempt more and more slowly), and the times its window started, was last written and ends. No account id, no training data, and no plaintext address, e-mail address or token is in it.

Your progress figures — volume, per-lift bests, estimated 1RM, PRs and cardio totals — are not stored separately. They are computed from the sets and cardio activities above, every time you open the Progress screen.

What the app doesn't do

  • No advertising, and no advertising networks. There is no ad code in the app.
  • No analytics, no tracking and no crash-reporting service. Nothing about how you use the app is sent to a third party.
  • No profiling, no scoring, and no selling or renting of your data. Your training data is used for one purpose: showing you your training.
  • No marketing email. The app has no mailing list and has never sent one.
  • No location, contacts, photos, calendar or microphone. The Android app requests a single permission — internet access — and nothing else.
  • No health-platform integration. Abyssal Strength does not read Apple Health or Health Connect and does not connect to heart-rate straps or wearables; the effort zone on a cardio entry is a number you choose yourself.
  • No payment details. Nothing can be charged in the app today: there is no subscription, no card field and no payment provider connected.

Health and medical

Abyssal Strength is provided for general fitness and informational purposes: it is a training, body-weight and calorie log. It records what you tell it about your training, your body weight and what you eat, and it does arithmetic on those numbers. It is not a medical device and does not diagnose, treat, cure, or prevent any medical condition. Nothing in the app is medical or nutritional advice, and nothing in it replaces the judgement of a qualified professional. Your plan, your daily calorie target, your logged sets and every figure derived from them — volume, tonnage, an estimated one-rep max, a comparison against an earlier period — are your own inputs added up, and the Progress screen names what each figure was computed from. The app never suggests a calorie target for you: one applies only after you set it yourself. Consult a qualified healthcare professional before you begin or change an exercise or nutrition programme, especially if you have an injury, symptoms, a medical condition, or are pregnant or taking medication.

Why we hold it

To run the product: to sign you in, remember your setup, build and keep your program, save what you logged, and compute your progress. One record class is held for two further reasons and for no other: the rate-limit counters, which exist so nobody can guess passwords against an account, create accounts in bulk, or make one signed-in session place unbounded calls. That is the entire list. If you can think of a use for your data that is not on it, we are not doing it.

Where it lives

Everything above lives in one managed PostgreSQL database (Neon), in the owner's account — with one exception beside your sign-in cookie, stated in full under Cookies: while you are signed in, a set or a cardio entry you save with no connection is held on the device until it can be sent, and the screens you have opened are held on the device too. The held write is a copy of your own writing, not a second store of it: it goes to that same database as your own write, and nowhere else. The app reaches it only from server-side code: the database credential sits in the server's environment, is never sent to a browser or into the installed Android app, and appears nowhere in the code those apps download. The rate-limit counters live in that same database, so this paragraph covers them too.

No athlete can read another athlete's data — every query in the product is narrowed to the signed-in account in the SQL itself, not by trusting the app.

How it travels

Every request travels over HTTPS. The web app is served over HTTPS, and the Android app is a native shell that loads that same HTTPS site, so its traffic is encrypted the same way. There is no plain-HTTP path in the product.

Cookies

One cookie, named abyssalstrength_session. It carries an opaque token that identifies your sign-in, it cannot be read by scripts on the page, and it is the only way the server knows who you are. There are no advertising cookies, no analytics cookies and no third-party cookies, and a visit where you are not signed in sets no cookie at all. Signing out clears it. One of the site's pages is an exception, and it says so on itself: the Device diagnostics page leaves a few small markers on the device it runs on — a random nonce, a timestamp and a count of how many times the page has loaded — so it can measure what that browser and device actually allow. They hold no training data, they are not used to identify you, and they never leave the device. When you are signed in, the app also keeps two things of your own on this device: a set or a cardio entry you save while the connection is down, held until it can be sent, and the screens you have opened (and a few it prepares in advance), so the app opens without a connection. Signing out removes the saved screens; clearing the site data removes both.

One note on requests rather than storage: the pages use the Inter typeface, and Inter is served from Abyssal Strength's own origin — the font file is delivered by the same server as the page itself, rather than fetched from Google's font service. A page load here therefore makes no third-party request at all: no font host, no analytics, no advertising and no tracking service. While you are reading this, the only server your browser talks to is Abyssal Strength's own.

How long we keep it

Nothing in the list above quietly expires. While your account exists it all stays, because it is what the app reads back to you: your setup, your programs, every set, cardio activity, weight check-in, calorie entry and calorie target you have logged, and your entitlement record if you have one. A row goes when you remove it in the app — a log line, a check-in, an entry or a target you delete — or when you delete the account. Nothing prunes old training on a timer, and there is no age after which a log stops being shown.

Two kinds of row are different, and both are worth stating exactly rather than in passing.

  • Sign-in rows: one per device, and each one stops being usable when its expiry passes, 30 days after it was created. The row itself is deleted when that device signs out, and every row on the account is deleted with the account. The app does clear dead rows by itself, riding the request path rather than a schedule: a request that resolves a signed-in session deletes up to 500 rows at a time, taking only rows that expired more than seven days ago or that were revoked, and it does that at most once an hour per server process. Nothing is scheduled, so a row can still sit in the table until some signed-in request is served — as well as until the next sign-out on that device, or until the account is deleted. What sits there is a SHA-256 hash of a token, not the token, and an expired token resolves to no session at all.
  • Rate-limit counters: a bucket's window is ten minutes for signing in, for signing out and for the per-session call budget, and one hour for signing up and for the streak of failed sign-ins. Once the window has ended the row is useless, and the limiter deletes expired rows itself the next time it runs — at most once a minute per server process. Nothing else deletes them, and no counter carries an account id, so deleting your account cannot reach one: a counter whose name holds a fingerprint of your address, of your e-mail address, or of a session token is left until its window ends and the limiter next runs — at most an hour while the app keeps serving requests, and not until it does again if it stops.

On the device you use, the two copies stated under Cookies have their own lifetimes: a set or a cardio entry saved with no connection is kept until it reaches the server, and the screens the app has saved are kept until you sign out or clear this site's data.

Deleting it all

You can delete your account and everything stored with it, yourself, from inside the app: open your Profile, tap Delete my account and type the word DELETE to arm it. That runs one statement against the database, keyed to the account the session cookie resolves to and to nothing the screen sends: it removes everything stored against the account — setup, programs, logged sets, cardio, weight check-ins, calorie entries and daily targets, and any entitlement record — immediately and permanently, and it deletes the sign-in row for every device that was signed in, so each of those sessions stops working. One qualification, because a deletion sentence should be exact: that delete reaches your account, not the device you are using. The app also keeps two things of your own on this device — a set or a cardio entry you saved while the connection was down, held until it can be sent, and the screens you have opened, so the app opens with no signal. Signing out removes the saved screens; it does not remove the held write, and deleting the account removes neither. Clearing this site's data on the device removes both.

  • The account itself, with its email address and password.
  • Your training setup: training type, goals, experience level, training days, units and the equipment you picked from the app's list.
  • Every program you own, with its training days, prescribed movements and prescribed cardio.
  • Every workout session you have opened or finished.
  • Every set you logged — reps, weight, RPE/RIR and rest.
  • Every cardio activity you logged, in a session or on its own.
  • Every weight check-in you recorded — your weight with the unit you typed it in (lb or kg), and the date and time you recorded it.
  • Every calorie entry — the food or meal name, your serving note, the calorie value, and the date and time you logged it.
  • Every daily calorie target you set, and the date it took effect from.
  • Your entitlement record, if your account has one — the tier your account is on, where that tier came from, and the dates it is valid from and until.
  • Your progress history, per-lift bests and PRs — computed from the sets above, so they go with them.
  • Every signed-in session, on every device, including the installed Android app.

Nothing of your training on our side. The exercise library is shared reference data that every athlete's plan points at, so the catalogue itself stays — but no row in it carries your account, and no training of yours is in it.

Two things a delete cannot reach, stated here rather than left to be discovered. The rate-limit counters described under How long we keep it are keyed to one or more fingerprints — of an address, of an e-mail address, or of a session token — carry no account id, and are removed only when their window ends and the limiter next runs: at most an hour, while the app keeps serving requests, and not until it does again if it stops. And the exercise library holds one column that can point at an account, on a movement an athlete wrote: deleting the account sets that column to empty, so such a movement would stay in the catalogue with no creator named. Nothing in the app can author a movement today, so in practice there is none.

It happens the moment you confirm: no waiting period, no deactivation, no undone state, and no copy of the account kept on the side for us to restore it from. It also does not sit in a support queue — the delete runs against the database as you press it. Your email address is released, so it can be used again, and a new account starts empty.

If you can no longer sign in, you can still have the account deleted — Delete your account explains both routes.

Backups, stated precisely

The product keeps no separate copy of your data: no export, no archive table, no second database, and nothing in it runs a scheduled backup job. There is no scheduler in the product at all. Deleting is the end of it here.

One qualification, because a policy should be exact about this: the managed database service Abyssal Strength runs on is entitled, under the plan the database is on, to keep its own operational backups and change history of the whole database. That is the provider's machinery and the provider's setting, not ours: the app cannot read it, nothing in the product controls it, and no feature in the product could restore a deleted account from it. Because that window is set by the provider rather than by anything we can measure from inside the app, this page states no number for it. A full copy of the database has been restored into a separate database and checked section by section, which is a test of the recovery route and not a copy of your account held on the side.

Children

Abyssal Strength is built for adults training on their own. It is not directed at children and is not designed for them. The app asks for no date of birth and no age, and it does not check how old anyone is; a minimum age for an account has not been set yet, so this page states no figure for it. If you believe a child has created an account, email us at the address below and we will delete it.

Not built yet

Some things a policy often describes do not exist here, and this page will not pretend otherwise: there is no way to export or download your data yet, no billing is connected, and nothing in the app can take a payment. Abyssal Strength is operated by FM Digital Ventures LLC; the plans screen shows the two tiers and their prices, and it offers no way to buy one.

If you want a copy of what is stored against your account, email the address below and it will be dealt with by hand.

Changes to this policy

This policy will be updated as Abyssal Strength changes, and the effective date at the top of the page changes with it, so you can always tell which text you are reading. When something material changes — a new kind of data, a new service handling it — the wording is revised to match the product at that moment rather than left as it was.

Contact

One address, for everything — questions about this policy, a deletion you cannot do yourself, anything else:

[email protected]

This address is monitored.

This page describes what the app does today, in the app's own words rather than a lawyer's. It is not a claim of certification against any privacy law or standard, and nothing on this page should be read as one.