| Our principles | We cover one brand, Slots of Vegas, and we cover it the way a specialist publication covers its subject: close, honest and useful. The lobby, the bonuses, the cashier, the mobile app and the service pages are all written from first-hand use. We do not copy marketing text, we do not rewrite the operator's press releases, and we do not publish 'top 10' filler that pads word counts without adding information. We also keep the guide short. If a page says what needs to be said in six hundred words, we do not stretch it to twelve hundred to look more authoritative. Readers are busy and the guide should respect their time. The flipside is that when a subject deserves the length — the full terms of a welcome bonus, say, or a payment method with specific state restrictions — we write it long and we do not apologise. Length tracks what the reader needs, not what the publisher wants. |
| Fact-checking | Before a page goes live, numbers are checked against the operator's own cashier screens, the current terms, the current promo page, and — for the mobile app — the current store listing on Google Play or the App Store. If a figure changes after publication we update the page and record the change in the version history. Two editors handle fact-checking: one writes, the other reviews. For numeric facts — bonus amounts, wagering multipliers, processing times, app sizes — the reviewer re-runs the check from scratch rather than reading the writer's screenshot. For legal statements — age limits, state restrictions, responsible-gaming references — we cite the regulator or the responsible-gaming body directly. Rumours and forum anecdotes are kept out of the guide; if a complaint is relevant, we document it on the Complaints page with the pattern of occurrences, not with a single user story. |
| Sources | Primary sources are Slots of Vegas's own property: cashier pages, terms, promotion pages, mobile app listings and support transcripts. Secondary sources, used sparingly, are published industry reports, the editorial standards pages of comparable guides, and government regulator statements, cited in the article when relevant. We prefer screenshots to transcriptions and transcriptions to paraphrase. When the operator updates a page, the previous screenshot is kept in our internal archive so that we can show, if a reader asks, what the page used to say. The archive is not public — it protects the operator's intellectual property in previously published versions — but a reader with a legitimate query can request a specific screenshot by email. |
| Sponsored content | We do not publish sponsored posts, paid-for reviews, or guest articles from the operator's marketing team. Our only commercial relationship with the operator is the affiliate commission documented on the disclosure page. If that changes, we will say so here first. We do not accept gifts in kind either — travel to launch events, hardware, promotional merchandise. Everything the editors use for testing is bought with site funds and the invoices are kept. When an operator asks for a correction on an article, we treat the request as any other reader correction: we check it against the primary source and respond with the result, not with a courtesy edit. |
| Update cycle | Trafficky pages — the home, the bonuses hub, the no-deposit page, the promo codes list, the mobile app page — are reviewed at least once a quarter and after any announced operator change. Service pages are reviewed at least once a year or after a regulatory change. Every page carries a 'last updated' date in the author block and a visible edit log if the change was material. Minor fixes — a typo, a broken outbound link — are made silently; substantive changes to numbers, terms or ratings are noted. Readers who have bookmarked a page can return to it and see what has changed since their last visit. |