Privacy Policy

Who is responsible

PRO APP DEV, Ireland, operates EYEWIT and is responsible for your personal data. This policy covers the contributor app, Newsroom, Control and this website. Company registration and postal contact.

For privacy questions or to exercise your rights, contact contact@eyewit.media. We do not require you to send an identity document with an initial request.

Information we handle

Accounts: email address, account identifiers, authentication records, optional name, profile and verification status. Contributor setup requires a country of residence. A phone number is optional; if Support has a specific reason to offer a callback, you can choose to add it in your signed-in profile. These are private contact details, not proof of identity. Google or Apple sign-in shares the identifiers and profile information returned by your chosen provider, including an Apple relay email where selected.
Your media: original photos or videos, audio within videos, descriptions, categories, prices, rights choices and available file metadata. Metadata may include recording dates, precise coordinates and device information already embedded in an imported original.
Location: optional foreground capture GPS, the event area you enter or confirm, optional nearby-place searches, and a recent location if you enable nearby request alerts. We do not use background GPS tracking for these features.
Optional AI help: when you choose Talk to support and send a question to the EYEWIT bot, your question, any follow-up details you send and approved public help articles are processed by Cloudflare Workers AI to select an app help answer. The assistant does not receive your account identifiers, media, GPS, bank records, staff notes or human support history from EYEWIT. Avoid putting personal details or secrets in the question. It cannot change your account or make decisions about you. You can contact a person without using AI.
Communications: newsroom conversations, support requests, contact enquiries, reports, moderation decisions, appeals, ratings and internal review records.
Optional tips and reminders: if you turn on Tips & reminders, EYEWIT may send app tips, promotional prompts and relevant payment setup reminders at most once every 24 hours, during daytime in your saved phone time zone. This choice starts off and can be withdrawn in Settings → Notifications. We keep the choice, consent time, time zone and last reminder time to enforce it. AI can select only from reviewed public tips; EYEWIT sends it no recipient identity, location, account details or verification result. Messages use approved wording. Setup eligibility is checked privately by EYEWIT, and test verification is clearly identified.
Service records: session tokens, device notification tokens, consent records, security and access records, IP/network information, and technical logs needed to operate and protect the service.
Newsrooms: organization details, team membership, invitations and press accreditation uploaded for review.
Financial features: the current pilot uses clearly labelled test wallet and Stripe verification records. Real sales and withdrawals remain disabled. Stripe-hosted onboarding collects the identity and bank information required for its verification flow directly on Stripe’s page. This flow does not upload or store copies of your identity documents, document numbers, verification selfies or bank account numbers on EYEWIT servers. EYEWIT stores the linked Stripe account reference, country, payment environment, general verification status, broad outstanding steps and relevant dates. Incoming Stripe notifications can contain personal details; our handler uses them transiently, ignores identity fields and does not save the full payload. Our separate account profile and any information you put in media, messages or email remain personal data handled by EYEWIT. Never submit identity documents through those channels. Use only Stripe’s fictitious test details while test mode is shown. We will provide the applicable information before activating real payments.

Why we use it

We use account, media and communication information to provide the service you request: managing your account, storing submissions, reviewing media, presenting approved listings and delivering messages and support. The basis is performance of our agreement with you, where the processing is necessary for that service.

Security, fraud prevention, restricted staff audit records and service reliability support our legitimate interests in protecting EYEWIT and its users, subject to your rights. Applicable legal obligations can require specific record retention or disclosures. Optional location assistance, notifications and sharing with Hive use separate choices and permissions; accepting the terms is not blanket consent to these features.

To protect anonymous exchanges, Newsroom messages are held for human review before delivery. Automated checks and Cloudflare Workers AI can flag names, precise addresses, contact details and other identifying context in a message. Recognizable contact details and numbers are masked before AI processing where supported. This analysis receives the message text, not account profiles, identity documents, media or conversation history. It returns risk categories to authorized reviewers, never an identity or an automatic delivery decision. Checks can miss identifying details; a human reviewer must explicitly check the message before approving delivery. AI classification results are not retained as a separate message transcript.

