Skip to content

Office Address

1301, Building B, Smart Valley, Country Garden, No. 50, Tiezai Road, Xixiang Street, Bao'an District, Shenzhen, CN

Phone Number

+8613686469587

Email Address

[email protected]

TV Boxes & Set-Top Boxes

Google-Certified Android TV Box: How to Verify the Claim

Google-Certified Android TV Box: How to Verify the Claim

Verify whether an android tv box is Google-certified using certificates, registry checks, DRM evidence, and SKU-level compliance records before ordering.

The procurement answer in one screen

A Google-certified android tv box is verified by a valid Google certification record tied to the exact model and production configuration, not by a catalogue label, a supplier screenshot, or a generic Android compatibility claim. A buyer should request the certificate or partner-level record, identify the licensed Google service and Android TV version, confirm the model number, and check whether the evidence matches the quoted SKU. For an android tv box entering an operator or IPTV program, Widevine L1 or PlayReady support is a separate acceptance condition and must also be confirmed for the ordered configuration.

The short decision rule is straightforward: certificate evidence, model identity, software build, DRM configuration, and factory production control must form one traceable chain. If the quotation says “Google certified” but cannot provide an independently checkable record, treat certification as unverified and put the burden of proof on the supplier. Do not substitute an AOSP statement for Google certification, and do not infer Widevine level from the Android version.

DataMax should therefore be evaluated SKU by SKU. A platform page can identify a candidate, but certification, DRM, and security provisions are confirmed against the production datasheet and order-specific compliance file. Before comparing hardware, use the canonical Android TV box for ISPs guide for the broader platform and middleware selection context. This page isolates the certification-verification angle.

What constitutes acceptable evidence

Four evidence levels appear in procurement discussions, but only the strongest combines a standard-specific document with a public or authorized registry lookup. The ranking below is editorial, not audited performance data.

Strength of conformity evidence a buyer can be handed

Supplier claim15
Generic test report42
Standard-specific report70
Certificate with public registry lookup94

Editorial qualitative planning scale (0-100), not audited or measured data; the DataMax editorial team assigned these relative scores.

A supplier statement scores 15 because it has no independent link to the device. A generic test report scores 42 because it may not cover the claimed certification. A standard-specific report scores 70 because it is more traceable, but it may omit the production SKU. A certificate with a public registry lookup scores 94 because the buyer can compare the record against the requested model. The remaining gap must still be closed through SKU-level evidence.

The editorial score does not determine whether a device passes a programme requirement. It helps procurement teams rank the quality of the handoff. A buyer receiving a generic report should request the specific certification record, while a buyer receiving a record should still compare its model identifier and scope with the purchase order. In other words, evidence quality and conformity status are separate decisions: the first says how reliable the paperwork appears; the second says whether the ordered product meets the stated obligation.

How the requirement actually works

“Google certification” is not one interchangeable badge across every device category. Buyers must identify what the supplier means: Android device compatibility, Google Play certification, Android TV certification, Google services licensing, or certification connected to a named application or service. These claims may be documented separately. A device can contain Google applications while remaining an AOSP configuration, or it can support a service such as Widevine without proving that the exact production unit passed an operator’s content-protection review.

The architecture starts with the operating system image. AOSP provides the Android Open Source Project baseline. A Google-certified commercial image normally adds an identified Google software release, device certification, and the relevant licensing or security provisions. The supplier should identify the Android version, build identifier, patch level, certification scope, and model identifier. A phrase such as “Android 14 TV” alone does not establish a Google-certified release.

Service access forms a second layer. DRM depends on a provisioned device key and the selected security level. Widevine L1 and L3 are not equivalent in hardware-backed path requirements. HDCP 2.2 or 2.3 is a separate content-protection requirement, and PlayReady is another rights-management implementation. The quotation should therefore name the required DRM and HDCP profile rather than collapse them into “DRM ready.”

AOSP or licensed OS baseline
→
Device and service certification
→
Provisioned DRM and security
→
Model and build matching
→
Production evidence audit

The evidence chain should connect each layer. An operator or integrator should not accept a certificate image whose model name resembles the quotation without matching the declared hardware, storage option, firmware and regional service configuration. Conversely, a catalogue showing “AOSP Android 14” may be appropriate for an operator-controlled middleware deployment that does not require the Google service set. The answer depends on the commercial requirements, so certification scope must be written into the specification.

