Skip to main content
Literally Apps — Home
id

Editorial Editorial

How we source data, verify numbers, update old articles, and handle correction requests.

1. Sourcing data

Every price figure, percentage, date, and factual claim in our articles comes from one of the following source categories:

  • Official service-provider pages — netflix.com/id, spotify.com/id-id, openai.com, gemini.google, hotstar.com, max.com, canva.com/id_id, and other official partners. Inline links are shown in the article.
  • Press releases and credible Indonesian media — Tempo, CNBC Indonesia, Kompas Tekno, CNN Indonesia, DataReportal, IDN Times.
  • Trusted global media — Variety, Bloomberg, Reuters, TechCrunch, for international updates relevant to Indonesia.
  • Literally Apps internal database — for our own reseller prices, synced weekly with the production catalog.

We do not use AI-generated content for factual claims. AI may help with an initial draft or structure, but every number is verified manually against the original source.

2. Price verification

Subscription prices move. Our workflow:

  • When an article is written: prices are checked directly on the provider's official page + our internal apps.ts.
  • Posts mentioning specific prices are re-reviewed at least every 60 days.
  • When there is a public price-change announcement (Netflix raise, Spotify restructure, etc.), the related post is updated within 48 hours with a new updatedAt.
  • If a provider withdraws a product entirely (e.g. Spotify Family removed in Indonesia Nov 2025), we write a new news-jacking post plus update the old post.

3. The difference between news and opinion

Some of our articles are news (announcements, policy changes, new releases). Some are opinion/analysis ("worth the wait?", "which is cheaper"). We separate them via tags and schema:

  • NewsArticle schema — posts that represent an announcement or factual reporting of a concrete event (launch announcement, price change, rebrand).
  • Article / BlogPosting schema — comparisons, guides, hot takes, and evergreen content.

Hot takes and opinion are always obvious from the heading and tone — we use phrasing like "our verdict", "honest take", "recommendation", etc. so readers do not misread them as pure breaking news.

4. Product disclosure

Almost every post recommends services we sell ourselves at Literally Apps. This is not affiliate marketing — we are a direct reseller with a transparent supply chain (accounts from official regional distributors). Every product recommendation:

  • Links directly to the product page at /app/<id> or /paket with transparent pricing
  • Is shown alongside the provider's official price
  • Comes with analysis of official alternatives (competitors) when one fits the reader's case better

5. Corrections and revision requests

If you find a factual error in our articles (wrong number, outdated claim, broken link), message our business WhatsApp with the subject "Correction — <topic>" plus the article URL. Our response targets:

  • Acknowledgement: 24 business hours
  • Verification + correction (if valid): 48–72 hours
  • Correction note: transparently added at the end of the article if the change is material

Press inquiries, partnerships, or other editorial requests: send them to our business WhatsApp with the subject "Editorial — <topic>".

6. Content we do NOT publish

  • Pirated accounts, cracking, or credential stuffing — we explicitly warn readers away from listings like these on marketplaces
  • Sponsored content without disclosure
  • Implausible "lifetime" claims
  • Misleading clickbait not supported by data in the body
  • Content that violates the Terms of Service of the main providers we reference