Fifth Third — frequently asked
Fourteen answers to the questions we hear most about the Fifth Third Edition of FifthThirdStore.
Why is it called Fifth Third?
Fifth Third is our internal release codename — the fifth product line inside FifthThirdStore, third quarterly batch. Every module you install today ships under the Fifth Third Edition shelf name and is signed with the Fifth Third release key. When the batch rotates in 2026-Q4 the codename will roll to the next one.
What is a Fifth Third module?
A small-footprint Android app hand-picked, packaged, signed and provisioned to your FifthThirdStore workspace. Every Fifth Third module ships as a standard Android package and installs through the system PackageInstaller.
How often do you ship new Fifth Third releases?
Every Wednesday. The Fifth Third Wednesday drop lands a mix of new modules, minor version bumps and maintenance patches. The changelog documents the exact payload of every batch.
What Android versions are supported?
The Fifth Third Edition targets Android 9 (API 28) and above. A handful of modules require Android 12 for the underlying platform APIs — the module data sheet lists the minimum version.
How many devices per workspace seat?
Three Android devices per seat, enrolled through the FifthThirdStore workspace app. A sandbox device counts separately and does not consume a seat.
Do Fifth Third modules require root?
No. A single module (BatteryProfile Pro) exposes optional root or Shizuku features for per-app CPU governor pinning; the rest of the shelf runs on the standard Android API surface.
How is a Fifth Third module signed?
With the Fifth Third release key. Every APK carries the standard v2 and v3 signatures. The public certificate is displayed on the security whitepaper page and pinned inside the FifthThirdStore workspace app.
What data do you collect on-device?
None per module unless the module explicitly needs it (for example the sensor logger reads sensors, the media caster reads local media). Nothing is uploaded to a cloud back-end without the user starting the transfer.
What happens when I cancel a Fifth Third subscription?
The module keeps running for the remainder of the paid period. On expiry the workspace entitlement is revoked and the module stops receiving updates on the Fifth Third Wednesday track. Your local data stays on-device.
Do you offer sandbox devices?
Yes. Every workspace gets one sandbox device by default. The sandbox device receives every new Fifth Third batch four days early so you can test before rolling out to the enrolled fleet.
Can I invoice through a company?
Yes. Checkout accepts a company name and VAT number. Invoices are issued monthly, in euro, from FifthThirdStore d.o.o. in Podgorica.
Do you accept crypto?
No. Card and SEPA direct debit only.
Is there a Fifth Third API for developers?
Yes — the marketplace API exposes entitlement, provisioning and audit-log endpoints under the /v1/fifth-third/ path. Access is included with every workspace.
How do I contact the Fifth Third editors?
The editorial team behind the Fifth Third Wednesday drop reads mail sent to support@fifththirdstore.org. For data-protection requests use dpo@fifththirdstore.org.