A practical test is to ask which entity made each assertion. The chipset supplier supports the hardware capability; the operating-system builder controls the image; the certification holder controls the submitted record; and the manufacturer controls production configuration. One supplier may quote a platform designed for certification without being the certificate holder for the exact SKU offered. The purchase record should identify the responsible party for every layer, otherwise a failed playback test can be routed to the wrong organization.

For example, a 4K service operator may require AOSP Android 14, Widevine L1, HDCP 2.2, a fixed launcher, managed updates and a specific hardware revision. A retail product may instead require Android TV certification and the Play Store for its destination country. Both requirements use the phrase “certified,” but they produce different evidence packages. The RFQ should specify the ecosystem, application, distribution channel and market before asking for a certificate.

The platform shortlist with datasheet values

The following DataMax shortlist shows only stated platform facts. None of these entries should be interpreted as proof that a particular production SKU is Google-certified. Certification status, certificate scope, public registry identity, and the active DRM configuration must be confirmed against the production datasheet and order-specific compliance evidence.

DataMax platform data for certificate-led evaluation
ModelSoC and processorOSRAM / ROMDecodeDRM and content protectionPorts and connectivity
DM21PAmlogic S905Y4, quad Cortex-A35AOSP Android 112GB / 8GB (4GB; 16/32/64GB optional)AV1 [email protected], VP9/H.265 4K@60, H.264 4K@30Widevine L1 / PlayReady / HDCP 2.2 optionalHDMI 2.0b out x1, USB2.0 x2, TF, S/PDIF, 3.5mm AV, RJ45 100M, Wi-Fi6 2x2 + BT5.4, DC 5V/2A
DM21SAmlogic S905Y5, quad Cortex-A55AOSP Android 142GB / 16GB (2/4/8GB; 16/32/64GB optional)AV1 / H.265 [email protected] 4K@60Widevine L1 / PlayReady optional; Dolby Vision/DTSHDMI 2.0b out, S/PDIF, AV, USB2.0 x2, TF, RJ45 100M (1G optional), Wi-Fi6 2x2 + BT5.4
DM21TAmlogic S905X5, quad Cortex-A510 (ARMv9)AOSP Android 144GB / 64GB (family options)H.266/VVC [email protected] 4K@120, AV1/VP9/H.265 4K@120, AVS3 4K@120, H.264 4K@60; inline AI-SRWidevine L1 / PlayReady optionalHDMI 2.0b out (no HDMI in), USB2.0 x1 + USB3.0 x1, TF, S/PDIF, AV, RJ45 100M (1G opt), Wi-Fi6 + BT5.4
DM22QAmlogic S905X5M, quad Cortex-A55 up to 2.5GHzAOSP Android 144GB / 64GB (2/4/8GB; 16/32/64GB optional)AV1/H.265 L5.1 4K@60; inline AI-SR (no NPU TOPS stated)Widevine L1 / PlayReady optional; Dolby Vision/DTSHDMI 2.0b out, USB2.0 x2, TF, S/PDIF, AV, RJ45 100M (1G opt), Wi-Fi6 2x2 + BT5.4

The distinction between the platform descriptions matters. DM21P is positioned for 4K IPTV and operator middleware set-top box use, with AOSP Android 11 and optional Widevine L1, PlayReady and HDCP 2.2. DM21S is positioned for 4K IPTV and OTT white-label applications on AOSP Android 14, with optional Widevine L1 and PlayReady. These statements describe platform capability, not certified-model status.

DM21T and DM22Q provide newer AOSP Android 14 platforms for higher-performance use cases. Their stated decode paths include 4K@120 for DM21T and 4K@60 for DM22Q. Neither product fact authorizes an 8K output claim; the production datasheet remains controlling. For any proposal, the buyer should attach the certificate record, model identifier and DRM order option to the corresponding row.

The AV1 requirement should also remain separate from the certification claim. Netflix reports that “88% of large-screen devices (TVs, set-top boxes, streaming sticks) submitted for Netflix certification 2021-2025 supported AV1; nearly all submitted since 2023, vast majority full 4K@60fps.” That population concerns submitted devices, not every shipped unit. A buyer can therefore use AV1 capability as a technical acceptance criterion while still demanding device- and application-specific certification evidence.

