Hormone Strength · Bandung
Contact the Hormone Strength editorial team
Use this page to reach the people who write and maintain Hormone Strength. We take questions about training content, corrections, and topic suggestions. We do not offer individual medical or dietary advice, and we cannot review your personal training plan in detail, but we do read everything that comes in and route it to the right person.
What to write to us about
Corrections to a page, questions about how a training principle is explained, and suggestions for topics worth covering all belong here. Specific notes are much more useful than general impressions, and they get resolved faster.
- Unclear wording Tell us which page and which part If a section on progressive overload, deloads, or a compound lift is unclear, point to the exact passage. Quoting the sentence helps more than describing it from memory.
- Accuracy reports Show us what you believe is correct If something reads as inaccurate, include the correction and where you are getting it. A source or a second reference turns a vague doubt into something we can check and act on.
- Topic requests Name the gap you ran into Requests about home training equipment, training splits for people with limited days, and recovery planning come up often, and they influence what gets written next.
- Your training context Small apartment or a shared gym? If you train somewhere that is not well covered, mention it. Local detail makes for better articles than generic advice, and it tells us which readers we are writing past.
We would rather set an honest boundary than give advice outside what this site is for.
We do not answer individual questions about a hormonal condition, a training plan for a specific diagnosis, or anything that requires a professional opinion. We also do not provide product recommendations, supplement guidance, or nutrition prescriptions. If your question is about your own situation rather than the site's content, a qualified professional is the right place to take it.
Visit the About page
Questions about the training content
We do not write personalized programs by email, but the questions we receive regularly do shape what gets written next. Several existing pages on this site started as reader questions sent through this form. That is how the site stays useful.
Training days per week
Two days, three days, or six — the number changes how a program is built. Tell us what your week actually looks like, not what you wish it looked like.
Equipment you can reach
A full commercial gym, a shared apartment rack, or two dumbbells and a bench. Name what is available so the answer is not written for the wrong setting.
What you have been running
The lift, the set and rep scheme, and how long you have held it. If something stalled, say roughly when — the timing usually points at the cause.
If you are stuck on a program detail, send those three things and we may cover it in a future article or point you to an existing page. For background reading on how principles connect, start with Training Principles.
Corrections and accuracy reports
If you find an error, include the page path, the exact sentence or section, and a brief explanation of the issue. If the correction involves training safety, put that in the subject line so we prioritize it. We do not publish a public change log, but we do update pages when a correction is warranted. You will get a reply confirming what we found or changed. We would rather fix something quietly than leave it standing because it was inconvenient to edit.
Suggesting a topic
Topic suggestions are welcome. Tell us what you were looking for and could not find, and what would have helped. If you train in a specific context that is not well covered, such as a small apartment or a shared gym, mention it — that detail is what keeps new articles grounded.
A correction that touches safety
Lead the subject line with it. Those messages are read first, ahead of general notes and topic requests.
A suggestion about coverage
Requests arrive often for home equipment, low-day training splits, and recovery planning. Add yours if your situation is missing.
If your note is about recovery timing, loading, or how often to back off, the Recovery & Deload page already covers the basics, and it is a faster read than waiting for a reply.
How to reach us
You can write to [email protected], call +62 22 424 8714, or use the form on this page. Our postal address is Jl. Braga No. 12, Sumur Bandung, Kota Bandung, Jawa Barat, 40111. Phone hours are limited, so email is the more reliable route for detailed questions. If you are writing about a specific page, including the path saves a round trip.
- Email [email protected]
- Address Jl. Braga No. 12, Sumur Bandung, Kota Bandung, Jawa Barat, 40111
Visiting in person? The editorial office is on Jl. Braga in Sumur Bandung, central Bandung. Writes and calls are still the faster route — the office is not set up for walk-in programming consultations.
Response times and what happens next
We aim to reply within a few working days. Detailed programming questions take longer because they often need a careful answer, and corrections involving training safety are handled first. If your message needs a response from a specific part of the team, we forward it rather than letting it sit. If you do not hear back within a week, send a short follow-up; occasionally a message lands in the wrong folder. We would rather get a nudge than miss your note.
Common questions before you write
Can I ask for a program written for me?
No. We do not build personal plans by email. What we can do is explain the reasoning behind a principle on the site, or point you to the page that already covers it. If you describe your training week, your question often becomes a topic we write about later.
How much detail should a correction include?
The page path, the exact sentence or section, and a short explanation of what you believe is correct plus where you are getting it. Three lines of specific detail are more useful than a paragraph of general doubt, and they are usually resolved in a single exchange.
Will you tell me if a page gets updated?
Yes. You get a reply confirming what we found or changed. We do not maintain a public change log, so the reply is how the outcome reaches you. If a correction changes a safety note, that normally happens first.
Is email better than calling?
For anything with detail in it, yes. Phone hours run Monday to Friday, 09:00–18:00, and a call is fine for a quick routing question. A written note keeps the page and sentence you are asking about in front of the person answering.
Where to go while you wait
A reply on a detailed programming question can take a few days. These pages answer the most frequent questions we receive before a message is even sent.