# Confirm before publication

These are material business/legal gaps, not implementation facts. A bundled question was sent to the owner during drafting. Until answered, bracketed placeholders remain in both policies; the HTML pages are marked review drafts and `noindex`. Assumptions below are correctable and do not silently become active product rules.

| Decision | Current evidence / proposed treatment | Owner answer |
| --- | --- | --- |
| Operator/controller | Codexgram is a product name; repository author, Expo owner and Gmail account are not proof of a contracting entity. | [LEGAL NAME, ENTITY TYPE, REGISTRATION IF RELEVANT] |
| Address and contacts | No approved public legal, privacy, safety or copyright channel. Do not invent `support@codexgram...` or publish developer credentials/email. | [POSTAL ADDRESS], [LEGAL EMAIL], [PRIVACY EMAIL], [SAFETY/COPYRIGHT CHANNEL] |
| Countries and audience | Plan proposes an English-speaking 18+ beta of up to 50; distribution/actual residency unknown. | [LAUNCH COUNTRIES / EXCLUDED TERRITORIES] |
| Minimum age and enforcement | Proposed 18+ contractual rule; no DOB/age verification. Confirm adult-only positioning and appropriate enforcement. | [MINIMUM AGE / AGE-ASSURANCE APPROACH] |
| Pricing/refunds | No app billing; free beta assumed from plan. No payment/refund clause needed now. | [CONFIRM NO USER CHARGES] |
| Content and IP | Propose retention of user ownership and only a service-operation license, not advertising, AI training or resale rights. | [APPROVE NARROW CONTENT LICENSE]; [CONFIRM BRAND/PHOTO/DEMO ASSET RIGHTS] |
| Acceptable use and moderation | Propose ordinary rules against unlawful/infringing/abusive content and security abuse. No moderation console, report delivery, rate quotas or appeals operation. | [APPROVE RULES, REMOVAL/SUSPENSION PROCESS, APPEALS CHANNEL] |
| Account deletion | App route disables it; no coordinated Clerk/Convex erasure job. Manual process needs an actual owner and verified procedures. | [REQUEST PROCESS, RESPONSIBLE PERSON, RESPONSE TARGET, DELETION TARGET, LAWFUL EXCEPTIONS] |
| Retention | Hour-delayed unused-upload cleanup and author post/comment deletion are implemented. No automatic expiry for accounts/social graph/local data; backup/log schedules unknown. | [PER-CATEGORY RETENTION, BACKUP CYCLE, SECURITY/LEGAL LOG PERIODS] |
| Vendors/regions | Clerk/Convex/Expo and development ngrok observed; remote-avatar hosts possible. Dashboard projects, DPAs, subprocessors, hosting/regions and transfer safeguards not audited. | [PRODUCTION VENDOR LIST, REGIONS, CONTRACTS AND TRANSFER MECHANISMS] |
| Diagnostics and telemetry | Clerk development SDK telemetry capability; no app opt-out prop observed. No authored ads/analytics pipeline found. | [KEEP/DISABLE SDK TELEMETRY; VERIFY RUNTIME TRAFFIC AND VENDOR LOGGING] |
| Legal bases/rights | Applicable privacy laws depend on entity, markets and people; do not assert all laws apply or that the service is compliant. | [PURPOSE-SPECIFIC LEGAL BASES; RIGHTS/HANDLING, REPRESENTATIVE/DPO/GRIEVANCE OFFICER IF REQUIRED] |
| Warranties/liability | Proposed limited beta disclaimer, always subject to mandatory consumer rights. No cap can be inferred from code or free pricing. | [APPROVED EXCLUSIONS, CAP/FORMULA, EXCEPTIONS] |
| Indemnification | No commercial posture agreed. Omitted rather than inventing a broad consumer indemnity. | [INCLUDE ONLY IF JUSTIFIED AND APPROVED] |
| Disputes | No choice of law, court, arbitration, class waiver or notice/cure period can be inferred. No arbitration/class waiver included by default. | [GOVERNING LAW], [VENUE], [DISPUTE PROCESS] |
| Dates, acceptance and changes | No versioned assent or material-change notification mechanism. Draft date is not an effective date. | [EFFECTIVE DATE], [ASSENT FLOW], [NOTICE METHOD / PERIOD] |
| Release/hosting | Android development builds exist; iOS unverified. No approved public download, contact or landing domain. | [PUBLIC HOST / URL], [APPROVED INSTALL DESTINATION WHEN AVAILABLE] |

## Proposed drafting posture

The Terms cover the current free development/beta photo community, not a promise that planned chat, private accounts, reporting, moderation, calls or account deletion already work. The Privacy Policy separates cloud data, device-local prototypes and development delivery. Proposed terms that create contractual rights or obligations are identified as owner-approval items; they are not described as code-enforced controls.

Do not publish pages containing placeholders or call them an accepted/final agreement. Filling text does not implement missing controls. Counsel should review applicability of consumer, privacy, child-safety, user-content/intermediary and app-store rules for the chosen markets before release.