Large-screen devices submitted for Netflix certification supporting AV1, 2021-2025
Large-screen devices submitted for Netflix certification supporting AV1, 2021-2025Source: Netflix Technology Blog, Dec 2025

The same figures, in searchable form:

Large-screen devices submitted for Netflix certification supporting AV1, 2021-2025
Submission outcomeSharePopulation context
Supported AV188Large-screen devices submitted for Netflix certification 2021-2025
No AV1 support12Large-screen devices submitted for Netflix certification 2021-2025

Source: Netflix Technology Blog, AV1 — Now Powering 30% of Netflix Streaming (2025-12-01)

This evidence supports an AV1 procurement question, not an inference of Google certification. For an android tv box programme, the buyer should ask whether AV1 is a contractual decode requirement, whether the application path is 4K@60, and which submitted or authorized device record supports the application claim. Keep that technical criterion separate from the Google certificate record.

Where this matters in a deployment

Certification verification changes with the operating environment. An operator issuing a managed IPTV service needs model-level software traceability, stable provisioning, an agreed middleware baseline and reproducible remote updates. A retail or distributor channel may need Google service availability, a specific storefront policy, and packaging disclosures. A commercial integrator may prioritize HDMI, network, and audio interfaces, but still needs test rights when protected content is central to the project.

In a telecom engineering laboratory, the evidentiary test becomes physical and operational. Devices are connected to HDMI capture equipment, network infrastructure, RF test instruments and display analyzers, while engineers reproduce boot, update, application and DRM flows. The photograph below shows the kind of bench environment in which a catalogue claim becomes a repeatable production test.

Google certified android tv box verify the claim
Deployment situations mapped to verification requirements
SituationPrimary requirementModel directionEvidence to request
Managed operator IPTVModel-specific firmware, middleware integration, provisioning, update control and required DRMStart with DM21P or DM21SCertificate record, software build matrix, provisioning description, DRM test report and pilot evidence
White-label OTT productConfigurable OS baseline, regional services, application rights and retail complianceEvaluate DM21SGoogle certification scope, regional service configuration, SDK or Play requirements and per-SKU compliance record
Premium cloud-gaming or UHD proposition4K media path, HDMI interface, storage and latency-related software controlsEvaluate DM21TExact firmware, display capability report, DRM configuration and service authorization
Gaming-oriented distribution4K@60 media path, storage, controller or accessory requirements and account policyEvaluate DM22QCertificate evidence, application-service status, codec test results and production test record
Hotel, retail or hospitality displayDevice recovery, centralized updates, physical interfaces and channel or service policySelect by interface and operating model rather than certification wording aloneReset behavior, update policy, peripheral test, signage workflow and per-SKU compliance evidence

The key deployment discipline is to define the required ecosystem before comparing claims. An AOSP build can be deliberate for an operator-controlled product, while a commercial Google service footprint can be necessary for a consumer-facing application programme. Certification verification is therefore not a universal quality score; it is evidence that a specific configuration meets a specific ecosystem requirement.

Consider an operator migration from a legacy set-top platform to an android tv box architecture. The migration may change the launcher, middleware and regional service footprint even if the enclosure and display remain unchanged. The acceptance plan should therefore identify the production image, test a fresh device, test an updated device and test a factory-reset device. It should also record whether protected playback depends on operator provisioning, because a successful trial on one unit does not establish fleet-wide behavior.

For a hotel deployment, the commercial requirement may be a managed storefront and remote recovery rather than a consumer certification badge. The integrator still needs a fixed model, approved firmware, service entitlement and reset procedure. A venue with several rooms can sample one hardware revision while preserving traceability through the asset register and update channel. That operational evidence often prevents more field variation than a second promotional logo.

Turning the question into a spec line

Convert the marketing question into a sequence that can be placed directly into an RFQ. The process starts with scope, moves through identity and software, and ends with production evidence. Each step should produce an auditable record.

  1. Define certification scope State whether the requirement covers Android device compatibility, Google Play certification, Android TV certification, a named Google service, or another specific authorization. Identify the destination market and distribution channel.
  2. Freeze device identity Record the manufacturer, commercial model, hardware revision, SoC, RAM/ROM option, ports and region. Do not accept “same chipset” as proof of the same certified model.
  3. Freeze software identity Require the Android version, build number, patch level, Google software package, launcher and middleware baseline. A model entry without a build record remains incomplete.
  4. Name DRM and security Specify Widevine L1 or another required level, PlayReady where applicable, HDCP version, key provisioning method and any operator security requirements.
  5. Request verification evidence Obtain the certificate or record, test-report identifiers, authorized registry details where available, and the date and production scope to which they apply.
  6. Define sample and production acceptance State that the delivered sample and production units must match the approved model and software configuration. Add the permitted change-control route and revalidation trigger.

