What the app specifies
These are the specifications, not an argument for installing anything. The ACE66 app is an Android package we host and sign ourselves, because Google Play's developer policy does not list real-money online gambling applications for the Malaysian store, which is why online casinos serving Malaysia distribute an Android file directly. Every line below can be checked on the handset in your hand: the build number, the permissions the operating system has granted, the space the files occupy, the browser versions we test against.
Three routes reach the same online casino floor. A signed Android package. A Safari home-screen web app on iPhone. An ordinary mobile or desktop browser with nothing installed at all. The route is a delivery mechanism and carries no properties of its own: the same 2,400+ games from the same 26 studios, the same certified builds, the same cashier and the same 1.2% cashback sit behind all three.
Everything a member would want to know about their standing attaches to the account rather than to the client: member ID, the MYR wallet, the wagering counter, the tier ceiling, the position of a cash-out in the queue. A player who claims the 120% welcome bonus in a browser on Monday meets the same wagering requirement in the app on Tuesday, down to the ringgit. A session opened in the app and a session opened on a borrowed laptop are read by the same checks, which ACE66 Login sets out field by field.
Device requirements, by route
These are the minimums we test against, not a recommendation. A handset below one of them is not locked out of anything; it falls back to the browser, which serves the identical casino, the same online slot titles and the same table games, at the cost of a sign-in each visit.
| Route | Minimum build | RAM | Free space | Note |
|---|---|---|---|---|
| Android app | Android 7.0 | 2GB | 250MB | Signed package, direct download |
| Android app, dealer video | Android 9.0 | 3GB | 250MB | Hardware H.264 decode |
| iOS web app | iOS 14, Safari | 2GB | Negligible | Share, then Add to Home Screen |
| Mobile browser | Chrome 90, Safari 14 | 2GB | None | Nothing installs |
| Desktop browser | Chrome 90, Edge 90, Firefox 88 | 4GB | None | 1280px wide for the table layout |
Read the RAM column against what else is resident on the phone rather than against the app alone. At 2GB the application runs correctly and is evicted from memory as soon as it goes to the background behind a messenger and a banking app, so the next open costs the full start-up rather than the resumed one.
The second row is the one that catches older handsets. Reels, a bet slip and a fishing room are small payloads: a slot spin is a few hundred bytes of result over animation the device already holds. A dealer game is continuous video, and a phone without hardware decoding for it renders in software, heats up and drops frames while the account and the real money behind the picture stay perfectly correct.
Where the storage actually goes
The download runs to about 42MB. The install asks for roughly 250MB free, which is higher than the download because the package and the unpacked application occupy the disk at the same time for the length of the job. Once the installer is discarded the application itself settles at about 95MB.
Cache is what grows after that. Casino shell, fonts, icons and game tiles are written to local storage so that an open costs a second rather than four, and on ordinary use that reaches 60MB to 90MB within a month, which is the 180MB figure quoted at the top. Android lists the split under Settings, then Apps, then ACE66, then Storage.
Clearing the cache is safe at any time and costs one slower start. Nothing about the account is held on the phone, because the balance, the bonus ledger and the payout queue live on the platform rather than the handset, so an uninstall removes local files and nothing else: a pending withdrawal continues through the queue while the app is gone, under the timings set out at ACE66 Withdraw. Dealer video is never written to disk, and a screenshot exists only because you saved it.
Permissions, and exactly what each one grants
Four permissions are involved and the first of them is granted to your browser rather than to us. None of the four touches money: a deposit or a payout runs on the same payment page the browser uses, over TLS. The table is the whole list.
| Permission | Granted to | What it allows | Required | Revoke at |
|---|---|---|---|---|
| Install unknown apps | Your browser or file manager | That one app may hand Android an installer | Once, to install | Settings, Apps, that browser |
| Notifications | ACE66 app | Cashier stage changes, settlement alerts, maintenance notices | No | Settings, Apps, ACE66 |
| Camera | ACE66 app | Photographing a document at the first withdrawal | No | App permissions, after use |
| Photos and media, read | ACE66 app | Attaching a saved screenshot to a ticket | No | App permissions |
Not requested, at any version: contacts, SMS, call log, precise location, microphone, accessibility services, device administrator. The whole list is the four rows above, which is why the install finishes in about twenty seconds and puts you straight on the casino floor.
Permissions govern installing, not running. Switching the install right off the moment the install finishes leaves the app working exactly as before, and Android will ask for it again at the next update. The three optional permissions can be refused at the prompt or revoked later, and refusing all three costs you a push alert, a camera shortcut and an attachment picker.
Build numbers, signing and the update route
Builds carry a three-part number in the form 4.2.118: feature release, point release, build. The number is printed in the app under Settings, then About, beside the cashier API level it is talking to. Quote both when you open a ticket about a screen that behaves oddly, because a studio patch and a shell patch ship on different days.
Updates arrive by prompt at launch rather than from a store. The prompt names the new number and what changed, and installing over the existing app keeps your sign-in and your settings. A point release is usually 8MB to 20MB. A feature release downloads the whole 42MB package again. We do not install anything silently and have no mechanism to do so.
Android compares the signing certificate before it will replace an installed app, which is why a point release installs straight over the build already on the phone and leaves the session and the settings where they were. An installer that stops partway is reporting a certificate mismatch rather than a fault on the handset.
The cashier inside the app offers exactly the payment options the browser offers, all of them in MYR: Touch 'n Go, DuitNow, Boost, GrabPay and FPX, from RM10 and landing under a minute. No build has ever carried a crypto option. The last three builds reach the cashier API, which works out at roughly 90 days, and past that the app declines to load the casino rather than display odds that may no longer be current. What the app carries from its first launch is the same 120% welcome bonus to RM1,688 and the same 1.2% rebate the browser carries, because the two read one account and one ringgit wallet.
Browsers we test against, and what fails first below them
Chrome 90, Safari 14, Edge 90 and Firefox 88 are the floor, and on Android the version that matters is often Android System WebView rather than the browser icon you tapped, because an in-app browser inside a messenger renders through it.
Below the floor the failure is ordered rather than total. The casino loads, the online slot games run, the cashier works, and the dealer stream is the first thing to break because it needs media extensions that older engines do not carry. A baccarat, blackjack or roulette table at ACE66 Live Casino that shows a black frame with a working bet layer underneath is almost always this and almost never the studio.
Two settings matter more than the version number. The session cookie is first-party and required, so a browser set to block all cookies signs you out at every navigation. Private mode works correctly and keeps nothing, which is the point of it. On desktop the table layout wants 1280px of width, and zoom past 150 per cent reflows the bet slip into a column.
Uninstalling, reinstalling and moving to a new phone
Uninstalling removes the application and its cache from the handset and touches nothing else. Balance, tier, wagering progress, a deposit bonus still clearing, saved payout accounts and any open ticket are held on the account, which is why there is no backup step and no export to take with you. That is ordinary for real money gaming: the client is disposable and the ledger is not.
A reinstall is the same download from the same page, and the first sign-in on an unfamiliar handset is read as exactly that. Expect a verification step of a minute or two: the device is new to the screening that watches account access, and a new device plus a new network plus an unusual hour is the shape it is built to pause on.
On a new phone, sign in once on the browser before you install, so the verification happens while you still have the old handset to hand for a code. Sessions on devices you no longer hold can be ended from the account rather than left running. An account opened for the first time on either route starts at ACE66 Register, and the fields asked for there are the same in the app and in a tab.