We send essential account and submission emails from noreply@eyewit.media. Submitting a contact form or creating an account does not subscribe you to marketing.

What Newsrooms can see

EYEWIT is a restricted professional platform, not a public social-media feed. Contributor submissions are not made available for the general public to browse. Media access within EYEWIT is limited to professional Newsrooms approved by EYEWIT and their authorized members, the contributor who submitted the media, and authorized EYEWIT staff for moderation, support and service operation. Approved Newsrooms can see reviewed media previews, the description, event area, asking price and licensing choices. Each media has a different contributor alias. A rounded contributor rating may appear beneath that alias.

A Newsroom that obtains a licence may subsequently publish the licensed content under the agreed rights. Restricted access inside EYEWIT does not mean that licensed content will never appear publicly.

This is pseudonymity, not complete anonymity. EYEWIT knows your account. Your images, audio, descriptions or repeated event details may identify you or other people. Precise capture GPS is excluded from marketplace fields. Do not include unnecessary identifying information in descriptions shown to Newsrooms.

Contributor and Newsroom conversations are moderated before delivery. Authorized operators can review them, including attempted contact sharing and relevant support history. Contributors cannot browse other contributors or their private libraries. Any identity disclosure needed for future legal or payment documents will be explained before real checkout is enabled.

For future paid sales, the purchasing Newsroom will receive the supplier name, billing address and any tax details required for the licence invoice only after payment has been verified. The contributor will be told which details will be disclosed and must accept the invoicing mandate before selling. These details will not be added to marketplace profiles or pre-sale conversations. Identity documents, bank account numbers, passwords and unrelated contact details are excluded from this invoice disclosure. Stripe and receiving banks may separately require evidence under their own checks. Any disclosure legally required before payment will be explained before checkout. This future-sale notice does not change the current pilot into a paid service.

Optional Hive analysis

Current contributor app versions submit media to EYEWIT moderation without offering external AI analysis. Some earlier versions offer a separate, optional permission to use Hive. Only if you gave that permission for a submission, EYEWIT sends the original media, including any embedded metadata, to Hive’s detection service. Sampled images, your description, event area and available dates/metadata may also be sent to Hive for context comparison.

A high detector score can lead to automatic rejection when the configured checks are satisfied. The default threshold is 80%; a score is not proof or a calibrated certainty about authenticity. Missing metadata alone is not grounds for rejection. You can ask for human review through the appeal action in My Media.

Permission is recorded for each submission. Declining it routes the media to human review. In the contributor app, open Account settings → Read EYEWIT privacy notice → Optional sharing choices to stop pending processing. You can also ask us through Support or email. A request already transmitted cannot be recalled; contact us to request erasure of data already shared, subject to applicable retention obligations and the provider’s processing arrangements. See Hive’s privacy information.

Providers and recipients

Stripe: hosted payment verification in the mode identified by the app. We send your account email, country and an internal account reference to set up the linked Stripe account. Stripe handles verification information under its own obligations and retention rules; this does not remove EYEWIT’s responsibility for the personal data it processes. See Stripe’s privacy policy.
Supabase: authentication, private database records and media storage used by the pilot.
Cloudflare: website/API hosting, routing, security and optional support replies and conversation translation through Workers AI. Support AI requires your separate choice in the chat. You can continue with documented help or a support person without AI and turn AI off in the same chat. Turning it off stops future requests and clears saved support translations; it cannot recall processing already sent. Standard support inference does not use AI Gateway logging, caching or model training. See Cloudflare Workers AI data use and exceptions.
Zoho ZeptoMail and Zoho Mail: transactional email delivery and handling contact/support enquiries.
Hive: optional media authenticity and context analysis, as described above.
Geoapify / OpenStreetMap: place lookup and optional nearby-place assistance. To check a submission’s location, we send the event-place text you enter; that lookup does not include original media, capture GPS or account identifiers. Optional nearby-place assistance sends requested coordinates through EYEWIT; up to three places within 300 metres may be suggested. Precise capture coordinates are not added to Newsroom fields.
Expo and Google Firebase / Apple notification services: device notification delivery when enabled. Nearby-request push messages do not contain precise GPS coordinates.
Apple and Google: optional sign-in and operating-system services. Opening external directions or a map sends the selected destination to that service.
Authorized staff and professional advisers: access limited by their functions and the purpose of the request. Authorities may receive information when disclosure is legally required.