A pasteable RFQ clause should read: “For each quoted SKU, provide the model-specific Google certification record and registry or authorized verification route, Android and Google software build identifiers, declared Widevine/PlayReady/HDCP configuration, and evidence that the certificate applies to the offered hardware and production configuration. State all deviations and require written approval before shipment.”

The first message to DataMax inquiry should contain the target model, destination country, required certification scope, Android or AOSP expectation, DRM profile, target RAM/ROM configuration, HDMI and network requirements, and expected volume programme. Buyers can also order samples, but sample testing should be designed around the stated acceptance criteria rather than used as a substitute for documentary evidence.

Turn the document request into a table with one row per proposed SKU. The columns should cover commercial model, hardware revision, Android version, build number, certificate scope, registry or authorized lookup result, Widevine level, PlayReady status, HDCP version, region, build date and evidence owner. If a quotation combines two RAM/ROM variants or two regional images, create separate rows. The commercial model alone is too broad because one certified configuration cannot silently cover every production variation.

The acceptance clause should also define what happens after an image change. A buyer may permit a patch update without restarting the entire review while requiring written notice. A launcher, regional service package, middleware or DRM provisioning change can alter the compliance relationship and should trigger a documented impact assessment. This sequence prevents “certified” from becoming an unbounded label attached to a continuously changing software branch.

For a meaningful trial, select units from the intended production configuration rather than accepting a hand-selected demonstration sample. Record the serial identifier, hardware revision and build, then test basic boot, network acquisition, application access, protected playback and recovery. A android tv box that passes the demonstration but carries a different production build should be rejected from the approval set until the discrepancy is reconciled.

Where quotations quietly diverge

The most common divergence occurs between certification scope and product description. One quotation may refer to Google Play certification for a handset-derived Android build, while another concerns Android TV certification for the set-top box. A third may simply describe access to Google Play services. These are not interchangeable procurement statements, and a dashboard label cannot resolve the difference.

Field trap

A catalogue entry listing Widevine L1 does not prove that every produced unit is provisioned at L1, that the requested PlayReady service is present, or that the commercial model appears in the applicable certification record. Require the ordered SKU, software build and provisioning method to be identified together.

Hardware naming creates a second trap. Similar model names, shared SoCs, or a “Google-certified Android TV platform” can hide changes in firmware, storage, region, services or distribution rights. The comparison must use immutable identifiers: model, hardware revision, build, certificate or registration number where available, and the option-level BOM. This protects the acceptance test from becoming a comparison between different commercial configurations.

A third trap is the use of “DRM” as a catch-all. Widevine, PlayReady and HDCP solve different parts of the content path. The supplier must identify the implementation, security level or version, and any hardware dependency. A software image can report support while the production provisioning or key service is incomplete. The acceptance evidence should show the expected flow, not merely a settings screen.

Field trap

Do not accept “certified” as the only compliance statement. If the programme changes the Android build, Google services, region, launcher, middleware, ROM configuration or firmware source, the supplier must identify whether re-certification, revalidation or a new record is required.

The commercial consequence of accepting ambiguous wording is straightforward: samples can pass while production units omit a service, the buyer can miss a release gate, and field returns can be traced to an unapproved image. These risks are larger than the effort required to add three identifiers and one verification route to the purchase order.

Other divergences appear in document control. A certificate may be valid but issued to a legal entity that is not the factory named in the quotation. A test report may cover a pre-production revision. A registry entry may use a marketing name that appears on no purchase order. Ask the supplier to state who owns the certification, who may use it, and which party is accountable for changes. The answer should appear in the quality agreement, not remain in a sales email.

Sample substitution is another frequent failure mode. A supplier may provide a retail-channel unit with one image and a different operator unit with another image. Both can be described correctly by their own commercial names, yet only one matches the buyer’s requirement. The sample schedule should therefore identify the exact quotation line, market and configuration, and the supplier should state whether the delivered unit is production-equivalent.

