Privacy Policy

How MarGioM Software Studio handles website visits, project inquiries, support requests, client portal records, files, payment workflow data, and communication details.

Effective date: June 20, 2026

A practical privacy notice for the MarGioM platform.

This policy applies to MarGioM.com, public inquiry forms, quote requests, request tracking, discovery workflows, proposals, contracts, deposits, payment proof, client portal access, support tickets, career applications, emails, and related project communication. It is written for MarGioM's real operating workflow and should be reviewed by a qualified legal professional before publication as final legal advice.

Information MarGioM Collects
MarGioM collects information you provide directly and operational data needed to review requests, communicate, and deliver software projects.
  • Contact details such as name, email, phone number, Telegram username, company, country, and preferred reply channel.
  • Inquiry and project details such as project type, budget direction, timeline, descriptions, requirements, reference links, selected features, proposal requests, discovery-call requests, and uploaded files.
  • Client workflow records such as Request ID, Access Code verification events, discovery answers, proposal decisions, contract/deposit status, project workspace activity, support tickets, change requests, bug reports, and project updates.
  • Career application and support information such as role interest, experience summary, portfolio links, support topics, ticket details, and communication history.
  • Technical and source metadata such as source page, source CTA, UTM campaign data, timestamps, browser/device signals, and basic abuse-prevention logs.
How Information Is Used
Information is used only for legitimate studio operations and communication around your inquiry or project.
  • Reviewing project fit, clarifying requirements, preparing proposals, and planning discovery calls.
  • Sending confirmation emails, Request ID and Access Code details, request updates, proposal links, invoice/deposit notices, support replies, and client portal invitations.
  • Operating admin dashboards, project tracking, client workspaces, file downloads, support tickets, invoices, and maintenance records.
  • Improving website content, lead-source understanding, form quality, fraud/spam protection, payment reliability, and operational security.
Files, Payments, and Sensitive Material
Visitors should avoid sharing secrets through public forms. Private project material should move through approved client channels.
  • Do not submit passwords, private keys, API secrets, bank credentials, payment card details, health records, or confidential customer databases through public forms.
  • Payment proof files, contracts, proposals, and project documents are treated as private operational records and should not be publicly exposed.
  • Online payments may be processed by payment providers such as Chapa or future supported gateways. MarGioM does not store full card, bank, or wallet credentials.
  • Manual payment instructions and uploaded proof are reviewed by MarGioM before a payment is marked verified.
Service Providers and Sharing
MarGioM uses trusted services to operate the website, store project data, send emails, process payments, and protect the platform.
  • Information may be processed by providers for hosting, database, authentication, file storage, email delivery, analytics, spam protection, payment processing, PDF/DOCX generation, and support operations.
  • Examples may include Vercel, Supabase, Resend, Chapa, analytics tools, security tools, domain/email providers, and future services needed to run MarGioM responsibly.
  • Authorized MarGioM team members or contractors may access project information only when needed for review, delivery, support, maintenance, accounting, security, or legal purposes.
  • MarGioM does not sell client project files, inquiry data, or private support messages.
Cookies, Analytics, and Source Tracking
MarGioM may use lightweight tracking to understand which pages, campaigns, and calls to action generate inquiries.
  • Forms may store source page, source CTA, campaign, medium, and UTM values so MarGioM can understand where a request came from.
  • Analytics and technical logs may help measure page performance, improve content, detect spam, and troubleshoot errors.
  • Browser settings, cookie controls, privacy extensions, or analytics opt-out tools may limit some tracking features.
  • Tracking should not be used to expose private project data publicly or to make automated decisions that start a paid project without human review.
Retention, Access, and Deletion
Different records are kept for different operational, legal, accounting, project delivery, and support reasons.
  • General inquiries may be retained while MarGioM evaluates, replies, follows up, or measures lead sources.
  • Project records, proposals, agreements, invoices, payment proof, messages, files, and support tickets may be retained for delivery, maintenance, accounting, legal, and business record purposes.
  • Career applications may be retained for hiring review unless deletion is requested or retention is no longer useful.
  • You may request access, correction, export, or deletion where appropriate. Some records may need to be retained when required for contracts, accounting, fraud prevention, dispute handling, security, or legal compliance.
Security and Access Controls
MarGioM limits access to business reasons and keeps production services configured with role-based protections where available.
  • Request access codes should be stored as hashes, and private admin data should not be shown in public tracking views.
  • Admin-only notes, private files, payment records, internal workflow data, and service-role credentials must remain restricted to authorized MarGioM users.
  • Client portal access is intended for verified clients and should be limited to the client project or workspace linked to that account.
  • No online system can be guaranteed completely secure. MarGioM works to apply reasonable safeguards and asks users to avoid submitting unnecessary sensitive data.
International Use and Children
MarGioM serves Ethiopian and remote clients, and some providers may process data outside the user's country.
  • By using MarGioM.com, you understand that hosting, email, storage, payment, analytics, and security providers may process data in different regions.
  • The website is intended for business and project communication, not for children. Children should not submit personal information through MarGioM forms.
  • If a parent or guardian believes a child submitted information, they can contact MarGioM to request review or deletion.
  • Users are responsible for ensuring they have permission to submit business data, team member details, reference files, or customer-related materials.

Contact and updates

Privacy questions and deletion requests

For privacy questions, corrections, or deletion requests, contact MarGioM through the support page and include the related Request ID, Inquiry ID, email address, or project context. This notice may be updated as MarGioM adds production services, payment providers, or client portal features.

support@margiom.comContact supportRead terms

Last updated June 20, 2026. This notice is operational guidance for MarGioM and should be reviewed by a qualified legal professional before relying on it as a final legal policy.