Optional AI wording for landmark descriptions is currently disabled. If enabled later, it will be explained before use; the planned wording request excludes original media, GPS, account identifiers and capture timestamps. Stripe is the current test payment provider; real sales and withdrawals remain disabled.

For location review, EYEWIT compares the entered place with available capture information. Missing or uncertain evidence remains unverified. A mismatch or reported mock location alerts a human reviewer; it does not automatically reject your submission. Derived reports contain a status, explanation and, where available, approximate distance or accuracy, without a new copy of exact coordinates. Detailed evidence is restricted to authorized staff and removed when the associated original is archived or the submission is deleted.

International processing

Hive operates its services in the United States and may process information there or in other countries. Other providers may also process information outside Ireland or the European Economic Area. Where GDPR transfer rules apply, transfers require an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses, together with any necessary supplementary measures. Contact us for information about the safeguards applicable to your data. A local-looking app interface does not mean every service is hosted in your country.

How long information is kept

Account information, accepted media and related messages are retained while needed to provide your account and manage the rights or requests associated with it. On a deletion request we review and remove the account and associated personal data, including uploaded content, except where retention is required by law. Any exception must have a specific purpose and restricted access; deleting an account is not merely suspending it.

Rejected originals and previews are scheduled for deletion after seven days without an appeal, subject to existing rights or a lawful preservation requirement. An appeal pauses that deletion; decision history is kept separately.
Recent location stops qualifying for nearby request matching after one hour. A database cleanup runs every five minutes to delete expired nearby-request coordinates from active storage, independently of the app servers. Your alert choice can remain saved without coordinates; update your location to resume nearby alerts. This cleanup does not remove location metadata embedded in submitted original media. Backups have separate retention cycles.
Website contact anti-abuse hashes and submission receipts expire after 24 hours. Enquiry emails remain only as long as needed to handle the enquiry and related obligations.
Nearby-landmark and AI support anti-abuse records normally clear within 25 hours. The AI support budget stores a hashed account identifier and timestamps, not questions or replies. AI help text stays in running app memory, without a saved AI transcript. A question copied into a human support message is stored only when you review and send it, under the usual support retention rules. Cloudflare may retain operational metadata under its published terms.
Unpublished drafts are held in the running app and are lost when it is closed or reloaded. Original copies in your device library are controlled by you.
Security, agreement, dispute and future financial records are assessed according to the purpose and applicable legal retention requirements. We will explain any exception affecting a deletion request.

Provider backups and records can have separate retention cycles. We do not promise that a copy disappears instantly from every backup or from an independent recipient’s records.

Your rights and choices

You may request access, correction, erasure, restriction or portability of your personal data, and object to processing based on legitimate interests, as applicable. You can withdraw optional permission without affecting processing that was lawful before withdrawal. Device settings control camera, microphone, location and notification permissions. Manual event-location entry remains available.

Use Account settings → Delete my account in the app, or our account deletion page. You can make other requests through contact@eyewit.media. We may verify account ownership using proportionate information, preferably your existing account or email. We normally respond within one month and will explain any lawful extension.

You may complain to the Irish Data Protection Commission or your competent local supervisory authority. You can contest an automated media rejection and provide additional explanation for a human reviewer.

Safety, storage and changes

We use access controls, private storage and protected connections. Account sessions use secure device storage on supported native devices; web sessions use browser storage. No service can guarantee absolute security. The presentation website does not add advertising cookies or marketing analytics.

EYEWIT is not designed for children. Do not submit material unlawfully obtained or unnecessary sensitive information about yourself or other people. Contact us if you believe a child has provided personal data without appropriate authorization.

We will update this policy when our practices change. Material changes and new optional processing will be explained in the app where appropriate. The version and date identify the policy you have read.