Questions to put in the supplier review

A factory review should test both product construction and the compliance evidence trail. The production datasheet is the starting point, followed by the authorized software image, assembly record and final test result. The reviewer should be able to move backward from a shipped unit to its approved hardware, firmware, provisioning and test evidence.

  1. Approve the controlled baseline Review the production datasheet, hardware revision, approved SoC, memory option, ports, Android or AOSP baseline, image identifier and declared service configuration.
  2. Verify incoming quality controls Inspect SMT records, AOI coverage, component traceability and inspection criteria. Relate the records to the hardware revision rather than accepting a generic factory statement.
  3. Verify software configuration control Confirm image version, signing or release control, update mechanism, partition treatment and the procedure for applying an authorized change to Google services or middleware.
  4. Verify content-security provisioning Review Widevine and PlayReady provisioning steps, HDCP configuration where required, key handling responsibility and failure handling.
  5. Review ageing and dark-room evidence Inspect the ageing plan, environmental conditions, sample loading and failure analysis for the approved model. Confirm that results are traceable to the production configuration.
  6. Audit the certificate file Match the commercial model, certification scope, registry record, dates and authorized entity to the ordered SKU. Record every deviation and its approval status.
  7. Execute sample and pilot validation Repeat boot, network, HDMI, update, application, protected-playback and recovery procedures on units drawn from the intended production configuration.

Reviewers should request a controlled evidence index: production datasheet, certificate or registry record, model-to-build cross-reference, DRM provisioning record, factory test plan, factory test result sample, change-control procedure and sample validation report. Each artifact should identify the model, hardware revision and applicable build; an undated PDF in a supplier folder is not a traceable record.

For operational scale, the process can be implemented through the factory quality review and the appropriate compliance review. For commercial commitments, use the certification evidence request. The essential control is not the number of documents, but the ability to connect each document to the unit being shipped. A short pilot, periodic audit and written change notification provide more defensible assurance than a single certificate screenshot.

The review should distinguish three owners. The factory owns hardware assembly, firmware flashing and end-of-line testing. The certification owner supplies the authorized record and explains its scope. The programme operator owns the final acceptance criteria, regional configuration and application test. Assigning each artifact to an owner avoids a common audit gap in which everyone assumes another party has already validated the same SKU.

Inspection records should follow the approved revision. For example, an AOI inspection sheet that lists only the SoC family does not prove that a specific memory option or board revision was checked. The review should ask how the inspection criterion changes when a RAM/ROM option, Wi-Fi module or connector changes. Similarly, ageing and dark-room records should identify the sample source and test duration from the applicable factory plan without converting those records into unrelated performance claims.

The pilot then closes the loop. Verify that the certificate identifier, model label, hardware revision, software build and protected-playback result all appear in one test record. If any field differs, classify the issue as a documentation mismatch, configuration mismatch or functional failure. That classification determines the owner and whether a corrected sample, revalidation or formal deviation is needed.

The comparison buyers actually make

The practical comparison is between an entry configuration and a commitment configuration, not simply between two logos. The entry path is appropriate for controlled pilots or operator middleware where the required service scope is limited. The commitment path adds traceable certification, per-SKU DRM provisioning, production controls and change governance before volume deployment.

Strength of conformity evidence a buyer can be handed (editorial scoring)
Strength of conformity evidence a buyer can be handed (editorial scoring)Source: DataMax editorial team, qualitative planning scale (0-100), not audited or measured data

The same figures, in searchable form:

Strength of conformity evidence a buyer can be handed (editorial scoring)
Evidence optionEditorial scorePlanning meaning
Supplier claim15Supports initial discussion but has no independent device link
Generic test report42May not cover the specific certification requirement
Standard-specific report70More traceable but may omit the production SKU
Certificate with public registry lookup94Enables comparison between the record and requested model

Source: DataMax editorial team, qualitative planning scale (0-100), not audited or measured data.

