Our promise
Every article on Being Tricky is written to help a real person solve a real problem. We don’t publish content just to rank in search, and we’d rather publish less than publish something we haven’t checked.
Who writes and checks the articles
Being Tricky is a one-person site. Prince Ramgarhia chooses the topics, does the testing, writes and edits every article, and is responsible for every word. There is no separate editor, so instead of a second pair of eyes we rely on a written checklist (below) that every article must pass before it’s published.
If someone else, such as a subject expert, actually reviews an article, their name appears as Reviewed by with what they checked. We never show a reviewer who didn’t review it.
How an article is made
- Topic: chosen from reader questions, site searches, search data and news that affects our readers.
- Testing: Android steps on a Samsung Galaxy phone, Windows steps on a Windows 11 PC. When a guide is tested hands-on, we record the device, software version and date in its Tested on box. See How we test.
- Untested platforms: iPhone and Mac steps are based on Apple’s official documentation unless the article says we tested them. They’re labeled “From Apple’s documentation” and linked.
- Writing: from our own test notes. AI tools may help with wording; see our AI use policy.
- Self-review: the checklist below, done on a different day from writing where possible, with fresh eyes.
- Publishing: only when the checklist passes. Our publishing system refuses to publish a draft that still has unresolved “verify” notes.
The pre-publish checklist
- Every step was done on the device named in Tested on, or is labeled as based on official documentation.
- Menu names, version numbers, prices and dates match the test notes and an official source checked that day.
- Warnings are included wherever a step could cost money, lose data or affect security.
- Sources are linked, official sources first.
- Screenshots are our own, with personal data blurred.
- The headline promises only what the article delivers.
- Affiliate links are disclosed at the top.
Sources
We rely on primary sources: official documentation from Google, Samsung, Microsoft, Apple and other companies, and government agencies such as the FTC, FCC and FBI, or the relevant authority in other countries. We link to them in each article.
Updates and dates
We show the date an article was first published. We only show an “Updated” date when we make a substantive change (new steps, a new software version, corrected facts), and we list those changes in the article’s update history. Fixing a typo doesn’t change the date. Older guides show a notice when they haven’t been re-checked in a while.
Independence
Advertisers and affiliate partners never see or approve our articles before they’re published, and they never decide what we recommend. See our advertising policy and ownership and funding.
Safety and privacy
We don’t publish guides that help anyone break into accounts, bypass security or privacy controls, or use pirated software. When readers search for those things, we explain the risks and show legitimate alternatives. Guides about scams and hacked accounts carry no ads.
Mistakes
One person can miss things. If you spot an error, please tell us. See our corrections policy.