--- title: White-Label inDrive App Security: Risks, Standards & Best Practices 2026 description: A practical security guide for founders planning a white-label inDrive app or inDrive clone in 2026. Learn how to protect user locations, ride data, payments, APIs, driver verification, admin access, and platform trust before launch. url: https://miracuves.com/blog/indrive-app-security-risks-guide date_modified: 2026-06-22 author: Abhinav Saini language: en_US --- ### Key Takeaways - Ride-hailing apps handle sensitive user and driver data. - Security should be a launch-day priority. - Payment, location, and account data need protection. - Compliance helps reduce legal and business risks. - Security requires continuous monitoring and updates. ### Security Signals - Use role-based access for riders, drivers, and admins. - Enable encrypted communication across all APIs. - Protect payment flows with PCI-DSS standards. - Use multi-factor authentication for admin accounts. - Maintain logs for critical platform activities. ### Real Insights - Most breaches start with weak access controls. - Location data leaks can damage user trust. - Regular audits help identify hidden vulnerabilities. - Compliance improves investor and customer confidence. - Secure platforms scale more safely in competitive markets. You’ve heard the horror stories. Ride-hailing apps leaking user locations. Payment data exposed due to weak APIs. Startups facing lawsuits after a single security breach wiped out user trust overnight. If you’re planning to launch a white-label inDrive app or **[inDrive clone](https://miracuves.com/indrive-clone/)**, one question matters more than features, pricing, or speed to market: **how secure is the platform before real users start booking rides?** **Is it actually safe?** In 2026, safety is no longer optional for [**ride-hailing platforms**](https://miracuves.com/ready-made-apps/ride-hailing-app/). Apps like inDrive handle real-time location data, personal identities, driver documents, trip histories, and payment information—making them prime targets for cybercriminals and regulatory scrutiny. At the same time, white-label app solutions often carry a stigma: - “Are they less secure than custom apps?” - “Will my users’ data really be protected?” - “Who is responsible if something goes wrong?” This guide answers those concerns honestly. We’ll break down: - How white-label inDrive app security actually works - The real risks founders should worry about (and the myths they shouldn’t) - The security standards your app must meet in 2026 - How to identify unsafe providers before it’s too late - And how [Miracuves](https://miracuves.com/) approaches white-label app security differently—enterprise-first, compliance-ready, and risk-aware This is not sales fluff. It’s a practical, security-focused assessment designed to help you make an informed decision before launching your platform. ## Understanding White-Label inDrive App Security Landscape ### What White-Label inDrive App Security Actually Means White-label security does not mean “shared,” “generic,” or “less protected.” ![White-label inDrive app interface showing ride booking, courier service, intercity travel, and real-time map navigation on a mobile screen](https://miracuves.com/wp-content/uploads/2025/12/services-app-interface-e1766495619659-1024x749.webp "White-Label inDrive App Security: Risks, Standards & Best Practices 2026 1")Image credit – Chat gpt - A reusable core architecture that has already been hardened, tested, and audited - Isolated deployments where your app’s data, users, and transactions are not shared with anyone else - Security controls applied at application, infrastructure, and data layers The difference lies in who designs and maintains the security framework. A serious provider builds security into the foundation, while unsafe vendors treat it as an afterthought. At Miracuves, white-label means pre-secured, not pre-compromised. ### Common Security Myths vs Reality **White-label apps are less secure than custom apps** Many custom apps fail because startups skip security audits, compliance, and penetration testing due to cost and time. A mature white-label inDrive app often starts with stronger baseline security. **One security breach means the provider is responsible** Security is a shared responsibility. The provider secures the platform, infrastructure, and code. The business owner must follow operational and compliance best practices. **Security can be “added later”** Retrofitting security after launch is expensive, risky, and often non-compliant with modern regulations. ### Why People Worry About White-Label inDrive Apps Concerns around white-label ride-hailing apps usually come from: - Vendors offering unrealistically cheap pricing - Lack of visible compliance certifications - Poor transparency around data handling - News of ride-hailing data breaches globally Since inDrive-style platforms involve negotiated pricing, driver–rider communication, and live tracking, users naturally worry about misuse of sensitive data. These fears are valid—but only when the provider cuts corners. ### Current Threat Landscape for Ride-Hailing Apps in 2026 Ride-hailing platforms are among the top five most targeted mobile app categories globally. Key threats include: - API abuse exposing trip and pricing data - Account takeover through weak authentication - Location tracking exploitation - Payment fraud and wallet manipulation - Insider threats from poorly controlled admin access According to global cybersecurity reports, transport and mobility apps saw a 38% increase in attempted API attacks between 2023 and 2026, driven largely by automated bots and credential stuffing attacks. ### Security Standards That Matter in 2026 By 2026, minimum acceptable security expectations for an inDrive-style app include: - Encrypted data storage and transmission by default - Zero-trust access controls for admin panels - Secure mobile authentication mechanisms - Continuous monitoring instead of one-time audits - Compliance-aligned system architecture from day one Anything below this baseline is no longer considered safe. ### Real-World App Security Statistics - Over 60% of mobile app breaches originate from insecure APIs - Nearly 45% of data leaks occur due to misconfigured cloud storage - Ride-hailing and logistics apps face higher regulatory penalties due to location and identity data exposure - Apps without regular security updates are 3× more likely to experience critical vulnerabilities within the first year These are not theoretical risks. They are patterns seen repeatedly across unsafe implementations. ## Key Security Risks & How to Identify Them ### Data Protection & Privacy Risks Ride-hailing apps like inDrive manage some of the most sensitive user data in any consumer platform. #### User Personal Information Names, phone numbers, profile photos, driver documents, and identity proofs must be stored securely. Poor encryption or shared databases can expose thousands of users instantly. #### Payment Data Security Even if third-party payment gateways are used, insecure token handling, weak callbacks, or improper storage can still lead to payment-related breaches. #### Location Tracking Concerns Real-time GPS data is highly sensitive. If not properly protected, it can be exploited for stalking, fraud, or physical safety risks. #### GDPR and CCPA Compliance Improper consent handling, unclear data retention policies, or lack of user data deletion options can result in serious regulatory penalties. ### Technical Vulnerabilities Most security failures happen at the technical layer, not the UI. #### Code Quality Issues Hardcoded credentials, outdated libraries, and poor error handling are common in unsafe white-label apps. #### Server Security Gaps Misconfigured cloud servers, open ports, and weak firewall rules expose backend systems to direct attacks. #### API Vulnerabilities Unprotected APIs can allow attackers to: - Access trip history - Manipulate pricing - Scrape user data - Perform unauthorized actions #### Third-Party Integrations Maps, notifications, analytics, and payment services introduce risk if not properly validated and monitored. ### Business-Level Security Risks Security failures don’t just affect systems—they affect the business itself. #### Legal Liability Data breaches can trigger lawsuits, regulatory investigations, and compliance violations. #### Reputation Damage Trust loss spreads faster than the breach itself. One incident can permanently impact user growth. #### Financial Losses Costs include incident response, legal fees, compensation, and lost revenue during downtime. #### Regulatory Penalties Non-compliance with data protection laws can lead to fines running into millions, even for early-stage startups. ### Security Risk Assessment Checklist - Is all user and driver data encrypted at rest and in transit? - Are APIs protected with authentication and rate limiting? - Is real-time location data access restricted and logged? - Are payment workflows PCI DSS aligned? - Is admin access role-based and audited? - Are regular security updates part of the delivery process? - Is compliance documented and verifiable? If a provider cannot clearly explain these points, the app is not ready for real-world deployment. Read more : – [InDrive App Features: What Sets It Apart](https://miracuves.com/blog/indrive-app-features/) ## Security Standards Your White-Label inDrive App Must Meet ### Essential Security Certifications A serious white-label inDrive app must align with globally recognized security and compliance frameworks. These are no longer optional in 2026. #### ISO 27001 Compliance This ensures the provider follows a structured Information Security Management System (ISMS), covering risk assessment, access control, incident handling, and continuous improvement. Why it matters: ISO 27001 reduces human error, enforces internal controls, and proves that security is a process—not a one-time setup. #### SOC 2 Type II SOC 2 Type II validates how user data is handled over time, not just at a single moment. It evaluates: - Security - Availability - Confidentiality - Processing integrity For ride-hailing apps, this is critical because user trust depends on long-term operational discipline. #### GDPR Compliance If your app serves users in the EU (or plans to), GDPR compliance is mandatory. This includes: - Explicit user consent - Right to data access and deletion - Clear data processing documentation - Breach notification protocols Non-compliance can result in penalties up to 4% of global annual revenue. #### HIPAA (If Applicable) While not mandatory for all ride-hailing apps, HIPAA becomes relevant if your platform handles medical transportation, patient data, or healthcare-related mobility services. #### PCI DSS for Payments Any app processing card payments must follow PCI DSS standards. This ensures: - Secure payment data handling - Tokenization instead of raw card storage - Restricted access to financial systems - Continuous vulnerability monitoring ### Technical Security Requirements Certifications alone are not enough. Your white-label inDrive app must meet concrete technical security benchmarks. #### End-to-End Encryption All sensitive data—including location updates, messages, and payment transactions—must be encrypted during transmission and storage. #### Secure Authentication Mechanisms Modern apps must support: - Two-factor authentication - OAuth-based logins - Secure session management - Protection against brute-force attacks #### Regular Security Audits Security audits should be conducted at defined intervals, not only before launch. Audits help identify: - New vulnerabilities - Configuration errors - Compliance gaps - Risk exposure from updates #### Penetration Testing Ethical hackers simulate real-world attacks to uncover weaknesses before criminals do. Penetration testing should cover: - APIs - Mobile apps - Admin dashboards - Cloud infrastructure #### SSL Certificates SSL is a baseline requirement to ensure encrypted communication between users, servers, and third-party services. #### Secure API Design APIs must include: - Authentication and authorization - Rate limiting - Input validation - Detailed logging and monitoring APIs are the most targeted attack surface in ride-hailing apps. ### Security Standards Comparison Overview A secure white-label inDrive app should demonstrate: - Compliance-backed governance (ISO, SOC 2) - Legal readiness (GDPR, PCI DSS) - Technical hardening (encryption, secure APIs) - Ongoing risk management (audits, monitoring) If a provider cannot clearly map their app to these standards, the risk is pushed directly onto your business. ## Red Flags: How to Spot Unsafe White-Label Providers ### Warning Signs You Should Never Ignore Security issues are often visible long before a breach happens. The problem is that many founders overlook them in favor of speed or pricing. #### No Security Documentation If a provider cannot share security architecture details, data flow diagrams, or compliance documentation, it usually means security was never formally implemented. #### Unrealistically Cheap Pricing Building and maintaining a secure [**inDrive**](https://indrive.com/)-style app involves infrastructure, audits, monitoring, and compliance costs. Extremely low pricing often indicates corners being cut. #### No Compliance Certifications Providers who dismiss ISO, SOC 2, or GDPR as “not required” are exposing your business to regulatory and legal risk. #### Outdated Technology Stack Old frameworks, unsupported libraries, and legacy servers are common sources of vulnerabilities. #### Poor Code Quality - Hardcoded keys - No environment separation - Weak error handling - No version control discipline These issues directly increase breach probability. #### No Security Update Policy Security threats evolve constantly. If updates and patches are not part of the contract, your app will become vulnerable over time. #### Lack of Data Backup Systems Without automated backups and recovery plans, a single incident can permanently destroy business data. #### No Insurance Coverage Reputable providers carry cyber liability insurance. If they don’t, the financial risk shifts entirely to you. ### Evaluation Checklist for White-Label inDrive App Providers Before selecting a provider, evaluate them systematically. #### Questions to Ask - How is user and driver data encrypted? - Where is data stored and in which regions? - How often are security audits performed? - Who is responsible for breach response? - What compliance standards are followed? #### Documents to Request - Security architecture overview - Compliance certificates - Audit and penetration test reports - Data processing agreements - Incident response policy #### Testing Procedures - API security testing - Authentication and authorization testing - Admin access control validation - Payment workflow verification #### Due Diligence Steps - Review past security incidents - Check client references - Validate update and maintenance commitments - Confirm legal and insurance coverage Choosing a provider without this diligence is one of the most common causes of white-label app failures. ## Best Practices for Secure White-Label inDrive App Implementation ![Secure white-label inDrive app implementation process covering security audits, compliance verification, monitoring, updates, and data protection](https://miracuves.com/wp-content/uploads/2025/12/secure-white-label-indrive-app-implementation-best-practices-1024x683.webp "White-Label inDrive App Security: Risks, Standards & Best Practices 2026 2")Image Source: Chatgpt ### Pre-Launch Security Practices Security work must begin long before users install the app. #### Security Audit Process Conduct a full security audit covering mobile apps, backend services, APIs, and cloud infrastructure. This helps identify weaknesses before they reach production. #### Code Review Requirements Independent code reviews ensure: - Secure coding standards are followed - No sensitive data is hardcoded - Business logic cannot be abused - Authentication flows are correctly implemented #### Infrastructure Hardening Servers should be configured using security-first principles: - Private networks for databases - Firewalls and intrusion detection - Least-privilege access controls - Environment separation for development and production #### Compliance Verification Before launch, verify that GDPR, PCI DSS, and other relevant compliance requirements are met and documented. #### Staff Training Programs Internal teams must be trained on: - Data handling policies - Access control procedures - Incident reporting workflows - Regulatory responsibilities Human error remains a leading cause of breaches. ### Post-Launch Security Monitoring Launching the app is not the end of security responsibility. #### Continuous Security Monitoring Use monitoring tools to detect: - Unusual login behavior - API abuse - Suspicious location access - Payment anomalies #### Regular Updates and Patches Operating systems, libraries, and frameworks must be updated continuously to address newly discovered vulnerabilities. #### Incident Response Planning A defined response plan ensures quick action during security events, minimizing damage and downtime. #### User Data Management Establish clear policies for: - Data retention periods - User data deletion requests - Data anonymization where possible #### Backup and Recovery Systems Automated backups and tested recovery plans protect the business from data loss, ransomware, and operational failures. ### Security Implementation Timeline Overview A secure white-label inDrive app rollout typically includes: - Pre-launch audits and testing - Secure infrastructure setup - Compliance validation - Controlled production launch - Ongoing monitoring and updates Skipping any of these steps increases long-term risk significantly. ## Legal & Compliance Considerations ### Regulatory Requirements White-label inDrive apps operate in a highly regulated environment because they process personal, financial, and location-based data. #### Data Protection Laws by Region Different regions enforce different data protection frameworks: - European Union: GDPR with strict consent, access, and deletion rights - United States: CCPA and state-level privacy laws - United Kingdom: UK GDPR - Middle East and Asia: Emerging privacy laws with localization requirements Your app must be designed to adapt to regional compliance obligations from the start. #### Industry-Specific Regulations Ride-hailing platforms may also face: - Transportation authority regulations - Local licensing and driver verification laws - Background check requirements - Platform accountability rules Ignoring these can lead to forced shutdowns or app store removals. #### User Consent Management Users must explicitly agree to: - Location tracking - Data processing purposes - Communication policies - Terms and privacy conditions Consent must be logged, stored, and retrievable for audits. #### Privacy Policy Requirements A compliant privacy policy must clearly explain: - What data is collected - Why it is collected - How long it is stored - Who it is shared with - How users can request deletion or correction Generic or copied policies increase legal exposure. #### Terms of Service Essentials Terms must define: - Platform responsibilities - User obligations - Limitation of liability - Dispute resolution mechanisms - Jurisdiction and governing law ### Liability Protection Strategies Even the most secure systems require legal safeguards. #### Insurance Requirements Cyber liability insurance helps cover: - Data breach response costs - Legal defense expenses - Regulatory fines where permitted - User compensation claims Insurance is increasingly required by enterprise partners and regulators. #### Legal Disclaimers Clear disclaimers define platform scope and reduce ambiguity around responsibility in edge cases. #### User Agreements Driver and rider agreements should address: - Data usage - Safety responsibilities - Pricing disputes - Account suspension policies #### Incident Reporting Protocols Regulations often require breach reporting within defined timeframes. Your app must support fast detection and documentation. #### Ongoing Compliance Monitoring Laws evolve. Continuous monitoring ensures your app remains compliant as regulations change. ### Compliance Checklist by Region A legally safe white-label inDrive app should: - Support regional data storage requirements - Enable user data rights management - Maintain audit-ready documentation - Track consent and policy acceptance - Integrate legal review into update cycles Without this structure, even a technically secure app can become legally unsafe. Read more : – [How to Hire the Best Indrive Clone Developer](https://miracuves.com/indrive-clone/development-company/) ## Why Miracuves White-Label inDrive App is Your Safest Choice ### Miracuves Security-First Advantage At [Miracuves](https://miracuves.com/), security is not treated as an add-on or optional upgrade. It is engineered into the core of every white-label inDrive app we deliver. Our approach is built around **enterprise-grade protection, regulatory readiness, and long-term risk reduction**, ensuring your platform remains safe as it scales. #### Enterprise-Grade Security Architecture Miracuves apps are designed using layered security models that protect data at the application, API, and infrastructure levels. #### Regular Security Audits and Certifications We follow structured security governance aligned with international standards, ensuring continuous assessment and improvement rather than one-time validation. #### GDPR and CCPA Compliant by Default User consent management, data access controls, and deletion workflows are built directly into the platform to support global compliance requirements. #### 24/7 Security Monitoring Our systems are continuously monitored to detect unusual activity, prevent abuse, and respond quickly to emerging threats. #### Encrypted Data Transmission All sensitive data—including location updates, messages, and transactions—is encrypted during transmission and storage. #### Secure Payment Processing Miracuves integrates PCI DSS–aligned payment workflows to protect financial transactions and reduce fraud exposure. #### Regular Security Updates Security patches, dependency updates, and infrastructure improvements are part of our ongoing maintenance commitment. #### Insurance Coverage Included We work with insured infrastructure and risk-mitigated deployment practices to protect both our clients and their platforms. ## Final Thought Miracuves white-label inDrive app solutions are built with enterprise-grade protection from day one. With 9k+ successful projects delivered and zero major security breaches reported, businesses trust Miracuves to launch safe, compliant, and scalable ride-hailing platforms. When built with the right architecture, standards, and governance, a white-label app can be just as secure — often more secure — than custom development. The real risk lies in choosing providers who treat security as optional. A security-first approach protects not only user data, but also your brand reputation, legal standing, and future growth. If you are planning a secure **[Ride Sharing Development](https://miracuves.com/solutions/ride-sharing/)** project, Miracuves can help you build a scalable platform with protected payments, real-time tracking security, driver verification, admin controls, and compliance-ready architecture. **[Contact us](https://miracuves.com/contact/)** today to get a free security assessment and understand how a security-first approach can protect your users, your data, and your brand. .miracuves-short-cta-2025 { background: linear-gradient(135deg, #a70d2a 0%, #7b081f 55%, #a70d2a 100%); color: #f9fbff; padding: 1.75rem 1.5rem; border-radius: 1.5rem; max-width: 800px; width: 100%; box-sizing: border-box; margin: 0 auto; box-shadow: 0 18px 45px rgba(0, 0, 0, 0.35); position: relative; overflow: hidden; font-family: system-ui, -apple-system, BlinkMacSystemFont, "SF Pro Text", "Segoe UI", sans-serif; } .miracuves-short-cta-2025::before { content: ""; position: absolute; inset: -40%; background: radial-gradient(circle at top right, rgba(255, 255, 255, 0.16), transparent 55%); opacity: 0.85; pointer-events: none; } .miracuves-short-cta-2025-inner { position: relative; z-index: 1; display: flex; flex-direction: column; gap: 1rem; } .miracuves-short-cta-2025-eyebrow { font-size: 0.8rem; letter-spacing: 0.14em; text-transform: uppercase; opacity: 0.9; } .miracuves-short-cta-2025-headline { font-size: 1.35rem; line-height: 1.3; font-weight: 650; } .miracuves-short-cta-2025-subline { font-size: 0.95rem; line-height: 1.5; opacity: 0.9; max-width: 40rem; } .miracuves-short-cta-2025-meta-row { display: flex; flex-wrap: wrap; gap: 0.5rem; margin-top: 0.25rem; } .miracuves-short-cta-2025-chip { display: inline-flex; align-items: center; gap: 0.4rem; padding: 0.3rem 0.7rem; border-radius: 999px; background: rgba(249, 251, 255, 0.06); border: 1px solid rgba(249, 251, 255, 0.18); font-size: 0.78rem; white-space: nowrap; } .miracuves-short-cta-2025-chip-label { text-transform: uppercase; letter-spacing: 0.14em; font-size: 0.7rem; opacity: 0.82; } .miracuves-short-cta-2025-chip-value { font-weight: 500; } .miracuves-short-cta-2025-actions { display: flex; flex-direction: column; gap: 0.6rem; margin-top: 0.9rem; } .miracuves-short-cta-2025-actions-row { display: flex; flex-direction: column; gap: 0.6rem; width: 100%; } .miracuves-short-cta-2025-btn { display: inline-flex; align-items: center; justify-content: center; padding: 0.65rem 1.1rem; border-radius: 999px; border: 1px solid rgba(255, 255, 255, 0.65); font-size: 0.9rem; font-weight: 550; background: #ffffff; color: #050505; box-shadow: 0 10px 26px rgba(0, 0, 0, 0.35); transition: color 0.18s ease, box-shadow 0.18s ease, border-color 0.18s ease, transform 0.18s ease; cursor: pointer; white-space: normal; text-decoration: none; text-align: center; width: 100%; box-sizing: border-box; } .miracuves-short-cta-2025-btn-secondary { border-color: rgba(255, 255, 255, 0.55); box-shadow: 0 10px 24px rgba(0, 0, 0, 0.28); background: rgba(255, 255, 255, 0.98); } .miracuves-short-cta-2025-btn:hover, .miracuves-short-cta-2025-btn:focus { color: #a70d2a; box-shadow: 0 14px 32px rgba(0, 0, 0, 0.42); border-color: #ffffff; transform: translateY(-1px); } .miracuves-short-cta-2025-reassure { margin-top: 0.4rem; font-size: 0.8rem; opacity: 0.86; } @media (min-width: 720px) { .miracuves-short-cta-2025 { padding: 2rem 2.1rem; } .miracuves-short-cta-2025-inner { flex-direction: row; justify-content: space-between; align-items: center; gap: 2.25rem; } .miracuves-short-cta-2025-main { flex: 1.3; } .miracuves-short-cta-2025-side { flex: 1; display: flex; flex-direction: column; align-items: flex-end; } .miracuves-short-cta-2025-headline { font-size: 1.55rem; } .miracuves-short-cta-2025-actions-row { flex-direction: row; justify-content: flex-end; gap: 0.75rem; } .miracuves-short-cta-2025-btn { width: auto; } } Miracuves Build a secure White-Label inDrive app without waiting months. See how our white-label inDrive solution handles security, compliance, and user safety — then get a demo, pricing, and a clear deployment plan for your market. inDrive • 6 Days deployment [Chat on WhatsApp](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number) [Book a consultation](https://miracuves.com/schedule-consultation/) In one call, we align security requirements, budget, and go-live dates with full clarity. ## FAQs ### 1. How secure is a white-label inDrive app compared to custom development? A properly built white-label inDrive app can be as secure or more secure than custom development because it starts with a tested, audited, and hardened security architecture. ### 2. What happens if there is a security breach? A secure provider follows an incident response plan that includes breach containment, investigation, regulatory reporting, and user notification within legal timelines. ### 3. Who is responsible for security updates? The provider is responsible for platform-level security updates, while the business owner must follow operational security best practices. ### 4. How is user data protected in a white-label inDrive app? User data is protected through encryption, access controls, secure APIs, and compliance-driven data handling policies. ### 5. What compliance certifications should I look for? ISO 27001, SOC 2 Type II, GDPR compliance, and PCI DSS are essential for ride-hailing platforms. ### 6. Can white-label inDrive apps meet enterprise security standards? Yes, when built with proper architecture, audits, and monitoring, white-label apps can meet enterprise-level security requirements. ### 7. How often should security audits be conducted? Security audits should be conducted regularly, ideally annually or after major platform updates. ### 8. What is included in Miracuves’ security package? Enterprise-grade security architecture, compliance readiness, encrypted data handling, continuous monitoring, and regular security updates. ### 9. How is security handled across different countries? The app supports regional compliance through adaptable data handling, consent management, and localization-ready legal frameworks. ### 10. What insurance is needed for app security? Cyber liability insurance is recommended to cover breach response, legal costs, and regulatory exp **Related Articles:** - [InDrive Revenue Model: How InDrive Makes Money in 2025](https://miracuves.com/blog/indrive-revenue-model/) - [Reasons startup choose our Indriver clone over custom development](https://miracuves.com/blog/indriver-clone-over-custom-development/) - [InDriver-Style App Cost Guide : MVP to Full Build](https://miracuves.com/indrive-clone/development-cost/)