Comparison of entry and commitment evidence
Decision dimensionEntry configurationCommitment configurationBuyer evidence
Certification positionSupplier statement may support initial platform evaluationModel-specific certificate or authorized record linked to production SKURegistry or authorized verification result
Software controlVersion named in quotationBuild, patch level, image source and change process frozenSoftware release cross-reference
DRM positionGeneral capability statedWidevine level, PlayReady use, HDCP version and provisioning method definedPer-SKU provisioning and playback test
Factory controlGeneral manufacturing reviewSMT, AOI, ageing, dark-room and traceability linked to the approved configurationControlled evidence index and audit sample
Change managementSupplier notifies material changes informallyWritten notice, impact assessment and revalidation triggerApproved change record
Pilot acceptanceFunctional demonstrationRepresentative units complete boot, update, playback, network and recovery testsSigned pilot report

The model shortlist remains useful after this distinction is made. DM21P provides a stated 4K IPTV and operator middleware platform with AOSP Android 11 and optional Widevine L1, PlayReady and HDCP 2.2. DM21S provides a stated AOSP Android 14 platform for 4K IPTV and OTT white-label use, with optional Widevine L1 and PlayReady. DM21T and DM22Q provide higher-performance AOSP Android 14 options for premium UHD, cloud-gaming and gaming-oriented use cases. Certification remains a separate, order-specific confirmation.

For a buyer, the decisive comparison is the completeness of the chain: platform fit, exact certificate scope, software identity, DRM provisioning and factory traceability. DataMax can supply the OEM platform and supporting review process, but the buyer must specify the ecosystem requirement and the evidence required for the delivered SKU. The appropriate first message to DataMax should name the target models, certification scope, destination market, DRM profile and production evidence needed for approval.

An android tv box programme should also compare the acceptance cost rather than the certification wording. The entry route may be faster for a laboratory evaluation, but it leaves more questions open about production equivalence and change control. The commitment route adds model-to-build mapping, authorized registry evidence, factory records and signed pilot results. It is the appropriate choice when the device is distributed beyond a controlled test environment.

Before release, ask the supplier to close the comparison with a signed matrix. One row represents one offered configuration; each column states the evidence owner and approval status. Any cell containing “same platform,” “optional” or “to be confirmed” becomes a release blocker until clarified. That final matrix gives procurement, engineering and operations one shared definition of the accepted android tv box.

Further reading

FAQ

Does Widevine L1 mean the Android TV box is Google-certified?

No. Widevine L1 describes a DRM security level, not Google platform certification. An android tv box may support Widevine L1 while using an AOSP configuration. Verify certification scope, software build and DRM provisioning separately for the exact SKU.

Can a supplier certificate PDF replace a registry check?

Not always. A PDF may be genuine while applying to a different model, revision, software build or authorization holder. Request the record and an authorized lookup route, then match the commercial model and manufacturing configuration to the quotation.

Is an AOSP Android 14 product automatically Google-certified?

No. AOSP identifies the Android Open Source Project baseline. It does not prove that a device has Google Play certification, Android TV certification, Google service licensing or the specific regional services required by the programme.

Which DataMax platform should an IPTV operator review first?

DM21P is stated for 4K IPTV and operator middleware set-top box use, while DM21S is stated for 4K IPTV and OTT white-label use on AOSP Android 14. Both list optional Widevine L1 and PlayReady. Confirm certification status, hardware revision, build and DRM configuration against the production datasheet.

What evidence should a first RFQ message contain?

Include the target model, destination market, required certification scope, Android or AOSP requirement, DRM and HDCP profile, RAM/ROM option, interface requirements, production volume and required test evidence. Ask the supplier to identify any model, build or configuration for which certification cannot be confirmed.

How does codec support relate to certification?

Codec capability is a hardware and software capability, separate from certification. DM21S states AV1 and H.265 [email protected] 4K@60, while DM21T states AV1, VP9 and H.265 4K@120. A buyer still needs application, service and device authorization evidence for the intended android tv box.

DataMax Engineering Team

Written by

DataMax Engineering Team

The DataMax Engineering Team writes from our Shenzhen hardware, RF and firmware labs next to our own SMT and assembly lines. Articles cover board-level design, RF tuning, certification pre-compliance and production validation for Android TV, Google TV and smart-display products.

Leave a comment

Your email address will not be published. Required fields are marked *

Keep reading

Stay Updated with the Latest TV Box Trends

Subscribe to our newsletter and be the first to know about new products, OEM/ODM tips, exclusive offers, and factory updates.

Your experience on this site will be improved by allowing cookies.
Chat with us on WhatsApp