Monetization Authorization Agreement

1. Parties and purpose

Party A is the named developer company associated with the Rupee Go application. Priyanshu is identified by the parties as the company contact for the authorization arrangement. Party B is Bhim Singh, identified as the advertising monetization partner and associated with Meta Business Portfolio ID 4306771092917189.

The purpose of this agreement is to set out the responsibilities, permitted activities and operational boundaries applicable to the monetization of advertising inventory within the specified Android app through the listed advertising services. It is confined to the named app and does not grant rights to unrelated applications, websites, source-code repositories or other businesses.

2. Identification of the application

The Android package name is the principal identifier for the app covered by this record. A change of package name, assignment to another developer or expansion to additional apps should be dealt with under a separately confirmed written arrangement.

3. Scope of advertising monetization authorization

Within the bounds of the rights held by Party A, Party B is designated to coordinate advertising monetization activities for this application through Google AdMob and Meta Audience Network. The contemplated activities include managing applicable advertising-account configurations, coordinating permitted ad placements, reviewing ad delivery and performance, and communicating with the networks in relation to monetization of the identified application.

Any implementation or change affecting the application must be coordinated with the developer and must comply with the latest Google Play, Google AdMob, Meta Audience Network and applicable legal requirements. No activity is authorized if it would require falsely claiming developer identity, misleading a review team, manipulating ad engagement, collecting prohibited user data or otherwise violating a platform policy.

4. Relationship between developer and monetization partner

Party A remains the developer and the relevant rights holder for the app. Party B's role is operational and commercial in respect of the advertising arrangements covered by the authorization. The appointment does not itself transfer application ownership, the Play Console account, intellectual property, the software, branding, user relationships, payment credentials or the right to represent any third-party advertising platform as an approving authority.

Any exclusivity over advertising inventory must be supported by the parties' actual written authorization and must not conflict with earlier grants or the relevant network requirements. The published party details and the Meta Business Portfolio ID identify the proposed relationship but do not, by themselves, establish an exclusive-rights grant.

5. Effective date and duration

The parties state an agreement date of 05 October 2026 and validity through 04 October 2030, inclusive, unless the actual agreement is earlier terminated, replaced or amended by the parties in a valid written form. Continuation beyond the expiry date requires a fresh written extension or renewal.

6. Ad networks and business account identification

The advertising networks named by the parties are Google AdMob and Meta Audience Network. For Meta-related partner identification, the stated Business Portfolio ID is 4306771092917189, associated in this record with Bhim Singh. An AdMob Publisher ID has not been supplied for this public record and should not be inferred from the Meta identifier.

Actual network accounts, tax and payment details, inventory ownership verification, SDK integrations and any advertising seller listings must accurately match the respective provider's records. An advertising platform may accept, restrict or decline monetization independently of this website.

7. Developer company's responsibilities

Party A is expected to maintain accurate application ownership records and publish correct developer contact information, including the app-support address help@sachinteam.com. Party A should support legitimate verification of its rights, identify the appropriate company representative, maintain lawful app disclosures and work with the partner on compliant advertising implementation.

Party A remains responsible for decisions about the app's publication and for maintaining any account access and user communications it controls. Where the platform requests proof of ownership or a permission agreement, only authentic corporate records and validly issued approvals or authorizations should be supplied.

8. Monetization partner's responsibilities

Party B is expected to operate only authorized monetization accounts, to keep account identifiers and payment instructions accurate, to comply with applicable advertising policies, to protect access credentials and user information, and to coordinate material monetization changes with Party A. Party B must not use this document to claim ownership of the app or any broader developer rights.

Party B should retain meaningful operational records of the advertising activities under its control, report material compliance or delivery issues to Party A and assist with requests for genuine supporting documents, so far as lawful and permitted by the relevant network.

9. Revenue, settlement and taxes

Any revenue sharing, commission, payout schedule, expenses, tax treatment or settlement method must follow the parties' separate confirmed commercial terms and the actual advertising platform's payment records. No percentage, amount, bank account or payout promise is established solely by the public text of this webpage.

Each party remains responsible for its own applicable statutory reporting and tax obligations. Discrepancies concerning advertising earnings should be reconciled against relevant platform reports and the parties' written financial arrangements.

10. App operations, ad placement and user experience

Advertising must be implemented only in technically and legally permitted placements and should not encourage invalid traffic, accidental clicks or misleading interactions. Advertising identifiers, SDK behavior, consent requirements, user-facing disclosures and age-related safeguards must be handled under current laws and service requirements.

When software updates or technical changes become necessary, Party A and Party B should coordinate deployment and testing. The partner's advertising role does not grant unilateral authority to alter the app's core functions, brand identity, privacy practices or distribution listing.

11. Privacy, data handling and confidentiality

Both parties should limit their use of non-public account data, analytics, credentials and other confidential information to the authorized purposes. Personal data relating to app users must be handled consistently with the applicable privacy policy, consent requirements and relevant legal obligations.

Credentials, API secrets, service-account keys, revenue reports containing sensitive financial data and private verification records should not be posted on the public website. Sensitive documents may be provided through an appropriate private verification channel.

12. Verification, company authority and supporting records

Priyanshu is the named company representative for this agreement information, and ECOBAN YARN PRIVATE LIMITED is the named developer. The company's actual authorization of its representative and the partner's actual monetization rights must be supported by genuine internal or executed documents whenever evidence is requested. The public agreement page is intended to make the relevant contact details, parties, app identity and stated dates readily accessible.

Reviewers may be directed to the public Google Play listing, the developer domain and the listed contacts for inquiries. Platform-specific approval or verification status must be determined by Google or Meta through their own systems.

13. Suspension, termination and expiry

Either party should follow the termination conditions in the actually executed agreement. Material platform-policy violations, loss of relevant ownership or permission, revocation by the rights holder, or significant misuse of credentials may require stopping the affected advertising activity as appropriate under the parties' obligations.

Following termination or expiry, access privileges and advertising configuration should be reviewed, private information returned or appropriately retained, and any outstanding settlements handled in accordance with the parties' agreed terms and applicable law.

14. Changes and additional applications

Material changes to the parties, the agreed scope, covered apps, monetization channels, duration or commercial conditions should be documented and confirmed by the relevant authorized persons. This public record concerns only the stated Android application and does not automatically extend to later apps, new package names, new business entities or additional advertising providers.

15. Communications and dispute handling

App-related support can be directed to help@sachinteam.com. Developer or company authorization inquiries can be directed to priyanshukediyal@gmail.com, and partner-specific correspondence can be directed to bhimsheokand0099@gmail.com.

Any dispute concerning the arrangement should first be raised in writing with the relevant party and dealt with under the provisions of the actual executed agreement and applicable law. The website does not set a new governing-law or exclusive-jurisdiction clause not otherwise agreed by the parties.

16. Record of the named parties

The following details identify the company representative and the advertising partner in the stated arrangement. Both profiles are reproduced for contact and agreement-reference purposes.