Review access and documents

Test account

If the app requires sign-in, fill in “Login / Email” and “Password” under “Demo access for reviewers” on the “Distribution” tab.

Use a separate account with demo data and access to the features under review, without administrator permissions. It must remain functional until the review is complete.

If sign-in requires a one-time code or a feature requires payment, agree with the publication team in advance on a test flow that does not need your involvement or a real charge. Do not change the security of regular accounts for the review.

Support and documents

Under “Legal information”, fill in:

Field	What to enter
Privacy Policy	Full URL of the published document
Terms of Use	Full URL of the published document
Support	Support page URL or email, such as support@example.com

Document pages must open without authentication. Click outside each field to save its value.

Generate a template

If you do not have your own documents, click “Generate template”. If no support contact is set, enter a URL or email in the dialog and confirm. SiteCargo will fill in the links to both documents; if the contact is already set, generation starts immediately.

Generation replaces the URLs in the privacy policy and terms fields. Open the generated documents and check the name, contacts, and description of data processing. Adapt the template to how your website, analytics, and third-party services work.

Additional details

The builder does not yet have separate fields for categories, age ratings, or data questionnaires. When the publication team requests them, prepare:

• the app's purpose, audience, and countries of distribution;
• details about chats, user-generated content, paid features, and age-restricted content;
• what data the website and app collect, why they collect it, which services receive it, and how users can delete it.

Include connected analytics, payment, map, and authentication services. The details must match the app's actual behavior and documents.