Privacy — Publisher

01 /

Who we are

Publisher is a native iPhone and iPad application provided by Roya Tech, an independent software studio founded by Ali Yıldırım and based in Türkiye. In this policy, “Publisher,” “we” and “our” refer to the app and its operator, Roya Tech.

02 /

Your Google connection & reports

You choose a Google account and authorize read-only access to AdMob reports through Google’s sign-in and consent screens. Publisher does not receive your Google password. It requests basic identity information and the admob.report permission; it does not request permission to change your ads, campaigns or payments.

The Google Sign-In SDK handles session credentials and renewal using its platform integration and Keychain. Name, email address and Google user ID are used for account presentation and report isolation. Publisher requests publisher account metadata, reporting currency, reporting timezone, estimated earnings, impressions, clicks, app report identifiers and related report metrics directly from Google over HTTPS.

These requests necessarily disclose your authorization, requested publisher resources and report parameters to Google. Google also receives normal network and SDK-related information under its policies. It would be inaccurate to say that no information is sent to Google.

03 /

What stays on your device

Publisher saves report summaries on your device so it can display recent reports and avoid unnecessary refreshes. Saved summaries may include publisher metadata, earnings estimates, dates, app identifiers/names, performance metrics, warnings and successful sync times.

Report files use iOS file protection and are excluded from the app’s report-file backups. They contain no OAuth token or Google password. They are separated by Google identity, publisher account, reporting currency and timezone; hashed filenames are an isolation measure, not a claim that the reports are anonymous.

Appearance, notification choices, announcement read states, reminder preferences and optional-service consent are local app preferences. Credentials are kept separately from report files. Some Keychain entries may survive reinstalling the app.

04 /

Announcements, private inbox & notifications

The optional announcement backend and APNs delivery are disabled in the current pre-release configuration. Publisher does not currently send your Google identity, Google tokens, publisher identifiers, earnings or report content to that service. Before optional hosted services are activated, their hosting and retention details must be published and any required consent obtained.

When an announcement service is offered, public feed and image requests expose normal connection metadata, including the network address visible to its host. A private inbox is a separate opt-in. It uses a random installation ID and a device-only Keychain secret; the service stores the ID and a hash of that secret. Sharing your support code may link that ID to you through your support conversation. It is not guaranteed anonymous.

Private message text is held by the developer’s service and is accessible to the developer; it is not end-to-end encrypted. Referenced artwork is public, so sensitive reports or private screenshots must not be placed in those image files.

Optional push delivery uses a separate random notification ID, an Apple device token, selected notification types, app version, delivery frequency, timezone and quiet hours. Linking private alerts requires proof of access to your private inbox. Permission is requested only after you choose to enable notifications. Apple receives the token and notification payload through APNs. Private alert previews contain generic text and a message identifier, not private message content.

These features are independent of your Google sign-in. Revenue alerts, daily summaries and server-side AdMob monitoring are not enabled. No developer advertising or analytics SDK is included in Publisher.

06 /

Retention & deletion

Local report summaries remain on the device until you delete them, switch Google accounts, disconnect, or iOS removes the app’s files. Deleting local reports keeps your Google connection; disconnecting also removes the local Google session and requests access revocation. If a request cannot reach Google, revocation may remain pending and you can remove access in Google’s account controls.

When a private inbox is available, turning it off queues removal of its registration and messages from active service records. Turning off notifications separately removes its push registration and queued alerts. An offline request may remain pending until the app is open with a connection; the app does not claim that remote deletion has already succeeded.

A message’s display end date does not automatically delete the server record. The implemented outbox cleanup removes notification jobs seven days after content expiry. Before hosted features are activated, the operator must finalize and disclose retention for messages, unused registrations, hosting logs and backups. No fixed server-backup retention is represented as currently in operation.

If you contact us by email, we receive the address and information you send. We use that correspondence to handle your request, keep it while needed for the request or applicable recordkeeping obligations, and consider deletion requests under applicable law. Use the data controls guide for precise in-app steps.

07 /

This website & cookies

This website does not set advertising cookies, use analytics trackers, embed advertising, or load third-party fonts. Its interface runs locally in your browser. There is no newsletter subscription, website account or background email submission.

The hosting provider necessarily processes normal web request information, such as IP address, request path and browser/network metadata, to deliver and protect the site. Hosting log practices depend on the provider selected for deployment and must be reflected in the published configuration. Clicking an email link opens your email application; following an external link takes you to that provider’s service.

08 /

Your choices & rights

You can delete local reports, disconnect Google, revoke Google permissions, and, where offered, turn off private inbox and notifications independently. The data controls guide explains each option.

Depending on the law applicable to you, you may have rights to access, correct, delete, restrict, object to processing or receive a portable copy of personal information, withdraw consent, and complain to the relevant data protection authority. Contact info@royatech.co to make a request. We may need proportionate information to verify your authority to act, but will not ask you to send a Google password or access token. We respond in accordance with applicable law.

09 /

Audience, changes & contact

Publisher is intended for developers and publishers managing their own authorized AdMob accounts, not as a service directed to children. Eligibility to use Google’s services is governed by Google’s own requirements.

We update this notice when the app’s data handling changes and identify the revised date at the top. Material changes, especially activation of a hosted service, must be communicated before the new processing begins. Questions can be sent to info@royatech.co.

Let’s keep it clear.

Questions about this page? Contact Roya Tech.

A clear view of your privacy.