Monthly Budget
Sia Makerlab 제품 포트폴리오 통합 페이지에서 제공하는 개인정보처리방침입니다.
Monthly Budget / 월급 사이클 가계부
Last Updated: September 5, 2026
Effective Date: September 5, 2026
Revision: 1.0
| Version | Date | Changes |
|---|---|---|
| 1.0 | September 5, 2026 | Pre-release policy updated to reflect the current app, optional Google Drive household sync, CSV export, advertising, and Google Play Billing |
This Privacy Policy explains how Monthly Budget (the "App") handles information. The App is an Android salary-cycle budgeting application operated by Sia Makerlab.
| Item | Details |
|---|---|
| App | Monthly Budget / 월급 사이클 가계부 |
| Package | com.siamakerlab.monthlybudget |
| Operator | Sia Makerlab |
| Contact | sia@siamakerlab.com |
| Website | https://apps.siamakerlab.com/monthly-budget/ |
The App does not create a Sia Makerlab account and Sia Makerlab operates no backend for budget, Google-account, sync, or purchase data. The optional Google Drive sync and Google SDKs described below can nevertheless transmit information off your device.
Core budgeting works offline. Budget data is first stored in the App's local Room database.
Google Drive sync is optional. If enabled, the App signs you in with Google, requests the limited Google Drive drive.file permission, and reads and writes JSON event files in a folder that you create or explicitly select. The folder may be shared with household members. Sia Makerlab does not receive or host those files.
Advertising, consent, purchases, app updates, and review prompts use Google services independently of Drive sync.
The App can store the following locally:
This information is used only to provide records, calendars, salary-cycle calculations, search, filters, and statistics. Sia Makerlab cannot access locally stored budget data.
If Drive sync is enabled, budget entries and custom classifications are included in JSON sync events uploaded to the selected Drive folder. These files can contain financial information and user content, including amounts, titles, notes, dates, categories, payment methods, recurrence settings, and deletion markers.
Google sign-in is used only for optional Drive sync; it does not create an App account. The App reads the email address, account name, and profile-photo URL contained in the Google ID token and stores them locally in DataStore.
To identify who created or last changed a shared entry:
A display-name change does not retroactively remove the author snapshot from older Drive events.
The App locally stores the selected root and events folder IDs and names, last-sync time, sync cursor, and a randomly generated device UUID. The device UUID and derived author ID can be included in event metadata uploaded to Drive.
The App uses short-lived Google access tokens while calling the Drive API. It does not operate a server that stores access tokens or refresh tokens, and no OAuth client secret is embedded for this flow.
When you request an export, the App writes the selected month's or year's date, type, amount, category, payment method, title, and memo fields as a CSV file to the location you choose with Android's system file picker. Sia Makerlab does not receive the file. Storage, sharing, and deletion of the exported file are controlled by you and the chosen storage provider.
The App uses Google Mobile Ads SDK and Google User Messaging Platform (UMP) for adaptive banner ads, app-open ads, consent handling, analytics related to ads, and fraud prevention. Depending on device settings, consent, region, and Google's configuration, Google may automatically process and share:
Advertising is not requested until UMP reports that ads may be requested. The App is not configured as directed to users under the age of consent. The App currently has no dedicated settings control for reopening the UMP privacy-options form.
The optional remove_ads product is a one-time, non-consumable purchase processed by Google Play. The App receives the purchase object and purchase token to confirm and acknowledge the purchase and caches the final ad-removal entitlement locally. Sia Makerlab does not receive card numbers, bank details, or billing addresses and does not store purchase data on its own server.
Google Play In-App Updates and In-App Review may process Google account, device, app, and interaction information under Google's terms. Sia Makerlab does not operate a separate server for review content or update history.
The App does not currently use Firebase Analytics, Firebase Crashlytics, Sentry, or a Sia Makerlab remote analytics or logging server. Sia Makerlab does not receive your budget database, Drive files, Google profile, CSV exports, or purchase token.
| Permission | Purpose |
|---|---|
| INTERNET | Google sign-in and Drive sync, AdMob and UMP, Google Play Billing, updates, and reviews |
| ACCESS_NETWORK_STATE | Check connectivity before network operations |
The App requests no contacts, camera, microphone, location, or broad storage permission. CSV destinations and Drive folders are selected through system or Google pickers.
Information is handled to:
Drive sync, CSV export, and ad removal are optional. Core budgeting remains available without Drive sign-in.
| Provider and service | Purpose and information involved | Provider policy |
|---|---|---|
| Google Credential Manager and Identity Services | Google sign-in, ID-token profile fields, Drive authorization, and short-lived access tokens | Google Privacy Policy |
| Google Drive API and Google Picker | Store, list, download, and share JSON events in the folder you choose under drive.file access | Google Privacy Policy and Google Drive Terms |
| Google Mobile Ads and UMP | Ads, consent, ad analytics, and fraud prevention; may process IP address, interactions, diagnostics, and identifiers | Google Privacy Policy |
| Google Play Billing | Process, acknowledge, and restore the one-time remove-ads purchase | Google Play Terms |
| Google Play In-App Updates and In-App Review | App update delivery and review prompts | Google Privacy Policy |
Third-party processing, retention, international transfers, and user controls are governed by the relevant provider's policies and your account settings.
We do not sell or rent your personal information.
When you enable Drive sync, you instruct the App to upload data to your chosen folder. Anyone with sufficient access to that shared folder can read, copy, change, or delete its JSON files. Take care before entering sensitive details in titles, notes, custom categories, or payment-method names. The folder owner and Google control sharing permissions, recovery, and permanent deletion.
Google may process data for the services in Section 6. We may disclose information we actually possess if legally required, but Sia Makerlab does not hold the App content described above on its servers.
Local budget records and settings remain until removed through the App, Android settings, or uninstallation. The budget database and App settings are excluded from Android Auto Backup and device-transfer backup rules.
Deleting an entry creates a logical deletion record so other devices do not restore it during synchronization. A tombstone and earlier Drive event files can remain after an in-app deletion.
Signing out removes the locally stored Google email, account name, profile-photo URL, and connected Drive folder IDs. Signing out does not:
To remove Drive copies, delete the relevant files or folder and empty Drive trash as appropriate. To revoke access, use your Google Account's third-party connection settings. Shared-folder owners and members may retain copies consistent with their access and Google's policies.
You control CSV files after export. Google retains and deletes advertising, account, Drive, purchase, update, and review data under its own policies and controls. The Google Play purchase entitlement may remain associated with the purchasing Google account and can be restored after reinstalling the App.
Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of personal data and to withdraw consent.
You can:
Because Sia Makerlab does not hold your App content on its servers, most access, correction, portability, and deletion actions occur on your device or through Google. For questions or requests directed to Sia Makerlab, email sia@siamakerlab.com.
The App uses Android app-private storage for its Room database and DataStore. Network calls to Google services use HTTPS/TLS. Drive access is limited to files the App creates or that you explicitly select or share with the App under the drive.file scope.
The local database and Drive JSON files are not encrypted end to end by Monthly Budget. Local protection relies on Android's application sandbox and device security; Drive protection relies on Google account and folder access controls. Shared-folder editors can access or alter synchronized data. No system is completely secure, so keep device and Google-account credentials protected and export backups carefully.
The App is a general-audience budgeting utility, is not designed for or directed to children under 13, and does not participate as a child-directed app. In jurisdictions with a higher digital-consent age, including parts of the EEA, users below that age should use the App only with appropriate parent or guardian involvement.
Google may process information in countries other than your own. Sia Makerlab does not receive a copy of your Drive data, but choosing Drive sync directs Google to store and process it under your Google account. Review Google's policies for information about processing locations and safeguards.
This is version 1.0 for the pre-release App. We may update this Policy when features, SDKs, permissions, or data practices change. We will change the Last Updated date and provide additional notice when required by law. A later edit before production may remain within version 1.0; revisions after production may receive a new version number.
Sia Makerlab
This Policy is authored in English. If a translated version conflicts with it, the English version controls to the extent permitted by law.