modpad.fun
“modpad”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).
What it is
- The site describes itself as: “An independent agency with a deep skill set, big ideas, lots of heart and a global reputation.”E2
- It's built with Vue and React (common tools for building web apps).E8E9
- Notable building blocks in its code: Three.js (3D graphics).E10
- In your browser it saves small bits of data in your browser.E13
- It has sections such as /fr.E27E28
- While loading, it called 7 endpoints on its own servers, such as /desk/, /desk/data/docs.json, /assets/juno/sixty/envmap.exr and 4 more.E16E17E18E19
Where your data goes
Analytics & trackingCount visits and record what you do on the page. 1
| static.cloudflareinsights.com | Cloudflare Web Analytics: page-view counter | 1×E6 |
How key features work
Loading its content
Its content loads from its own API while you browse (/desk/, /desk/data/docs.json, /assets/juno/sixty/envmap.exr, /desk/data/presets.json and 2 more).E16E17E18E19E20
/desk//desk/data/docs.json/assets/juno/sixty/envmap.exr/desk/data/presets.json/desk/data/sample.json/desk/data/species.jsonDrawing and editing in the browser
The page draws and edits graphics in your browser using Three.js (3D graphics) and the canvas.E10E15
Three.js (3D graphics)canvasMeasuring what you do
Visits and clicks are measured with Cloudflare Web Analytics and Google tag (gtag.js) (found in its traffic or its code).E6E11
Cloudflare Web AnalyticsGoogle tag (gtag.js)Saving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E13
local_storagePages and API calls
Pages it links to
/fr/Endpoints
Called while loading (seen) or named in the code (code).
| modpad.fun/desk/ | seenE16 |
| modpad.fun/desk/data/docs.json | seenE17 |
| modpad.fun/assets/juno/sixty/envmap.exr | seenE18 |
| modpad.fun/desk/data/presets.json | seenE19 |
| modpad.fun/desk/data/sample.json | seenE20 |
| modpad.fun/desk/data/species.json | seenE21 |
| modpad.fun/desk/sound/computer-click.wav | seenE22 |
| /api | codeE23 |
| /api/rfp-enquiries | codeE24 |
| /api/job-enquiries | codeE25 |
| /api/general-enquiries | codeE26 |
Evidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- REA hit its size budget on parts of 1 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id uhqcpvlY.