Legal · Privacy Policy
Privacy Policy
This document says exactly what this service stores, why it stores it, how long it keeps it, and what it does with data obtained from your Google account. It describes the software as built, not as intended.
Who this covers
An account holder who registers at https://ampuh.biz.id. There is no other way to obtain an account, and the service has no free tier that operates without one.
What is collected, and where it goes
Nothing is collected by observation. Every item below is either supplied by you, produced by an action you started, or recorded because a security event happened.
| What | Why | How it is stored |
|---|---|---|
| Email address and display name | To identify your account and send transactional messages you have asked for | Plain, because an address must be readable to be emailed |
| Password | To sign you in | Never stored. Only an Argon2id hash, which cannot be reversed into the password you chose |
| Websites you add as projects | They are the subject of the audits you run | Plain. A hostname is public information |
| Audit results for your own sites | They are the product | Plain, and visible only to your account |
| Sign-in and account-change history | So you can see whether somebody else has used your account | The event and its time are plain. Your IP address and browser are stored only as one-way hashes and cannot be turned back into an address or a device |
| Google account credentials you connect | To call the Google APIs you asked this service to use on your behalf | Encrypted with AES-256-GCM before being written |
| Provider API keys you supply | Your own quota is used for your own work | Encrypted with AES-256-GCM. Only the last few characters are ever displayed back to you |
| Rate-limiting counters | To stop the public forms being abused | A hashed identifier and a count. No address and no URL |
No payment card details are collected anywhere in this service. No advertising or analytics service is embedded in it, so no third party observes your use of it.
Google user data
If you connect a Google account, this service asks Google only for the access the connection method you chose needs, and uses it only to perform the operations you request.
- Every method: your Google account's email address and basic profile, to show which account is connected; your Search Console properties and performance data, to report on them; and site verification, to prove ownership of a website you add.
- Methods 01 and 02 only (an OAuth client from your own Google Cloud project): the Google Cloud projects you nominate, to enable APIs and create and test the API keys you asked for; read-only access to Google Analytics properties you link to a project; and the Google Drive files this service creates, when you ask it to save a report there. It cannot see any other file in your Drive.
AmPuH SEO Intelligence Next's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In plain terms, and each of these is a statement about the software as built: Google data is not sold, not transferred to anyone except to provide or improve features you are using, not used for advertising, and not read by a human except where you have given explicit permission for a specific support request, where it is needed for security, or where the law requires it. Google data is never used to develop, improve or train artificial intelligence or machine learning models, including generalised or foundational models. Your access and refresh tokens are encrypted at rest and are scoped to your account alone; no other account can use them.
You can disconnect Google at any time from the connection settings inside the service. Disconnecting revokes the token with Google and deletes the local copy, along with the project, API state and property records that depended on it.
Artificial intelligence features
Where this service uses a generative model, it does so with an API key you supply, on your own quota, and only for content you have asked it to explain. Plain-language explanations of audit rules are written once and reused for every customer, so no page of yours is sent to a model in order to produce them. AI output is never written into a customer-facing report without a human having reviewed and approved it first. No data obtained through Google APIs is used to train, fine-tune or improve any artificial intelligence or machine learning model, by this service or by anyone it works with.
How long things are kept
- Your account and projects: until you ask for them to be removed.
- Sign-in and account-change history: failed sign-ins and account changes are kept indefinitely, because they are the evidence you would need if your account were attacked. Routine successful sign-ins are trimmed to the most recent 200 per account.
- Read-only operational records: 30 days.
- Records of a change made at a provider on your behalf: 180 days, so a dispute can be settled within a normal audit cycle.
- Rate-limiting counters: 30 days.
- Reports you generate: ad hoc analysis output is held only for your browser session and is discarded when you sign out. A report you deliberately save is kept for a period set by your plan - 30 days on Basic, 90 on Pro, 365 on Advanced - and each project keeps a bounded number of them, so saving a new one can retire the oldest unpinned report you have not touched. Pinning a report extends it to 365 days and exempts it from that trimming. Nothing here is kept forever, and you can delete any of them sooner.
Your choices
From inside your account you can change your name, change your email address (which requires confirming the new one before it takes effect), change your password, and sign out of every other browser at once. You can disconnect any provider you have connected. You can turn off service incident emails, the message we send when a provider your account uses stops working and when it is back; we record only which incident each message was about, and delete that record after 90 days. To have your account and its data removed, write to the support address at the top of this page.
Where data is processed
This service runs on shared hosting and stores its data in a single database in that environment. Requests you initiate are sent to the providers you connect, which are operated by those companies under their own policies: Google, Bing, Yandex and IndexNow participants.
Security, stated plainly
Traffic is served over HTTPS. Secrets are encrypted with AES-256-GCM. Passwords are hashed with Argon2id. Addresses and browser identifiers are hashed rather than stored. Every outbound request this service makes is restricted to public hosts on standard web ports, with private and internal address ranges refused, so the service cannot be induced to fetch something inside its own network.
No system is beyond compromise, and this document does not claim otherwise. What it does claim is that the items marked encrypted or hashed above are genuinely stored that way.
Cookies and local storage
This service sets three cookies and no others. Every one of them is first-party, marked Secure and HttpOnly so no script can read it, and none is used to observe you. There is no analytics cookie, no advertising cookie and no third-party script anywhere in this service, which is why you are not being asked to consent to anything: there is nothing here to consent to.
| Name | Why it exists | How long it lasts | Why no consent is asked |
|---|---|---|---|
ampuh_session | Keeps you signed in and carries the token that protects every form on the site from being submitted by another website on your behalf | Until you close the browser. It is never written to disk with an expiry date | Strictly necessary. Without it you cannot sign in at all, which is the service you came for |
ampuh_device | Remembers a browser you marked as trusted, so two-factor authentication does not challenge you on it again | 30 days, fixed at the moment you ask for it. Using the browser does not extend it, and you can revoke it from your security settings | Set only because you explicitly asked for it, by ticking that box. Never set otherwise |
ampuh_installer | Holds the installer's own session while the first administrator account is being created | Until you close the browser, and only during installation | Strictly necessary, and no ordinary reader of this page will ever receive it |
Four pages set nothing at all. This document, the Terms of Service, the instrument
manual and the free tools each load their configuration by hand and deliberately start no session, so
visiting them stores nothing on your device and leaves nothing behind to delete. Everywhere else,
including the landing page, ampuh_session is set on the first request -
it carries the token that protects every form on this site, so it exists before there is a form to
protect. It still holds nothing about you until you sign in, and it is still gone when you close the
browser.
One page uses your browser's own database, and only on your computer. Source Audit (/source-audit/) keeps, in this browser's IndexedDB, a reference to the project folder you chose, a fingerprint of each relevant file it read, any paths you told it never to offer for AI review, the active template you chose and, only if you ask it to remember them, your notes for the reviewer, so the next scan can tell you what changed. It holds no file contents: the redacted copies its secret guard prepares exist only in the open tab and are gone when it closes. If you send an AI review as a batch, it also keeps, until the answers are collected or the batch is cancelled, the name Google gave that job and, for each request in it, the paths, line ranges and fingerprints of the parts it carried, never their contents and never your key. None of it is sent to this service, and "Forget this project" on that page deletes it. No other page writes to local storage, session storage or IndexedDB, with one exception that holds nothing about you. The free tools keep what you type in the page itself, which is why reloading a tool clears it and why closing the tab is genuinely the whole of the matter.
Signed-in pages remember, for the open tab only, that you hid a service notice. When a provider this service depends on is down, signed-in pages show a notice you can hide. Hiding it keeps one entry in this browser's session storage: a 16-character code that identifies that notice, so it stays hidden on the next page and comes back when the situation changes. It holds nothing about you or your account, is never sent to this service, and is deleted by your browser when the tab closes.
When you ask Source Audit for an AI review, a second opinion or to save a report to Google Drive, your browser talks to that provider directly. The AI review sends the redacted copies of the files the page offered, and any notes you wrote for the reviewer after the secret guard has read them, from your browser to Google Gemini, on the API key you type into that page. The key is held in the open tab only: it is never stored and never sent to this service. What Google does with that content is governed by your own agreement with Google; on Gemini's free tier Google may use it to improve its products, and the page asks you to confirm you understand that before anything is sent. If you ask for a second opinion, the critical and high findings and an excerpt of each file they cite go the same way, from your browser to OpenAI or Anthropic on the key you type for it, under your agreement with that provider; that key, too, never leaves the tab. Saving a report sends it from your browser to your own Google Drive. A review sent as a batch is held by Google as one job until this page collects its answers and deletes it, or until Google's own retention for batch jobs ends. For any of these, this service records only counts, the AI provider, the tokens used and the two Drive file ids, never the files or the report. Match-live and live correlation ask this service to read the public pages of a site this account has verified: public static files by their URL paths, or the home page, which is handed to your browser and compared there; no file, finding or quote is sent for either. Remove on a row of that page's history deletes this service's record of that audit; the report itself stays in your Google Drive or wherever you downloaded it, and this service never deletes a file in your Drive.
If a cookie banner, a consent pop-up or a tracking script ever appears on this site, it did not come from this service. Nothing in this codebase renders one. Tell us at the address below, because on this product that would be a security finding rather than a marketing decision.
Should this ever change - a payment provider at checkout is the realistic case - this section changes with it, and anything genuinely optional will be introduced with a proper choice: refusing as easy as accepting, nothing switched on before you say so, and your decision recorded with its date.
Changes to this policy
If this document changes materially, the effective date at the top changes with it. Continuing to use the service after that date means the revised version applies.
Contact
Questions about this policy, or a request to remove your data: royocta2025@gmail.com.
See also the Terms of Service.